How to judge testing progress

It is usual to base the assessment of software testing progress on a coverage measure such as code coverage or specification coverage, or on the percentage of the input domain exercised. In this paper it is argued that these characteristics do not provide good indications of the degree to which the...

Full description

Saved in:
Bibliographic Details
Published in:Information and software technology Vol. 46; no. 5; pp. 323 - 328
Main Author: Weyuker, Elaine J.
Format: Journal Article
Language:English
Published: Amsterdam Elsevier B.V 15.04.2004
Elsevier Science Ltd
Subjects:
Computer programming
Distributed processing
Operational distribution
Software
Software testing
Studies
Test data adequacy
Test progress
Testing
Software testing
Test data adequacy
Test progress
Operational distribution
ISSN:0950-5849, 1873-6025
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:It is usual to base the assessment of software testing progress on a coverage measure such as code coverage or specification coverage, or on the percentage of the input domain exercised. In this paper it is argued that these characteristics do not provide good indications of the degree to which the software has been tested. Instead we propose that the assessment of testing progress be based on the total percentage of the probability mass that corresponds to the test cases selected and run. To do this, it is necessary to collect data that profiles how the software will be used once it is operational in the field. By so doing, we are able to accurately determine how much testing has been done, and whether it has met the standards of completeness for the product under consideration.
Bibliography:SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 14
ISSN:0950-5849
1873-6025
DOI:10.1016/j.infsof.2003.09.008