An External Quality Supporting Test- Driven Development of Web Service Choreographies
Pogiri Ravi Kumar, P. V. G. K. Jagannadha Raju, S. Maruthu Perumal · 2014
Recently, software development teams using agile processes have started widely adopting test-driven development. Despite its name, ―test driven ‖ or ―test first ‖ development isn’t really a testing technique. Also known as test-driven design, TDD works like this: For each small bit of functionality the programmers code, they first write unit tests. Then they write the code that makes those unit tests pass. This forces the programmer to think about many aspects of the feature before coding it. It also provides a safety net of tests that the programmers can run with each update to the code, ensuring that refactored, updated, or new code doesn’t break existing functionality. TDD can also extend beyond the unit or ―developer facing ‖ test. Many teams, including my own, use ―customer facing ‖ or ―story ‖ tests to help drive coding. These