2009
DOI: 10.1007/978-3-642-04694-0_8
|View full text |Cite
|
Sign up to set email alerts
|

A Concurrency Testing Tool and Its Plug-Ins for Dynamic Analysis and Runtime Healing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
3
3
1

Relationship

1
6

Authors

Journals

citations
Cited by 10 publications
(7 citation statements)
references
References 5 publications
0
7
0
Order By: Relevance
“…The two other programs are real life case studies (see, e.g., for more detail [20]). WebCrawler is a part of an older version of a major IBM production software.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…The two other programs are real life case studies (see, e.g., for more detail [20]). WebCrawler is a part of an older version of a major IBM production software.…”
Section: Methodsmentioning
confidence: 99%
“…Light-weight static analyses may produce many false alarms, many static analyses may be specialised to a narrow class of bugs, and heavy-weight approaches may have troubles with scalability. There also exist approaches that combine static and dynamic analyses in an attempt to suppress their deficiencies [5,20]. A use of static analyses to help search-based testing to focus on interesting parts of the tested code may be another interesting issue for future research.…”
Section: Finding Bugs In Concurrent Softwarementioning
confidence: 99%
“…These approaches are related to what we propose in this article with null operations. Also related to null operations, some techniques introduce variations in the scheduling of multithreaded applications (using sleep()) to avoid race conditions and deadlocks in Java applications [Nir-Buchbinder et al 2008;Křena et al 2009]. While these techniques target solely nondeterministic failures, Automatic Workarounds can deal with deterministic failures as well.…”
Section: Related Work On Self-healing Systems and Software Redundancymentioning
confidence: 99%
“…When dealing with today's real‐life applications, one cannot apply such restrictions. The original coverage metric was therefore slightly modified . The modified metric is referenced to as DUPairs * later.…”
Section: Concurrency Coverage Metrics and Saturation‐based Testingmentioning
confidence: 99%
“…For experimental evaluation of concurrency metrics, the platform called SearchBestie was used to set up and execute tests with the IBM ConTest. The ConTest tool provides a facility for bytecode instrumentation and a listeners infrastructure allowing one to create plug‐ins for collecting various pieces of information about the multi‐threaded Java programmes being executed as well as to easily implement various algorithms for dynamic analyses. The tool is itself able to collect structural coverage metrics (basic blocks, methods) and some concurrency‐related metrics (ConcurPairs, Sync) too.…”
Section: Concurrency Coverage Metrics and Saturation‐based Testingmentioning
confidence: 99%