Add mCODE read profile tests created by the testscript-generator and update validation functionality to support
New behavior
profiles in TestScripts reference the canonical URL of a profile, not the StructureDefinition location. StructureDefinition locations must be specified in the config file (relative file path or web location). These are loaded and the corresponding urls are listed as 'available' for use in profiles.
during runnable creation, checks to see if a profile canonical url is in the list of available profiles.
Code changes
fixed bug that was preventing variable options from loading (:variable -> "variable")
implemented updated profile load logic
added mCODE-specific tests and profile files
updated unit tests for TestScriptEngine and Runnable
profiles the external validator is already aware of are available for validation use, as are profiles in TestScripts for which the canonical url resolves to a StructureDefinition
no profile loading to external validator during profile conformance check (done earlier)
command line and config file options
Testing guidance
bundle exec bin/testscript_engine execute --config config-multipleMCODE.yml
Not all will succeed, but at least some should pass
bundle exec bin/testscript_engine execute --profile Profiles/mCODE spec/profiles/structuredefinition-us-core-patient.json --testscript_name UsMCODECancerDiseaseStatusReadProfile
For command line - profiles should be loaded
Summary
Add mCODE read profile tests created by the testscript-generator and update validation functionality to support
New behavior
Code changes
:variable->"variable")Testing guidance
bundle exec bin/testscript_engine execute --config config-multipleMCODE.ymlNot all will succeed, but at least some shouldpassbundle exec bin/testscript_engine execute --profile Profiles/mCODE spec/profiles/structuredefinition-us-core-patient.json --testscript_name UsMCODECancerDiseaseStatusReadProfileFor command line - profiles should be loaded