Karen N. Johnson

BIO: Karen is a longtime active contributor to the software testing community. She frequently speaks at conferences both in the US and internationally. Karen is a contributing author to the book, Beautiful Testing by O’Reilly publishers. She is the co-founder of the WREST workshop, the Workshop for Regulated Software Testing. She has published numerous articles; she blogs and tweets about her experiences. Find her on Twitter as @karennjohnson (note the two n’s) and her website: http://karennicolejohnson.com/. Karen is Director Jamf Now, Development & Delivery at Jamf.

KEYNOTE: Making Test Automation Visible: Why & How

Test automation is often built without the benefit of everyone on the team knowing what was built or how choices were made in building automation. Sometimes throughout the process of building automation, a tester can feel as though neither people on the team nor the stakeholders around the team “care” about what automation is being built as long as testing is completed faster. And sometimes too, automation demos can be rather dull to watch and although people have watched the demo, team mates often still don’t have a sense of what automation has been built or with what frequency automation is being run.
Ultimately sometimes the team and it’s stakeholders don’t know if the test automation is really helping or not. What we need to remember is that test automation is part of the product, it (the automation) just happens to be the non-visible, non-customer facing part of the product that holds a specific mission – the mission of being to deliver the product to the customer. So with an understanding of why it is important to be aware of the test automation, we can move forward to look at how to communicate what automation has been built and to deliver that information in a consumable way so that those on and around the team are well-informed.

What this talk addresses

A look at why it is important that other people on the team as well as stakeholders around the team, know what automation has been built.
Ideas for how to present information about the test automation that has been built and what remains to be built.