Editing Unit testing (section)

=== Extreme programming ===
Unit testing is the cornerstone of [[extreme programming]], which relies on an automated [[list of unit testing frameworks|unit testing framework]]. This automated unit testing framework can be either third party, e.g., [[xUnit]], or created within the development group.

Extreme programming uses the creation of unit tests for [[test-driven development]]. The developer writes a unit test that exposes either a software requirement or a defect. This test will fail because either the requirement isn't implemented yet, or because it intentionally exposes a defect in the existing code. Then, the developer writes the simplest code to make the test, along with other tests, pass.

Most code in a system is unit tested, but not necessarily all paths through the code. Extreme programming mandates a "test everything that can possibly break" strategy, over the traditional "test every execution path" method. This leads developers to develop fewer tests than classical methods, but this isn't really a problem, more a restatement of fact, as classical methods have rarely ever been followed methodically enough for all execution paths to have been thoroughly tested.{{Citation needed|date=November 2008}} Extreme programming simply recognizes that testing is rarely exhaustive (because it is often too expensive and time-consuming to be economically viable) and provides guidance on how to effectively focus limited resources.

Crucially, the test code is considered a first class project artifact in that it is maintained at the same quality as the implementation code, with all duplication removed. Developers release unit testing code to the code repository in conjunction with the code it tests. Extreme programming's thorough unit testing allows the benefits mentioned above, such as simpler and more confident code development and [[refactoring]], simplified code integration, accurate documentation, and more modular designs. These unit tests are also constantly run as a form of [[regression test]].

Unit testing is also critical to the concept of [[Emergent Design]].  As emergent design is heavily dependent upon refactoring, unit tests are an integral component.{{cn|date=November 2023}}