Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

TEST STATUS Reporting System

IP.com Disclosure Number: IPCOM000062517D
Original Publication Date: 1986-Dec-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Dean, TL: AUTHOR [+4]

Abstract

A test status reporting system (TSRS) provides an automated process to record actual versus the planned status for software testing activities. TSRS provides up-to-date information useful in making business decisions in a timely manner. Test case execution plans are set by the individual testers prior to entering a formal test phase of a software development project. Testers enter on TSRS the planned date that the test case will be attempted. After all test cases have been entered, TSRS asks the tester to set a weekly success rate schedule. This success rate is a percentage of all test cases that are expected to be successful each week. The rate is not tied directly to a given test case, but to the total of all test cases.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 1

TEST STATUS Reporting System

A test status reporting system (TSRS) provides an automated process to record actual versus the planned status for software testing activities. TSRS provides up-to-date information useful in making business decisions in a timely manner. Test case execution plans are set by the individual testers prior to entering a formal test phase of a software development project. Testers enter on TSRS the planned date that the test case will be attempted. After all test cases have been entered, TSRS asks the tester to set a weekly success rate schedule. This success rate is a percentage of all test cases that are expected to be successful each week. The rate is not tied directly to a given test case, but to the total of all test cases. Thus, specific test cases do not have to be attempted in a specific order as long as the weekly objectives are met. The percentage rate always has to be higher every week of the test cycle with a final goal of 100% successful test cases. After all information is entered from all of the testers, a summary screen may be viewed to determine current overall status of the project. Below is an example of the status information given for a given project.
.CE UNIQUE TEST CASE ATTEMPTS AS of 08/27/86

WEEK ATTEMPTS % SUCCESSFUL CURRENT

ENDING PLANNED/ACTUAL SUCC BLOCKED PLANNED/ACTUAL STATUS 07/30/86 96 / 99 74 33 / 75 ON SCHED 08/06/86 214 / 183 150 13 46 / 81 BEHIND 08/13/86 221 / 202 175 11 56 / 86 BEHIND 08/20/86 224 / 21...