Jump to content

Continuous test-driven development

Add links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by KolbertBot (talk | contribs) at 22:33, 19 September 2017 (Bot: HTTP→HTTPS (v461)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Part of a series on
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and bodies of knowledge
Glossaries
Outlines

Continuous test-driven development (CTDD) [1] is a software development practice that extends test-driven development by means of automatic test execution in the background (sometimes called continuous testing[2]). In CTDD the developer writes a test first but is not forced to execute the tests manually. The tests are run automatically by a continuous testing tool (see external links for examples) running in the background. This technique can potentially reduce the time waste resulting from manual test execution by eliminating the need for the developer to start the test after each phase of the normal TDD practice: after writing the (initially failing) test, after producing the minimal amount of code for the test to pass and after refactoring the code.

See also

References

  1. ^ Madeyski, L. and Kawalerowicz, M. Continuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool, Proceedings of the 8th International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE), 2013, Angers, France, 4–6 July 2013: p.260-267.
  2. ^ Saff, D. and Ernst, M. D. Reducing wasted development time via continuous testing, Fourteenth International Symposium on Software Reliability Engineering, 2003, Denver, USA, 17-20 November 2003: p.281-292.

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=Continuous_test-driven_development&oldid=801479447"