Browse Prior Art Database

Hierarchical Test Status Production System Disclosure Number: IPCOM000175711D
Original Publication Date: 2008-Oct-20
Included in the Prior Art Database: 2008-Oct-20
Document File: 10 page(s) / 66K

Publishing Venue



A method to automatically build hierarchical test status information useful to many layers of management from low-level information provided direct from test systems

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

Page 1 of 10

Hierarchical Test Status Production System

In a development organisation test results are normally stored and presented in a hierarchical fashion so that
engineers concerned with the day to day running of tests can enter and refer to detailed information about a small part of
the project and team leaders and managers can see an overview of test status of larger areas of the project.

    Taking the detailed information provided by engineers and consolodating it to overviews for various levels of
management is a time consuming activity that must be repeated regularly.

The information required at each level typically comprises:
Name of test program or item

Version of build under test
List or number items yet to be run
List or number of items run
List or number of items passed
List or number of items failed and have not been analysed List or number of items failed and have been analysed List or number of defects opened for the current item
List or total of expected or actual durations for each item Known solution:

    Typically an engineer will create overviews by reviewing low-level test results and summing such information as
number of teststeps passed and number of teststeps run.

Drawback of known solution:

    The work of summarising and presenting test status takes a considerable amount of time of all workers at all
levels in a test department which is a large drain on resourse.

    In a typical organisation all salient information from each test run is stored in a row of a database table.

Data from that table would typically be presented in a web-page.

    In this invention the database table will also hold rows to represent the status of the test work that each member
of the test management is responsible for. Each of these higher level rows hold a list of lower
level rows they represent. Thus the rows reflect the hierarchy of the test management organisation.

Also in this invention software programs are provided which:
1. Summarises the test status of all rows below each in the hierarchy and inserts it in that row.

This software will run periodically or on demand. In this way test status that
is inserted at the bottom of the hierarchy of database table rows percolates up to the top level automatically.
2. Displays any row in the database table as a web page. The web page also provides links to
displays rows above and below in the hierarchy.
3. Allows a manager to specify that a summary of a given set of testruns or other summaries is required.
4. Allows anyone to drill down through the hierachy of test status information.

Page 2 of 10

The advantages of this solution are:
1. The work required to present test status is greatly reduced.
2. Management will have more up-to-date test status information at their disposal.

Terms used in this description:

    Defect - An item which records all technical information about a fault discovered in a system under test.

    Test script - A software program that performs a set of test steps on the s...