Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsIf a test case does not pass review, the responsible tester updates the test case to reflect the changes notedduring the review. The test case is once again reviewed to ensure that the modifications are correct.When a DSD document contains use cases that require multiple cooperating systems, those use cases arereserved for the system test phase and tested up to the boundary of the component during unit testing.Using ReqTrace, Team Noridian maintains the new MMIS requirements and use case traceability. Thetest cases are further integrated into ReqTrace where the test case management occurs. When creatingtest cases with ReqTrace, the testers can draw the information from ReqTrace and create thetraceability link from requirements to test cases. The Team can then maintain traceability and ensureproper test case coverage. Furthermore, when requirements are changed, test cases are flagged and arelinked to the change requirements so that the relationship between software, requirements, and testcases is constantly synchronized.A test process must be repeatable. This must be considered throughout the test case construction phase.During iterative design and development, test case refinement and detailing continues as the codedevelops. Test case construction is completed when all requirements can be validated through test cases.Traceability reports helps to determine whether all the requirements are mapped to test cases to completevalidation. When mapping is complete, test case construction is also complete.Test case design is focused on verifying the requirements and determining if the requirements are met.The use cases are the starting point for test case design. Use cases are broken down into manageableand testable test cases so that clear steps are available to validate all test conditions required. Thisapproach, using use cases as a source for test cases, covers all of the requirements that need to bedelivered to the Department.Each test case must meet the following guidelines and goals:• Test cases must be traceable to the requirements: The test case clearly shows the requirement orrequirements that the test case addresses• Test cases must provide clear test instructions: Instructions are clear and precise• Test cases must identify clear prerequisite test conditions: The prerequisite conditions required tosuccessfully execute the test cases and to validate the requirement are defined• Test cases must be written to be tester independent: Any tester can read and execute the test case.• Test cases must provide explicit input and output definition: The input data required to satisfy theoutput to be achieved is explicitly stated• Test cases must clearly state the expected results: The expected results of the test, and the actualresult of the test after it has been executed, are stated so that the two results can be easily compared• Test cases must identify boundary conditions: The test conditions used to test the system withextreme values in the valid range• Test case must identify any required external interfaces: The test case clearly identifies and tests all ofthe interfaces associated with the test case• Test cases must include negative testing: Tests the conditions which the application should not acceptand validate the output• Determine data requirements: Identify the data requirements for the test cycle. Establish internal testdata for test cycles until the converted data is made available for system testing. Test cases must also:• Be reusable at various phases• Have unique identifiers• Be maintainable for the lifetime of the software• Provide a clear list of the environment and profile in which test cases are executed• Follow the test case naming convention: ---8 | 138