/
ClaML Load and Unload Test Case
ClaML Load and Unload Test Case
Overview
Test suite for demonstrating a full ClaML load using the mojos.
Implementation
- ClaMLLoadAndUnloadTest
Execution 1
- Run Updatedb mojo in "create" mode to clear the database
- Run Reindex mojo to clear the indexes
- TEST: verify db has no concepts.
- Run the Claml loader mojo against the sample "config/src/resources/data/icd10.xml" data.
- TEST: verify concepts count.
- TEST: verify release info exists
- TODO: ideally we'd verify other types as well.
- Create a "ICD10" project (name="Sample Project" description="Sample project." terminology=ICD10 version=latest admin.user=admin)
- TEST: verify there is a project with the expected name
- Start an editing cycle for "ICD10"
- TEST: verify there is a release info with the expected name and "planned" flag equal to true.
- Run the Claml loader mojo against the sample "config/src/resources/data/icd10cm.xml" data.
- TEST: verify concepts count.
- TEST: verify release info exists
- TODO: ideally we'd verify other types as well.
- Create a "ICD10CM" project (name="Sample Project" description="Sample project." terminology=ICD10CM version=latest admin.user=admin)
- TEST: verify there is a project with the expected name
- Start an editing cycle for "ICD10CM"
- TEST: verify there is a release info with the expected name and "planned" flag equal to true.
- Remove the terminology "ICD10" with version "latest"
- TEST: verify there is a concepts table with no contents for ICD10.
- Remove the terminology "ICD10CM" with version "latest"
- TEST: verify there is a concepts table with no contents.
- Re-run "createdb" to restore initial state of the database.
Expected Runtime
- 15 min
Notes
This is mostly a test that the sequence of mojo operations works expectedly with light checks of data conditions. It is expected that more comprehensive checking can be done elsewhere.
References/Links
- n/a