Continuous test-driven development: Difference between revisions
Content deleted Content added
Filled in 6 bare reference(s) with reFill 2 |
m remove links to deleted portals |
||
| Line 1: | Line 1: | ||
{{Software development process}} |
{{Software development process}} |
||
'''Continuous test-driven development''' ('''CTDD''')<ref name=Madeyski13>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.</ref> is a [[software development]] practice that extends [[test-driven development]] (TDD) by means of automatic test execution in the background, sometimes called [[continuous testing]].<ref name=Saff03>Saff, D. and Ernst, M. D. ''Reducing wasted development time via continuous testing'', Fourteenth International Symposium on Software Reliability Engineering, 2003, Denver, USA, |
'''Continuous test-driven development''' ('''CTDD''')<ref name=Madeyski13>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.</ref> is a [[software development]] practice that extends [[test-driven development]] (TDD) by means of automatic test execution in the background, sometimes called [[continuous testing]].<ref name=Saff03>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.</ref> |
||
==Practice== |
==Practice== |
||
| Line 16: | Line 16: | ||
== References == |
== References == |
||
{{Portal|Software Testing}} |
|||
{{reflist}} |
{{reflist}} |
||
Revision as of 12:26, 7 August 2019
| Part of a series on |
| Software development |
|---|
Continuous test-driven development (CTDD)[1] is a software development practice that extends test-driven development (TDD) by means of automatic test execution in the background, sometimes called continuous testing.[2]
Practice
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 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.
Continuous testing tools
- Infinitest open source Eclipse and IntelliJ plug-in[3]
- NCrunch commercial continuous testing plug-in for Visual Studio[4]
- Autotest - continuous testing for Ruby[5]
- AutoTest.NET - autotest for .NET[6]
- AutoTest.NET fork for CTDD[7]
- Mighty-Moose - packaged version of AutoTest.NET[8]
- Wallaby.js - continuous testing for JavaScript/TypeScript/CoffeeScript[9]
References
- ^ 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.
- ^ 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.
- ^ "Infinitest". infinitest.github.io.
- ^ "NCrunch for Visual Studio". www.ncrunch.net.
- ^ "Save a file, autotest will run the matching tests! (Autotest without ZenTest): grosser/autotest". November 10, 2018 – via GitHub.
- ^ "AutoTest.NET is a tool for automatically running builds and test in the background when code changes. This practice gives you immediate feedback and helps facilitate real test driven development. -." February 19, 2019 – via GitHub.
- ^ "AutoTest.NET is a tool for automatically running builds and test in the background when code changes. This practice gives you immediate feedback and helps facilitate real test driven development. -." March 27, 2018 – via GitHub.
- ^ http://www.continuoustests.com/
- ^ "Wallaby - Integrated Continuous Test Runner for JavaScript". wallabyjs.com.