In ATDD, the team creates one or more acceptance-level tests
for a feature before beginning work on it. If it doesn't do what the customer wants
you've wasted your time and their money. We need to describe the required
behavior in a form that both developers and non-technical stake holders can
understand. Communication is a key and it is facilitated if everyone involved
in the project uses the same language as for executable specifications
functional and nonfunctional requirements.
No comments:
Post a Comment