Distributed expectation-driven residual testing

Naslavsky, Leila

doi:10.1049/ic:20040350

Cited by 4 publications

(1 citation statement)

References 10 publications

(8 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This type of testing is motivated by the fact that software products are typically released with less than 100% coverage, so testers assume that any potential defects in the untested code (the residue) occur so rarely so as not to bear consideration. Much of the research in this area to date has focused on measuring the coverage provided by this approach by looking at untested residue [38] [43] or by comparing the coverage to specifications [37]. However, this work does not consider the actual execution of tests in the deployment environment, as we describe here.…”

Section: Related Workmentioning

confidence: 99%

Quality Assurance of Software Applications Using the In Vivo Testing Approach

Murphy

Kaiser

et al. 2009

2009 International Conference on Software Testing Verification and Validation

View full text Add to dashboard Cite

Software products released into the field typically have some number of residual defects that either were not detected or could not have been detected during testing. This may be the result of flaws in the test cases themselves, incorrect assumptions made during the creation of test cases, or the infeasibility of testing the sheer number of possible configurations for a complex system; these defects may also be due to application states that were not considered during lab testing, or corrupted states that could arise due to a security violation. One approach to this problem is to continue to test these applications even after deployment, in hopes of finding any remaining flaws. In this paper, we present a testing methodology we call in vivo testing, in which tests are continuously executed in the deployment environment. We also describe a type of test we call in vivo tests that are specifically designed for use with such an approach: these tests execute within the current state of the program (rather than by creating a clean slate) without affecting or altering that state from the perspective of the end-user. We discuss the approach and the prototype testing framework for Java applications called Invite. We also provide the results of case studies that demonstrate Invite's effectiveness and efficiency.

show abstract

Section: Related Workmentioning

confidence: 99%