Test-driven Development
For many developers tests are tedious. What counts are the features. Tests likely to be postponed to the end of the development process. If then the release is on the cusp, stress is predictable. The tests still have to be written. Since there are days or even weeks between implementing the logic and testing, the developer has to relearn the logic. That costs time. Additionally in many parts bugs appear – which means night-shifting.
It doesn't have to come so far. If a developer tests his features consequently in periodic steps close to the programming, he requires less time for testing and feels safe. Because his feature is tested – it functions and fulfils the requirements. If he carries out a re-factoring he directly knows where the error came up due to the failed test.
Our workshops on the topic of test-driven development not only teach the testing before development, they practise it as well. We make your developers fit for testing.
- Test-driven development: Theoretical concepts and practical exercises with JUnit and Groovy
- Quality measurement and test-driven development: Construction of a infrastructure for test-driven development with Continuous Integration Systems