Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria

Testing a software system consists of executing it over a suitable sample of input data and then checking if the output produced matches what was expected. Testing is widely used to enhance software quality, and, specifically, to uncover bugs that are inevitably introduced during the software develo...

Descripción completa

Guardado en:
Detalles Bibliográficos
Autor principal: Marré, Martina
Formato: Articulo Contribucion a revista
Lenguaje:Inglés
Publicado: 1998
Materias:
Acceso en línea:http://sedici.unlp.edu.ar/handle/10915/135584
https://publicaciones.sadio.org.ar/index.php/EJS/article/view/139
Aporte de:
id I19-R120-10915-135584
record_format dspace
institution Universidad Nacional de La Plata
institution_str I-19
repository_str R-120
collection SEDICI (UNLP)
language Inglés
topic Ciencias Informáticas
spanning sets of entities
coverage testing
spellingShingle Ciencias Informáticas
spanning sets of entities
coverage testing
Marré, Martina
Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
topic_facet Ciencias Informáticas
spanning sets of entities
coverage testing
description Testing a software system consists of executing it over a suitable sample of input data and then checking if the output produced matches what was expected. Testing is widely used to enhance software quality, and, specifically, to uncover bugs that are inevitably introduced during the software development process. One of the most difficult problems in testing is knowing when to stop the testing process. On the one hand, it is not possible in general to give an answer to whether a test suite guarantees the absence of faults. On the other hand, we need a way to limit the cost of testing. Therefore, it is useful to have criteria to determine when a program has been tested enough. Ideally, the testing process should be planned in advance. However, in practice the tests are incorporated little by little, until some adequacy criterion is satisfied. In particular, different coverages can be used to determine when the program has been tested enough. The idea is to guarantee that each statement, decision or other feature of the program has been executed at least once under some test. A major problem is that testing takes a considerable amount of the time and resources spent on producing software [?]. Therefore, it would be useful to have ways 1. to reduce the cost of testing, and 2. to estimate this cost. In particular, the number of tests to be executed impacts heavily on the cost of testing. In fact, the time and resources needed for testing increase as the number of test cases increases. Hence, to reduce the cost of testing, the number of test cases generated to satisfy a selected test criterion should be as small as possible. Moreover, a bound on the number of tests that have to be performed to satisfy a selected test strategy can be used by managers and testers to estimate the effort needed to carry out the tests.
format Articulo
Contribucion a revista
author Marré, Martina
author_facet Marré, Martina
author_sort Marré, Martina
title Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
title_short Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
title_full Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
title_fullStr Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
title_full_unstemmed Program Flow Analysis for Reducing and Estimating the Cost of Test Coverage Criteria
title_sort program flow analysis for reducing and estimating the cost of test coverage criteria
publishDate 1998
url http://sedici.unlp.edu.ar/handle/10915/135584
https://publicaciones.sadio.org.ar/index.php/EJS/article/view/139
work_keys_str_mv AT marremartina programflowanalysisforreducingandestimatingthecostoftestcoveragecriteria
bdutipo_str Repositorios
_version_ 1764820455490846721