From: Jane L Huang (jhuang@Lightfirst.com)
Date: Thu Apr 10 2003 - 00:47:47 EST
I recently received an invitation to a talk by Robert Martin about requirements and testing
In the promo he states that:
"Agile methods have taught us a great deal about automated testing, both at the unit level and at the system level. Agile methods have also taught us that well written automatic tests are better at specifying requirements than prose documents are."
He then goes on to claim that "a good automated test can also be a good requirements document."
I would be very interested to hear people's points of view on this. Let's assume that the agile approach is being applied in a non safety critical application.
Do you agree that agile automated tests can replace requirements specifications? What would we lose by doing this? Also, could agile concepts such as early delivery and feedback compensate for any of these losses?
This is a refrain I am hearing increasingly often from a growing agile community, and I think a good discussion would be very useful.
Sincerely,
Jane Huang, PhD.
School of Computer Science, Telecommunications, and Information
Systems,
DePaul University,
243 So. Wabash Avenue
Chicago IL 60604
312-362-8863
jhuang@cs.depaul.edu
This archive was generated by hypermail 2.1.6 : Mon Apr 14 2003 - 09:00:09 EST