You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2024. It is now read-only.
How would you regenerate cassettes used by functional tests? Once you set up your appvm to run the dev server and proxy and to be able to talk to the sd-sdk functional tests, then what do you do? The docs say:
Now, delete any related JSON file under data/ directory, or remove all of them, and then execute make test TEST=tests/test_apiproxy.py. This is command will generate the new data files, which can be used in CI or any other system.
I think what's missing here is that you actually need to first delete data/setUp.json and comment out
and also you have to do something in order to regenerate the new cassette for test_api.py (not just for test_apiproxy.py) which uses data/test-setup.yaml which fails when you delete it. This is still unclear.
Description
Say you want to update the sdk like so:
How would you regenerate cassettes used by functional tests? Once you set up your appvm to run the dev server and proxy and to be able to talk to the sd-sdk functional tests, then what do you do? The docs say:
I think what's missing here is that you actually need to first delete
data/setUp.json
and comment outsecuredrop-sdk/tests/test_apiproxy.py
Line 29 in aa15037
test_api.py
(not just fortest_apiproxy.py
) which usesdata/test-setup.yaml
which fails when you delete it. This is still unclear.Also say you want to make a change such as:
You would need to make sure not to restart the server so you can use the same token right? This needs to be clarified in the docs.
These are two examples of changes that are currently being used successfully in the securedrop-client pr here: freedomofpress/securedrop-client#1137
The text was updated successfully, but these errors were encountered: