Skip to content
#

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

  1. Add a test
  1. Run all tests. The new test should fail for expected reasons
  1. Write the simplest code that passes the new test
  1. All tests should now pass
  1. Refactor as needed, using tests after each refactor to ensure that functionality is preserved

Repeat.

Here are 7,452 public repositories matching this topic...

clean-architecture-manga
fluentassertions

A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.

  • Updated Nov 23, 2024
  • C#

AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.

  • Updated Sep 21, 2024
  • C#

Created by Kent Beck, D.D. McCracken

Released 1957

Followers
50 followers
Wikipedia
Wikipedia

Related Topics

atdd bdd continuous-testing extreme-programming testing