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
In order to work around difficulty with mocking non-string responses in the datajson extension, the data.gov team wants to implement a integration test for datajson export from the inventory app.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
GIVEN datasets are created within an organization on inventory app
WHEN the organization data.json file is exported
THEN a zip file is downloaded
AND the parsed file contains the expected data.json file and metadata
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Due to the change in ckan tests, the TestExport class in ckanext-datajson will be re-implemented in inventory-app to validate this key use case
mogul
changed the title
Test Export in Inventory-app instead of ckanext-datajson
Test export of datajson from the inventory-app instead of ckanext-datajson
Jul 8, 2021
User Story
In order to work around difficulty with mocking non-string responses in the datajson extension, the data.gov team wants to implement a integration test for datajson export from the inventory app.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
WHEN the organization data.json file is exported
THEN a zip file is downloaded
AND the parsed file contains the expected data.json file and metadata
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Due to the change in ckan tests, the
TestExport
class inckanext-datajson
will be re-implemented in inventory-app to validate this key use caseOriginal code is here.
Security Considerations (required)
None
Sketch
Implement with bats testing framework.
The text was updated successfully, but these errors were encountered: