Dynamic Analysis of Upgrades in C/C++ Software

Pastore, Fabrizio; Mariani, Leonardo; Goffi, Alberto; Manuel, Oriol; Wahler, Michael

doi:10.1109/issre.2012.9

Cited by 18 publications

(24 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The selection strategy implemented in VART keeps the cost of monitoring, inference and model checking under control, avoiding scalability issues in practice [48].…”

Section: Detecting Dynamic Propertiesmentioning

confidence: 99%

See 1 more Smart Citation

Verification-aided regression testing

Pastore

Mariani

Hyvärinen

et al. 2014

Proceedings of the 2014 International Symposium on Software Testing and Analysis

Self Cite

View full text Add to dashboard Cite

In this paper we present Verification-Aided Regression Testing (VART), a novel extension of regression testing that uses model checking to increase the fault revealing capability of existing test suites. The key idea in VART is to extend the use of test case executions from the conventional direct fault discovery to the generation of behavioral properties specific to the upgrade, by (i) automatically producing properties that are proved to hold for the base version of a program, (ii) automatically identifying and checking on the upgraded program only the properties that, according to the developers' intention, must be preserved by the upgrade, and (iii) reporting the faults and the corresponding counter-examples that are not revealed by the regression tests. Our empirical study on both open source and industrial software systems shows that VART automatically produces properties that increase the effectiveness of testing by automatically detecting faults unnoticed by the existing regression test suites.

show abstract

“…The selection strategy implemented in VART keeps the cost of monitoring, inference and model checking under control, avoiding scalability issues in practice [48].…”

Section: Detecting Dynamic Propertiesmentioning

confidence: 99%

“…Jadet statically identifies patterns of method invocations and discovers anomalous sequence of method calls [61]. Radar dynamically generates and checks program properties and control-flow models that capture the behavior of software units, such as program functions [48].…”

Section: Related Workmentioning

confidence: 99%

Verification-aided regression testing

Pastore

Mariani

Hyvärinen

et al. 2014

Proceedings of the 2014 International Symposium on Software Testing and Analysis

Self Cite

View full text Add to dashboard Cite

show abstract

“…The FSA could be part of the program specification or could be automatically inferred by monitoring test case execution, as it usually happens in anomaly detection techniques that compare passing and failing executions [3], [7].…”

Section: Ava: Automata Violations Analyzermentioning

confidence: 99%

“…For instance, BCT [3] and RADAR [7] use both models on data values and operation sequences. Probabilistic Program Dependency Graph combines bayesian probabilities with structural information to capture anomalies in the flow of the data [21].…”

Section: B Model Based Approachesmentioning

confidence: 99%

AVA: Supporting Debugging with Failure Interpretations

Pastore

Mariani

2013

2013 IEEE Sixth International Conference on Software Testing, Verification and Validation

Self Cite

View full text Add to dashboard Cite

Abstract-Several debugging techniques can be used to automatically identify the code fragments or the runtime events likely responsible of a failure. These techniques are useful, but can help reducing the debugging effort only to a given extent. In fact, even when these techniques are successful, software developers still have to invest a lot of effort in understanding if and why something detected as suspicious is really wrong.In this paper we present the tool implementing the AVA technique. AVA, compared to other approaches dedicated to automatic debugging, in addition to automatically identifying the events likely responsible of a failure, generates an explanation about why these events have been considered suspicious. This explanation can be used by developers to quickly discard imprecise outputs and more effectively work on the relevant anomalies.

show abstract

“…These models are used to assess the impact and the correctness of upgrades [19]. Validation has taken place both on Linux and internal ABB code.…”

Section: B Dynamic Analysis Of Software Upgradesmentioning

confidence: 99%

PINCETTE - Validating Changes and Upgrades in Networked Software

Chockler

Denaro

Ling

et al. 2013

2013 17th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Networked control systems ensure today's dependability of essential infrastructure such as water, electricity and transportation. Over a life cycle of tens of years, maintenance upgrades of the software running these control systems must not introduce new software errors or otherwise break existing functionality. The EU FP7 project PINCETTE addresses this challenge by employing a combination of static and dynamic software verification tools. The changes between versions are used both as guidance for improving efficiency of software verification, and also to define new notions of correctness. We report on current progress and initial validation results by our industrial partners.

show abstract

Dynamic Analysis of Upgrades in C/C++ Software

Cited by 18 publications

References 23 publications

Verification-aided regression testing

Verification-aided regression testing

AVA: Supporting Debugging with Failure Interpretations

PINCETTE - Validating Changes and Upgrades in Networked Software

Contact Info

Product

Resources

About