Test-driven development
Test-driven development (TDD) is a software development process relying on software requirements being converted to test cases before software is fully developed, and tracking all software development by repeatedly testing the software against all test cases. This is as opposed to software being developed first and test cases created later. Programmers also apply the concept to improving and debugging legacy code developed with older techniques.
Process
- Add a test
- Run all tests. The new test should fail for expected reasons
- Write the simplest code that passes the new test
- All tests should now pass
- Refactor as needed, using tests after each refactor to ensure that functionality is preserved
Repeat.
Here are 359 public repositories matching this topic...
Example of how to write Chef recipes by testing first. My personal examples and notes of the process.
-
Updated
Jun 25, 2015 - Ruby
Serverspec / Specinfra backend for Docker nsenter execution driver.
-
Updated
Jan 3, 2016 - Ruby
Serverspec / Specinfra backend for Docker Compose.
-
Updated
Jan 8, 2016 - Ruby
Serverspec / Specinfra backend for Docker LXC execution driver.
-
Updated
Jan 9, 2016 - Ruby
eCommerce Rails web app built by @dlaguerta, @esther-ng, @NatashaRaime, and @brookseakate
-
Updated
Oct 28, 2016 - Ruby
Shipping Service API for use in Betsy websites, built by @heatherherrington and @brookseakate
-
Updated
Nov 10, 2016 - Ruby
Created by Kent Beck, D.D. McCracken
Released 1957
- Followers
- 47 followers
- Wikipedia
- Wikipedia