If your background is testing on a traditional project, you are likely used to
getting requirements that you can use to develop test cases, and then getting
completed functionality to test. In an agile project, you are expected to test
on continually changing code with changing requirements. One common pitfall for
new agile testers is: ?I?ll test the stories on Tuesday when I get my new QA
build?. Waiting for a new build will almost guarantee you?ll always be an
iteration behind the developers. One easy way to avoid this trap is to start
testing as soon as the developer has completed their story. Sometimes this means
you need to be inventive about where and how you test.
Agile testing means a mindset change for traditional testers and new tools and techniques to learn.
|
The Discussion Group for Software Quality meets once a month.
All sessions are free. Advance registration by RSVP is required.
For more information e-mail
info@software-quality.ab.ca