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 make sure base use cases are covered, data.gov admins want a complete end-to-end test fixed for ISO to DCAT-US.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
GIVEN the development work is complete
WHEN the tests are run for MDTranslator
THEN any items that aren't mapping in our default/best case scenario then an error is thrown.
User Story
In order to make sure base use cases are covered, data.gov admins want a complete end-to-end test fixed for ISO to DCAT-US.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
WHEN the tests are run for MDTranslator
THEN any items that aren't mapping in our default/best case scenario then an error is thrown.
Background
Related to analysis performed by metadata experts: https://drive.google.com/drive/u/1/folders/120R3ORnEvF1QFG4IuWch43H8WELtajFA
Security Considerations (required)
None
Sketch
There is already an end-to-end test in place: https://github.com/GSA/mdTranslator/blob/master/test/translator/tc_iso19115_2_datagov_to_dcatus.rb
Some tests are commented out, and probably relate to what is in the spreadsheet.
Ideally we should take a copy of the spreadsheet and work through what is addressed, commit by commit.
This might involve cleaning up our real world example to make it an "ideal" example.
The text was updated successfully, but these errors were encountered: