- No traditional style business requirements or functional specification documents. We have small documents (story cards developed from the 4×4 inch cards) which only detail one feature. Any additional details about the feature are captured via collaborative meetings and discussions.
You will be testing as early as practical and continuously throughout the lifecycle so expect that the code won’t be complete and is probably still being written
Your acceptance Test cases are part of the requirements analysis process as you are developing them before the software is developed
The development team has a responsibility to create automated unit tests which can be run against the code every time a build is performed
With multiple code deliveries during the iteration, your regression testing requirements have now significantly increased and without test automation support, your ability to maintain a consistent level of regression coverage will significantly decrease
Refer to http://agiletesting.com.au/