Reducing wasted development time via continuous testing
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Testing is often performed frequently during development to ensure software reliability by catching regression errors quickly. However, stopping frequently to test also wastes time by holding up development progress. User studies on real development projects indicate that these two sources of wasted time account for 10-15% of development time. These measurements use a novel technique for computing the wasted extra development time incurred by a delay in discovering a regression error. We present a model of developer behavior that infers developer beliefs from developer behavior, and that predicts developer behavior in new environments - in particular, when changing testing methodologies or tools to reduce wasted time. Changing test ordering or reporting reduces wasted time by 4-41% in our case study. Changing the frequency with which tests are run can reduce wasted time by 31-82% (but developers cannot know the ideal frequency except after the fact). We introduce and evaluate a new technique, continuous testing, that uses spare CPU resources to continuously run tests in the background, providing rapid feedback about test failures as as source code is edited. Continuous testing reduced wasted time by 92-98%, a substantial improvement over the other approaches. We have integrated continuous testing into two development environments, and are beginning user studies to evaluate its efficacy. We believe it has the potential to reduce the cost and improve the efficacy of testing and, as a result, to improve the reliability of delivered systems.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Plans and the structure of behavior.
Miller, G. A., Galanter, E., & Pribram, K. H. (1960) · doi:10.1037/10039-000 · Cited by 4,630
Cited by
Continuous software engineering: A roadmap and agenda
Fitzgerald, B., & Stol, K.-J. (2017) · Journal of Systems and Software · doi:10.1016/j.jss.2015.06.063 · Cited by 723
Continuous software engineering and beyond: trends and challenges
Fitzgerald, B., & Stol, K.-J. (2014) · Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering · doi:10.1145/2593812.2593813 · Cited by 212
Early Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82
“Continuous testing [36], [37], [38], [18] applies the same idea to testing: it uses excess cycles on a developer’s workstation to continuously run regression tests in the background.”
MethodSelf-citationA large-scale longitudinal study of flaky tests
Lam, W., Winter, S., Wei, A., Xie, T., Marinov, D., & Bell, J. (2020) · Proceedings of the ACM on Programming Languages · doi:10.1145/3428270 · Cited by 64
“Much existing work [Coverity 2014; Infer 2020; Larus et al. 2004; Memon et al. 2017; Muşlu et al. 2015; Sadowski et al. 2015; Saff and Ernst 2003] has found that providing developers with feedback regarding problematic code is most helpful if provided as soon as possible in the development process.”
Bhanushali, A. (2023) · International Journal of Science and Research (IJSR) · doi:10.21275/sr231021114758 · Cited by 11
Metadata
- Authors
- Saff, D., & Ernst, M. D.
- Venue
- 14th International Symposium on Software Reliability Engineering, 2003. ISSRE 2003.
- Publisher
- IEEE
- Published
- 2005-04-25
- Pages
- 281-292
- OpenAlex
- W2116525104
- Cited by
- 141
- References
- 1
- FWCI
- 5.49
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Reducing wasted development time via continuous testing. https://app.cochat.ai/papers/10.1109/issre.2003.1251050
- The paper
- Saff, D., & Ernst, M. D. (2005). Reducing wasted development time via continuous testing. 14th International Symposium on Software Reliability Engineering, 2003. ISSRE 2003. https://doi.org/10.1109/issre.2003.1251050
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.