-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 1 Test Plan
jujaga edited this page Oct 31, 2012
·
2 revisions
This wiki page covers the outline of how the system and components for SCOOP Iteration1 will be tested. This component and system testing is in addition to any unit tests authored during the development process.
As a prerequisite we'll need to create an Oracle. This can be accomplished by loading the test data in a database, then characterizing it by a set of metrics.For example, how many males? how many females? How many instances of certain medication codes? etc.
- Load the OSCAR database with the test data (10,000 individuals)
- Export E2E documents - the new feature
- Validate the structure of the E2E documents - using XSD and schematron (may need some code writing)
- Validate the content of the E2E documents - write some custom XML processing software to compare the XML files to the known metrics generated from the Oracle.
- Create a set of 10,000 test E2E documents from the test data
- Manually load the E2E documents into hQuery gateway
- Run queries in MongoDB to compare the data with the overall known metrics from the Oracle
- Set up Mirth, load test dataset in OSCAR db, and run the scenario from start to finish
- Run queries in the hQuery composer to verify the known metrics from the Oracle.
Time the scenario from start to finish with 10,000 individuals. Consider testing with larger test datasets.
SCOOP is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
- SCOOP Overall Design
- SCOOP Actors
- User Stories and Use Case Maps
- System Architecture
- Development Process
- Prototypical Questions
- Current Meds vs Med List
- Data Enrichment Design
- Data Visualization
- Deployment Architecture
- EMR-2-EMR (E2E)
- OSCAR Setup
- Gateway & Hub Setup
- OSCAR Development Notes
- OSCAR DB Table Notes
- Coding Standards
- Mongodb Notes
- Server Configuration
- PDC Gateway Server
- Iteration Overview
- Feature List
- Architecture
- Requirements
- Visualization Requirements
- Test Specification