2013
DOI: 10.1002/stvr.1495
|View full text |Cite
|
Sign up to set email alerts
|

Handling test length bloat

Abstract: SUMMARYThe length of test cases is a little investigated topic in search-based test generation for object-oriented software, where test cases are sequences of method calls. While intuitively longer tests can achieve higher overall code coverage, there is always the threat of bloat -a complex phenomenon in evolutionary computation, where the length abnormally grows over time. In this paper, we show that bloat indeed also occurs in the context of test generation for object-oriented software. We present different… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2014
2014
2020
2020

Publication Types

Select...
3
2
1

Relationship

3
3

Authors

Journals

citations
Cited by 18 publications
(6 citation statements)
references
References 40 publications
0
6
0
Order By: Relevance
“…This is so that the initial execution of the predicate, with some specific true/false evaluation, is not lost in the process of pursuing the alternative outcome. As longer test suites require more memory and execution time, controlling the length of the test suite can improve search performance [9]. Therefore, when deciding which test suites should proceed into the population for the next iteration of the search, EvoSuite prefers shorter test suites to test suites with the same fitness but whose test cases of composed of cumulatively higher number of statements.…”
Section: Genetic Algorithm Search For Test Suitesmentioning
confidence: 98%
“…This is so that the initial execution of the predicate, with some specific true/false evaluation, is not lost in the process of pursuing the alternative outcome. As longer test suites require more memory and execution time, controlling the length of the test suite can improve search performance [9]. Therefore, when deciding which test suites should proceed into the population for the next iteration of the search, EvoSuite prefers shorter test suites to test suites with the same fitness but whose test cases of composed of cumulatively higher number of statements.…”
Section: Genetic Algorithm Search For Test Suitesmentioning
confidence: 98%
“…However, the implementation of the GA in the underlying EVOSUITE ranks two individuals by their size if their fitness values are equal, such that smaller test sets have a higher probability of being selected for reproduction. Consequently, during phases of the search where there is no exploration of new coverage or adequacy, redundant test cases are removed from the test sets, and thus behavioural adequacy does not lead to bloat .…”
Section: Discussionmentioning
confidence: 88%
“…Out of this population, the GA selects individuals for reproduction, where individuals with better fitness values have a higher probability of being selected. To avoid undesired growth of the population (bloat ), individuals with identical fitness are ranked by size, such that smaller test sets are more likely to be selected. Crossover and mutation are applied with given probabilities, where crossover exchanges individual tests between two parent test sets, and mutation changes existing tests or adds new tests to a test set.…”
Section: Generating Adequate Test Setsmentioning
confidence: 99%
“…As longer test suites require more memory and execution time, controlling the length of the test suite can improve search performance . Therefore, when deciding which test suites should proceed into the population for the next iteration of the search, E VO S UITE prefers shorter test suites to test suites with the same fitness but are composed of a higher number of statements.…”
Section: Search‐based Test Generationmentioning
confidence: 99%
“…As longer test suites require more memory and execution time, controlling the length of the test suite can improve search performance [35].…”
Section: Genetic Algorithm Search For Test Suitesmentioning
confidence: 99%