Expectation | Details | Owner |
---|
Testing Timeline | - CMS will provide a detailed testing timeline and schedule.
| CMS |
Creation of use cases | - Create possible use cases needed to properly test the change.
- Utilize testing template provided here: Testing Feedback Process
| EDI |
Selection and create of test data for testing | - Create the data required to test the use cases documented above.
- Transmit a representative sampling of the types of transactions that are normally submitted. This should include both negative and positive use cases.
- Baseline file will form the base for testing a change from the initial data value to a subsequent change to that data value.
Example: Testing code 11225 requires a transaction whereby the patient is discharged and then subsequently readmitted. The baseline file would process the patient's discharge reason. The change file would than readmit the patient with a new admission code.
| EDI |
Execution of test cases | - Includes both baseline and change file in order to fully test the use case.
| EDI |
Review feedback file and analyze results. | - Retrieve and review feedback files for each transmission.
- Perform an analysis of the data to see why a test case failed. Consider if this is a EDSM issue or data entry issue.
- Submit results to ADO based on process documented here.
- Work with ADO to review any EDSM related issues.
| EDI/ADO |
Bug fixing and regression testing. | - If the record was rejected, correct the data and resubmit the file.
| EDI |
Sign off on testing | - Provide a final sign-off to provide a Go / No-Go recommendation for production implementation.
| EDI |