2. You are a tester on a team that is “going agile” or has “gone agile” Most testing has been people manually clicking and typing on the “QA Server” Bug reports have been filed and many ignored for a while, leading to a huge bug database The test team now has to figure out how to “go agile”, too Or, maybe you’re new to a team that has never had a tester or test team before Does this sound familiar?
3. So many “types” of testing, and how much of each do we need? What’s the “big picture”?
7. Stop the bleeding Identify frequent and time-consuming tasks Begin to automate them Begin to run them regularly “Hey developer, can you help me with this?”
9. Start pair-developing (pair tester with dev) Start writing test automation with new features Regular builds or continuous integration “Done” means coded and tested (and documented, if needed) Stay Current
11. Start to fill in automation of regression tests Some UI tests Many FitNesse/ integration tests LOTS OF unit tests Begin to refactor both code and tests Catch Up