2015 IEEE/ACM 37th IEEE International Conference on Software Engineering 2015
DOI: 10.1109/icse.2015.78
|View full text |Cite
|
Sign up to set email alerts
|

DASE: Document-Assisted Symbolic Execution for Improving Automated Software Testing

Abstract: Abstract-We propose and implement a new approach, Document-Assisted Symbolic Execution (DASE), to improve automated test generation and bug detection. DASE leverages natural language processing techniques and heuristics to analyze program documentation to extract input constraints automatically. DASE then uses the input constraints to guide symbolic execution to focus on inputs that are semantically more important.We evaluated DASE on 88 programs from 5 mature real-world software suites: COREUTILS, FINDUTILS, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
19
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 24 publications
(21 citation statements)
references
References 56 publications
0
19
0
Order By: Relevance
“…Note that our coverage results for klee are different from klee's paper. As discussed and reported in previous works [12,41], the coverage differences are mainly due to the major code changes of klee, an architecture change from 32-bit to 64-bit, and whether manual system call failures are introduced. angr shares the same limitation as klee requiring to maintain multiple states and provide models for execution environment, while it shares the disadvantage of crete in having no access to semantics information.…”
Section: Discussionmentioning
confidence: 67%
See 2 more Smart Citations
“…Note that our coverage results for klee are different from klee's paper. As discussed and reported in previous works [12,41], the coverage differences are mainly due to the major code changes of klee, an architecture change from 32-bit to 64-bit, and whether manual system call failures are introduced. angr shares the same limitation as klee requiring to maintain multiple states and provide models for execution environment, while it shares the disadvantage of crete in having no access to semantics information.…”
Section: Discussionmentioning
confidence: 67%
“…In this section, we present the evaluation results of crete from its application to GNU Coreutils [38] [5,12,41]. This is why we chose it as the benchmark to compare with klee and angr.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Wiederseiner [65] uses "elfdump" to generates the symbol table of the code-base and source code line data of the ELF file. Wong [66] uses "elfdump", "objdump" and "readelf" to extract 2 This work is licensed under a Creative Commons Attribution 4.0 License. For more information, see https://creativecommons.org/licenses/by/4.0/.…”
Section: A Overviewmentioning
confidence: 99%
“…Previous work has applied NLP techniques to related problems. WHYPER (Pandita et al 2013) and DASE (Wong et al 2015) apply NLP techniques to identify sentences that describe the need for a given permission in a mobile application description and extract command-line input constraints from manual pages, respectively. The work in (Witte et al 2008) used documentation and source code to create an ontology allowing the cross-linking of software artifacts represented in code and natural language on a semantic level.…”
Section: Related Workmentioning
confidence: 99%