Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | * **Ultimate Goal**: Reduce costs and increase productivity. | ||
| 2 | * **Definition 'Production Code':** Code that provides functionality to meet project requirements. | ||
| 3 | * **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code. | ||
| 4 | |||
| 5 | === Benefits of Testing === | ||
| 6 | |||
| 7 | * **Quality Assurance** | ||
| 8 | ** **Automated Testing**: Minimizes the need for human source code checking or manual testing, providing a cost-effective way to ensure continuous quality assurance and the correct functioning of software at all times. | ||
| 9 | ** **Early Feedback**: Tests provide immediate bug feedback. This is especially true for detecting accidentally introduced bugs caused by code changes. The earlier bugs are detected, the cheaper they are to fix. | ||
| 10 | ** **Bug Location Detection**: Tests identify bug locations, saving debugging time. | ||
| 11 | * **Testable Design** | ||
| 12 | ** Writing tests automatically enforces design best practices, resulting in a 'testable design' and higher quality code. Good code and architecture are testable, and vice versa. | ||
| 13 | * **Documentation** | ||
| 14 | ** ((( | ||
| 15 | Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state. | ||
| 16 | ))) |