Automation is the general demand from project teams so that projects can be shipped as soon as the last code is checked in to source code. Automation of areas that don't change can be a great benefit to testers. Automating not well documented new feature can take much longer than any plan, unless it is done by the developer of the product.
Other changes in testing style that help agile projects
- Do not call for rigid Testing Procedures as the requirements/features can change rapidly.
- Test early and often.
- Test from end user perspective and early
- Build pass is a test case - don't you think so?
- Adopt iterative testing - not waiting for the last build to start test cycle
- Each recorded bug in the system is asset and liability. Liability in that there is fixed cost associated with the administration of the defect. Don't have the team motivation based on bug count - instead focus on quality of the product and the number of not already known issues returning from field
- Module/unit testing (jUnit) can help - especially when the system level is not quiet ready
- Practice light weight documentation style. Not a pretty verbose documentation.
- Make reusable checklists - preferably in wiki
- Testing Sequence for an incremental internal/external release
- New features
- Bug verification
- regression testing (run any automated test continuously)
No comments:
Post a Comment