Once Upon A Time in Software... Learning automation is a quest for valiant QAs. This talk gives you a road-map of how QAs get started, how developers can help, and why it's a good idea. I'll also talk about the post-battle tavern-debrief of how to give good feedback, and how to safely walk into Mordor.
As a QA, you will leave with reasons why automation can make you more awesome, steps to get started, and a list of exercises to work through.
As a developer, you will leave with ways to help testers start into automation, how to give good feedback, and why this will help your team deliver a better product.
Once Upon A Time in Software (why you should try automation)
The Reluctant Hero: But I don't want to be a developer!
One does not simply walk into Mordor (QAs taking the first steps)
Power-ups, dragons, wizards, and gold (How developers can teach, exercises to start with)
The post-battle tavern-debrief (Good feedback and coaching to improve)
Happily ever after, for everyone
When you’re the only QA, how do you instill quality practices and build that mindset into the wider company? I'm going to walk through how we went from eight to forty-five quality advocates, and talk about recruiting, training, fun, multiple remote offices, delegation, velociraptor-avoidance techniques, staffing, blood, sweat, and tea. I’ll share the potholes we fell into so you can fall in different ones, and build a practice of awesome testers.
Building a QA practice requires buy-in from management and developers, and can mean changing the process to include up-front quality advocacy, instead of end-of-the-line quality control. Quality starts before the project is sold to the stakeholders, and it doesn't end until after the product is in the hands of the end users. Growing a practice means finding the right people to work with, and communicating well with clients, users, sales, management, and developers.