Acceptance Test Driven Development
Acceptance Test Driven Development
It feels just natural that you would want to do ATDD.
After all, wouldn't you want to validate the implementation against the original requirement. Very logical. Unfortunately a lot of 'Testers' in the software industry are of the opinion that you cannot do anything unless the implementation is complete. For such people, ATDD is not only un-natural but outright bizarre.
The 'Developers' try and work around this problem by having more and more tests at the 'unit' level. That's their natural response. This, unfortunately, ends up with a situation where there is not enough acceptance tests coverage against the original specification. Lack of tests mean that the implementation gaps (as opposed to bugs) are discovered nearer the release
This has a potential of having a robust product but still not meeting the end user goal.
Close but no cigar!!
It feels just natural that you would want to do ATDD.
After all, wouldn't you want to validate the implementation against the original requirement. Very logical. Unfortunately a lot of 'Testers' in the software industry are of the opinion that you cannot do anything unless the implementation is complete. For such people, ATDD is not only un-natural but outright bizarre.
The 'Developers' try and work around this problem by having more and more tests at the 'unit' level. That's their natural response. This, unfortunately, ends up with a situation where there is not enough acceptance tests coverage against the original specification. Lack of tests mean that the implementation gaps (as opposed to bugs) are discovered nearer the release
This has a potential of having a robust product but still not meeting the end user goal.
Close but no cigar!!
posted by spark @ 6:59 AM
0 comments
0 Comments:
Post a Comment
<< Home