Skip to content

Iteration 2 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 Iteration 2 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.

OSCAR Component Testing

  1. Load the OSCAR database with the test data
  2. Export E2E documents - the new feature
  3. Validate the structure of the E2E documents - using XSD and schematron (may need some code writing)
  4. 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.

hQuery Import Component Testing

  1. Create a set of 10,000 test E2E documents from the test data
  2. Manually load the E2E documents into hQuery gateway
  3. Run queries in MongoDB to compare the data with the overall known metrics from the Oracle

Overall System Integration Testing

  1. Set up Mirth, load test dataset in OSCAR db, and run the scenario from start to finish
  2. Run queries in the hQuery composer to verify the known metrics from the Oracle.

Overall System Performance Testing

Time the scenario from start to finish with 10,000 individuals. Consider testing with larger test datasets.

Current Iteration: 13

General Topics

Resources


Previous Iteration: 12

Previous Iteration: 11

Previous Iteration: 10

Previous Iteration: 9

Previous Iteration: 8

Previous Iteration: 7

Previous Iteration: 6

Previous Iteration: 5

Previous Iteration: 4

Previous Iteration: 3

Previous Iteration: 2

Previous Iteration: 1

Previous Iteration: 0

Clone this wiki locally