TDD and ETVX – Can they be equated?
In Test-Driven Development (TDD) developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test and finally refactors the new code to acceptable standards.
ETVX stands for Entry-Task-Verification-eXit. IBM introduced the ETVX model during the 80’s. In this model any process is broken down down to multiple tasks which would be performed linearly. You will enter a task only if the entry criteria is met and exit the task when verification is complete and the exi criteria is met.
- Entry Criteria = Working software
- Exit Criteria = Passing the automated test
- Task = Write the code
- Verification = Run the automated test
So, can we say that TDD follows ETVX model or is the similarity only superficial?