A software development practice in which a failing automated test is written for a small piece of desired behavior before the code that implements it, with the code then written just enough to pass the test and afterward refactored.
Facts
Partially Attested
Origin YearDate marks the original publication of Kent Beck's canonical book; the underlying test-first practice is described by Beck as rediscovered from earlier programming disciplines, not newly invented that year. Core Principlewriting an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case. 1 Connections
Sources
1. Test-driven development - Wikipedia
Introduction (lead section)Quote, Introduction (lead section)
writing an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case.
2. Test-driven development, By Example (Open Library catalog record)
Original publication date fieldQuote, Original publication date field
November 8, 2002
Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.