Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Concolic_testing> ?p ?o. }
Showing items 1 to 21 of
21
with 100 items per page.
- Concolic_testing abstract "Concolic testing (a portmanteau of concrete and symbolic), first coined in the paper "CUTE: A concolic unit testing engine for C" by Koushik Sen, Darko Marinov, and Gul Agha, is a hybrid software verification technique that performs symbolic execution, a classical technique that treats program variables as symbolic variables, along a concrete execution (testing on particular inputs) path. Symbolic execution is used in conjunction with an automated theorem prover or constraint solver based on constraint logic programming to generate new concrete inputs (test cases) with the aim of maximizing code coverage. Its main focus is finding bugs in real-world software, rather than demonstrating program correctness.A description and discussion of the concept of concolic testing was introduced in DART by Patrice Godefroid, Nils Klurland, and Koushik Sen. CUTE further extended the idea of concolic testing to data structures. Another tool, called EGT (renamed to EXE and later improved and renamed to KLEE), based on similar ideas was independently developed by Cristian Cadar and Dawson Engler in 2005, and published in 2005 and 2006. PathCrawler first proposed to perform symbolic execution along a concrete execution path, but unlike concolic testing PathCrawler does not simplify complex symbolic constraints using concrete values. These tools (DART and CUTE, EXE) applied concolic testing to unit testing of C programs and concolic testing was originally conceived as a white box improvement upon established random testing methodologies. The technique was later generalized to testing multithreaded Java programs with jCUTE, and unit testing programs from their executable codes (tool OSMOSE). It was also combined with fuzz testing and extended to detect exploitable security issues in large-scale x86 binaries by Microsoft Research's SAGE.The concolic approach is also applicable to model checking. In a concolic model checker, the model checker traverses states of the model representing the software being checked, while storing both a concrete state and a symbolic state. The symbolic state is used for checking properties on the software, while the concrete state is used to avoid reaching unreachable state. One such tool is ExpliSAT by Sharon Barner, Cindy Eisner, Ziv Glazberg, Daniel Kroening and Ishai Rabinovitz".
- Concolic_testing thumbnail Concolic_testing_example.svg?width=300.
- Concolic_testing wikiPageExternalLink crest.
- Concolic_testing wikiPageExternalLink cute.
- Concolic_testing wikiPageExternalLink pathcrawler-online.com.
- Concolic_testing wikiPageExternalLink pathcrawler-online.com.
- Concolic_testing wikiPageExternalLink pex.
- Concolic_testing wikiPageExternalLink jalangi.
- Concolic_testing wikiPageExternalLink janala2.
- Concolic_testing wikiPageID "25029425".
- Concolic_testing wikiPageRevisionID "577869596".
- Concolic_testing hasPhotoCollection Concolic_testing.
- Concolic_testing subject Category:Automated_theorem_proving.
- Concolic_testing comment "Concolic testing (a portmanteau of concrete and symbolic), first coined in the paper "CUTE: A concolic unit testing engine for C" by Koushik Sen, Darko Marinov, and Gul Agha, is a hybrid software verification technique that performs symbolic execution, a classical technique that treats program variables as symbolic variables, along a concrete execution (testing on particular inputs) path.".
- Concolic_testing label "Concolic testing".
- Concolic_testing sameAs m.09gqkz2.
- Concolic_testing sameAs Q5158734.
- Concolic_testing sameAs Q5158734.
- Concolic_testing wasDerivedFrom Concolic_testing?oldid=577869596.
- Concolic_testing depiction Concolic_testing_example.svg.
- Concolic_testing isPrimaryTopicOf Concolic_testing.
