Software Quality Assurance Practice Exam

The statement that "All code modules must have unit tests before coding begins" aligns perfectly with the principles of Extreme Programming (XP), specifically the practice of extreme unit testing. In XP, there is a strong focus on test-driven development (TDD), which emphasizes creating unit tests for functionalities before writing the actual code that implements those functionalities. This approach ensures that every piece of code is covered by unit tests from the start, which not only increases confidence in code quality but also fosters better design decisions and reduces the chances of bugs being introduced into the system.

By requiring unit tests to exist prior to the coding phase, this methodology promotes a collaborative environment where developers think critically about the requirements and design of their code with an emphasis on testability. This early testing framework helps guide the implementation process and can streamline the development cycle, enhancing both productivity and software quality.

In contrast, other testing methods mentioned, such as Agile testing and the Open Unified Process, may advocate for testing throughout the development lifecycle but do not specifically require the implementation of unit tests before coding begins in the same prescriptive manner as Extreme Programming does. Therefore, the emphasis and structure provided by extreme unit testing distinctly highlight its requirement for prior unit test creation.