From 975f49eb61fcbe1460b4d57717a6ebfc00e1209a Mon Sep 17 00:00:00 2001 From: Anna Tyrrell <16312226+githesp@users.noreply.github.com> Date: Sun, 24 Feb 2019 18:47:00 +1300 Subject: [PATCH] Edit for spelling and grammar. (#27611) --- guide/english/agile/test-driven-development/index.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/guide/english/agile/test-driven-development/index.md b/guide/english/agile/test-driven-development/index.md index 4b1fff582e..1a8b7cc72a 100644 --- a/guide/english/agile/test-driven-development/index.md +++ b/guide/english/agile/test-driven-development/index.md @@ -3,8 +3,7 @@ title: Test Driven Development --- ## Test Driven Development -Test Driven Development (TDD) is one of Agile Software Development approaches. It is based on the concept that -> you must write a test case for your code even before you write the code +Test Driven Development (TDD) is an Agile Software Development approach. It is based on the concept that you write a unit test first, and then write the code that will allow this test to pass. This means we are working iteratively to specify and build correct behaviour and also to create clean code with good structure. With TDD, the unit test is written first with a test that fails, you then write the code that will execute and allow the unit test to pass. Overall TDD saves time spent performing unit tests and other similar tests since test creation is developed before the code has even been written. @@ -26,7 +25,7 @@ Each new feature of your system should follow the steps above. Agile Data's Introduction to TDD -Wiki on TDD +Wikipedia on TDD Martin Fowler Is TDD Dead? (A series of recorded conversations on the subject)