A systematic review of software robustness

Shahrokni, Ali; Feldt, Robert

doi:10.1016/j.infsof.2012.06.002

Cited by 77 publications

(40 citation statements)

References 83 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As these methods do not have access to a speci cation or model, they rely on other techniques than speci ed test oracles [4]. For example, for certain outputs implicit oracles can be used: a segmentation fault is always a sign of a robustness fault [38], while nding a bu er over ow means a security fault [7]. Other implicit oracles include general contracts like o.equals(o) is true [29].…”

Section: Related Workmentioning

confidence: 99%

Classifying generated white-box tests: an exploratory study

Honfi

Micskei

2019

Software Qual J

View full text Add to dashboard Cite

White-box test generator tools rely only on the code under test to select test inputs, and capture the implementation's output as assertions. If there is a fault in the implementation, it could get encoded in the generated tests. Tool evaluations usually measure fault-detection capability using the number of such fault-encoding tests. However, these faults are only detected, if the developer can recognize that the encoded behavior is faulty. We designed an exploratory study to investigate how developers perform in classifying generated white-box test as faulty or correct. We carried out the study in a laboratory se ing with 54 graduate students. e tests were generated for two open-source projects with the help of the IntelliTest tool. e performance of the participants were analyzed using binary classi cation metrics and by coding their observed activities. e results showed that participants incorrectly classi ed a large number of both fault-encoding and correct tests (with median misclassi cation rate 33% and 25% respectively). us the real fault-detection capability of test generators could be much lower than typically reported, and we suggest to take this human factor into account when evaluating generated white-box tests.

show abstract

Section: Related Workmentioning

confidence: 99%

Classifying generated white-box tests: an exploratory study

Honfi

Micskei

2019

Software Qual J

View full text Add to dashboard Cite

show abstract

“…When possible, the analysis would move more toward quantitative assessments and to include more attributes and factors. For robustness, we could consider other robustness aspects from the literature [18] as well. A company with experience in working with SBST systems, for example, may be able to estimate the cost of implementing GödelTest quite accurately, as well as have a clearer understanding of the effect the implementation would have on its products.…”

Section: Sbst Experiencementioning

confidence: 99%

A Testability Analysis Framework for Non-functional Properties

Felderer

Marculescu

Neto

et al. 2018

2018 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

Self Cite

View full text Add to dashboard Cite

show abstract

“…In addition to self-stabilization, there exist several different notions of robustness for discrete systems. For example, in [24] a systematic literature review is presented, where the authors distill and categorize more than 9000 papers on software robustness. In the following, we focus on the few approaches that provide quantitative measures of robustness for discrete systems and thereby are close to the framework presented in this paper.…”

Section: Related Workmentioning

confidence: 99%

Abstracting and refining robustness for cyber-physical systems

Rungger

Tabuada

2014

Proceedings of the 17th International Conference on Hybrid Systems: Computation and Control

View full text Add to dashboard Cite

According to the IEEE standard glossary of software engineering, robustness is the degree to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions. In this paper we present a design methodology for robust cyber-physical systems (CPS) based on a notion of robustness for CPS termed input-output dynamical stability. It captures two intuitive aims of a robust design: bounded disturbances have bounded consequences and the effect of sporadic disturbances disappears as time progresses. Our framework to synthesize robust CPS is based on an abstraction and refinement procedure, where the robust CPS is obtain through the refinement of a design for an abstraction of the concrete CPS. The soundness of the approach is ensured through the use of several novel notions of simulation relation introduced in this paper.

show abstract

A systematic review of software robustness

Cited by 77 publications

References 83 publications

Classifying generated white-box tests: an exploratory study

Classifying generated white-box tests: an exploratory study

A Testability Analysis Framework for Non-functional Properties

Abstracting and refining robustness for cyber-physical systems

Contact Info

Product

Resources

About