In this building block, a number of measures are described that can be used in, or be of influence on, the development tests. Most of these measures have consequences for the way in which the unit test and/or the unit integration test is carried out, apart from the code review which is an addition to the development tests and has no direct influence on these. It depends on the situation whether any of these measures, and if so which ones, will be chosen. For that reason, they are not included in the development test activities discussed in section 7.3, of TMap Next but are briefly described below. The fact that they are optional emphatically does not mean that they only have limited advantages. On the contrary, appropriate application of the measures in the right context can deliver huge advantages.
The following measures are discussed in succession:
- Test-Driven Development (TDD)
TDD is a development method that strongly influences the UT, because it presupposes automated tests and ensures that test code is present for all the (source) code.
- Pair Programming
A development method in which two developers work on the same software and also specify and execute the unit test in mutual co-operation.
- Code review
This evaluation of the code supplements the development tests.
- Continuous Integration
An integrative approach that requires automated unit and unit integration tests, minimising the chance of regression faults.