Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsThe test phase summary report is generated once testing begins. The reporting period of the report is onecalendar week (i.e., Saturday through Friday). The reporting period dates are documented in the report.The cut-off time for statistics to be included in a given weekly report is 4:00 p.m. on Friday. Anystatistics received after 4:00 p.m. on Friday are included in the following week’s report. These reports aredistributed by 4:00 p.m. on Monday.The report contains two sections. The first section provides information for the current week beingreported. The last row of the section always reflects the previous week’s activity and the row aboverepresents the current week’s activity. Presenting the report in this manner, with historical weeklyinformation, may assist management in identifying patterns, if any, regarding weekly activity that may beused to make decisions regarding the project. The second section of the summary report providescumulative (i.e., to-date) summary statistics. The last row of the section always reflects the cumulativetotal as of the previous week’s activity. The row above represents the current week’s cumulative total.The last two rows help determine the progress made in the testing phase for the current week.The metrics available in both sections are reported by business area and functional area with clearidentification of the risks associated with a particular area. Figure 8-82 contains the description offields in the test phase summary report and a sample report generated from our system is provided inFigure 8-83. Both figures together address the minimum information required by the RFP forautomated tracking tool reports.Weekly Summary Report FieldsFieldDescription# Test Cases (TCs) Retested Number of test cases retested in the reporting period# TCs Executed Number of test cases newly executed during the week. (This does not include the retested test count)# Defects Opened Number of new test defects opened for a given module in the reporting period# Defects Closed Number of new test defects tested and closed for a given module in the reporting period# Defects Pending Build Number of defects for which development has completed repairs and the test team is awaiting delivery in order to retest# Defects Delivered Retesting Number of test defects delivered for retesting in the reporting periodTesting Process SummaryTotal # TCsNumber of test cases estimated for completion of testing of a module# TCs Executed Number of test cases executed by module# TCs Passed Number of test cases that have fully met the criteria of pass (i.e. no F1, F2, F3 defects opened against them)# TCs FailedNumber of test cases which failed testing a module and have defects associated (F1, F2, or F3) which prevent the test casefrom passing# Open Defects Number of defects which are currently open for a given module# Closed Defects Number of closed defects which have been resolved and tested for a given moduleFigure 8-82. Weekly Test Summary Report Field Definitions. Team Noridian's test tracking approach isbased on proven, results-oriented experience in implementing Medicaid and Medicare systems.8 | 142