Linda Wilkinson, Evisions Inc.
So you’re working on or with agile teams – but are you really agile? Or are your sprints more like little waterfalls, with testing STILL at the end of the process, STILL dependent on one or two people doing the testing, and STILL discovering too many bugs too late to fix on time – forcing painful choices between quality and schedule? Too many bugs found in Production in spite of your spiffy TDD processes? Are you automating a test set that wasn’t that great to begin with? Have a test team using exploratory testing when they don’t know how to explore? Part of our mandate as testing experts is to raise the bar. How do we help make that happen? How do we improve and educate ourselves and our companies in regards to testing?
One of our big challenges as testers is recognizing that maybe, just maybe, we aren’t “all that”. Our testing is by necessity limited in scope and perspective. We are not the developer. We are not the end user. If testing is solely up to us, we will miss things. Important things. The purpose of this paper is to talk about ways we can collaborate to build (and therefore automate) better test sets. How to negotiate who does what and make testing a team activity. How to move towards or improve TDD efforts. And above all, how to do those things in fast, fun, collaborative ways that not only help us to build better software, but better teams.
Target Audience: Expert/Advanced