Testing Documentation Requirements

40.3.8 - Testing Documentation Requirements (Rev. 97, Issued: 01-15-16, Effective: 09-21-15, Implementation: 09-21-15) 1. The SSM, STC, and MAC shall maintain documentation that fully demonstrates the requirements of this transmittal were met for each quarterly release. At a minimum the SSM, Beta tester, and MAC shall maintain the following test documentation to demonstrate full compliance: • Test Requirement and Test Case repository with traceability; • Test Log; • Test Status for the execution (run) of each test case (i.e., Pass, Fail, Not Run); • Actual Results for the run of each test case in which the actual results did not match the expected results; and • Documented proof of each test run, i.e., screen shots, scheduler job logs, etc. 2. The SSM, STC, and MAC shall: • Maintain all test documentation for the four quarterly releases prior to the current release under test. The documentation must be available for review by CMS (or its agent). • Document all software defects (problems) within the CMS specified repository such as INFOMAN. 3. The SSM shall communicate all confirmed software defects (problems) and fixes directly to CMS in writing through their CMS Maintenance Lead/(GTL) or other designee as specified by the CMS Project Officer. 4. A/B, DME MACs shall provide any testing documentation to their CMS regional office upon request. Additional requirements for selected shared system maintainers, STC, and CWF hosts may be contained in these organizations' individual contracts. Electronic screen shots may be incorporated/attached into the results of ALM has proof of online results. Test Log requirements may be fulfilled by correctly using the ALM “run” feature as outlined in the Quarterly Release Test Management User Guide.