Cited by 24Software Engineering Techniques and PracticesSoftware Testing and Debugging TechniquesSoftware Engineering Research

The DOI matches its Crossref record; 17 of the 17 references it cites were found in a registry or an index.

Quality of Testing in Test Driven Development

Cauevic, Adnan, Punnekkat, Sasikumar, Sundmark, Daniel·2012·2012 Eighth International Conference on the Quality of Information and Communications Technology

Abstract

Test-driven development is an essential part of Extreme Programming approach with the preference of being followed in other Agile methods as well. For several years, researchers are performing empirical investigations to evaluate quality improvements in the resulting code when test-driven development is being used. However, very little had been reported into investigating the quality of the testing performed in conjunction with test-driven development. In this paper we present results from an experiment specifically designed to evaluate the quality of test cases created by developers who used the test-first and the traditional test-last approaches. On an average, the quality of testing in test-driven development was almost the same as the quality of testing using test-last approach. However, detailed analysis of test cases, created by test-driven development group, revealed that 29% of test cases were "negative" test cases (based on non-specified requirements) but contributing as much as 65% to the overall tests quality score of test-first developers. We are currently investigating the possibility of extending testdriven development to facilitate non-specified requirements to a higher extent and thus minimise the impact of a potentially inherent effect of positive test bias.

Overview

Integrity signals

Registry

Crossref · 10.1109/quatic.2012.49

Cites

17 of 17 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 17 references

Research works printed but not linked: 3

  1. 0, Judy - Java Mutation Tester
  2. 0, EclEmma - Java Code Coverage for Eclipse
  3. 0, JUnit Framework

Cited by

Sorted by citations

See all 24

Metadata

Authors
Cauevic, A., Punnekkat, S., & Sundmark, D.
Affiliations
Mälardalen University (SE)
Venue
2012 Eighth International Conference on the Quality of Information and Communications Technology
Publisher
IEEE
Published
2012-09
Pages
266-271
OpenAlex
W2077208035
Cited by
24
References
17
Citations by year
2026: 1 · 2025: 1 · 2023: 1 · 2022: 1 · 2021: 1 · 2020: 1 · 2019: 2 · 2018: 4 · 2017: 2 · 2016: 3 · 2015: 3 · 2014: 2 · 2013: 2
FWCI
1.76
Type
conference paper
Language
en
Open access
closed
Locations
International Conference on the Quality of Information and Communications Technology (QUATIC) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
test-driven development, test case quality, Extreme Programming, agile software development, test quality evaluation

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