Formal analysis of the effectiveness and predictability of random testing
Proceedings of the 19th international symposium on Software testing and analysis
Black-box system testing of real-time embedded systems using random and search-based testing
ICTSS'10 Proceedings of the 22nd IFIP WG 6.1 international conference on Testing software and systems
Increasing functional coverage by inductive testing: a case study
ICTSS'10 Proceedings of the 22nd IFIP WG 6.1 international conference on Testing software and systems
Testing container classes: random or systematic?
FASE'11/ETAPS'11 Proceedings of the 14th international conference on Fundamental approaches to software engineering: part of the joint European conferences on theory and practice of software
Proceedings of the 2012 International Symposium on Software Testing and Analysis
Grouping target paths for evolutionary generation of test data in parallel
Journal of Systems and Software
Achieving scalable model-based testing through test case diversity
ACM Transactions on Software Engineering and Methodology (TOSEM)
Evaluating test suite characteristics, cost, and effectiveness of FSM-based testing methods
Information and Software Technology
| Hi-index | 0.00 |
In the presence of an internal state, often it is required a sequence of function calls to test software. In fact, to cover a particular branch of the code, a sequence of previous function calls might be required to put the internal state in the appropriate configuration. Internal states are not only present in object-oriented software, but also in procedural software(e.g., static variables in C programs). In the literature, there are many techniques to test this type of software. However, to our best knowledge, the properties related to choosing the length of these sequences have received only little attention in the literature. In this paper, we analyse the role that the length plays in software testing, in particular branch coverage. We show that on “difficult” software testing benchmarks longer test sequences make their testing trivial. Hence, we argue that the choice of the length of the test sequences is very important in software testing.