2015 IEEE 8th International Conference on Software Testing, Verification and Validation (ICST) 2015
DOI: 10.1109/icst.2015.7102587
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating Symbolic Execution-Based Test Tools

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
1

Year Published

2016
2016
2019
2019

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 17 publications
(20 citation statements)
references
References 18 publications
0
19
1
Order By: Relevance
“…Model based software and systems engineering [114,115,121,122]: techniques and tools for requirements engineering, design, analysis, optimization, deployment, testing [116], maintenance, domain-specific modeling languages, model transformations [123] and code generation). Formal methods [118,119,124] The Intelligent Systems Group is competent and dedicated to research in ambient intelligent systems [127], heterogeneous information processing, data analysis, medical image analysis [126], modeling complex systems [128], bioinformatics, biomedical informatics [125].…”
Section: Main Research Fieldsmentioning
confidence: 99%
“…Model based software and systems engineering [114,115,121,122]: techniques and tools for requirements engineering, design, analysis, optimization, deployment, testing [116], maintenance, domain-specific modeling languages, model transformations [123] and code generation). Formal methods [118,119,124] The Intelligent Systems Group is competent and dedicated to research in ambient intelligent systems [127], heterogeneous information processing, data analysis, medical image analysis [126], modeling complex systems [128], bioinformatics, biomedical informatics [125].…”
Section: Main Research Fieldsmentioning
confidence: 99%
“…Our initial paper concentrated on tools using symbolic execution. This paper extends the scope of the work by including search‐based and random testing; extending the features with handling environment, reflection, multi‐threading, and native code; adding a new tool and a previously manually evaluated tool to the automatic evaluation framework; performing a large number of experiments; and extending the analysis from only code coverage to several other properties.…”
Section: Introductionmentioning
confidence: 99%
“…The resulting test cases may thus set the input objects to states not reachable through the programming interfaces [17], and may result in test cases not yielding feasible behaviours of the program. For example, the test code of Figure 4 assigns the numeric value 7 to list.size (line 9), which is a correct solution for the constraint List.size>3 in the path condition, but violates the invariant of the current list structure that contains only 4 nodes (excluding the sentinel node list.header).…”
Section: Building Heapmentioning
confidence: 99%
“…Symbolic techniques, like JPF [53], jPET [1], JBSE [10,11], and BLISS [48], identify input states to execute code elements, but rely on direct heap manipulation to instantiate the data structures that comprise these input states. Test cases that instantiate the input data structures by directly manipulating the heap memory may either not compile, since they directly access private fields, or create unreachable program states, since they bypass the program functions that preserve the invariants [17], and are often hardly readable and understandable by developers [18].…”
Section: Introductionmentioning
confidence: 99%