Creating Visibility with Test Automation – Webinar Recap

test automation visibility

Webinar Recap:

We were thrilled to dive into test automation and spend some time with Joe Colantonio from the popular test automation podcast series and Kevin Dunne from QASymphony during our recent webinar “Creating Visibility and Speed with Test Automation & Test Case Management”. With over 800 attendees, Test Automation seems to certainly be on of the hottest topics for QA and development teams today. In this webinar, Joe and Kevin discuss how to manage automation script maintenance, critical reports and metrics around automated testing, deciding on the proper mixture of automation types, staffing the right mix of talent and much more!

Use this link to watch the on-demand webinar

You can also view the slides below

Lots of great content was covered, but let’s highlight a few key takeaways:

Setting Automation Expectations:

automation manager

One of the first things to do in order to make your test automation efforts more visible starts with setting managers expectations right form the beginning of the project. A lot of times management doesn’t realize that automation is not a one and done thing, it needs to be maintained over time, takes money and resources to keep up, and it’s a team effort. Support from management is key not only to visibility, but the success of an automation project.

Using Risk to Manage Automated Tests Efforts:

Instead of being prescriptive, view test coverage through a lens of risk and ask yourself questions such as; what kind of risks exists to my application or how can my system break and build test coverage base around those risk areas. For example, if you’re testing a health related application, you want to focus on your efforts on the part of the application that can harm or kill someone. It’s risk based; if that didn’t application didn’t work properly, someone might get hurt. Test mixes are great, but marrying a risk based approach can get to better test coverage that adds value.

A single source of truth:

What’s the status of my application? Finding a “single source of truth”, using a test management tool makes answering that question much easier and visible through one dashboard, one location and makes it easy for traceability. Having one location where you can see all of your requirements, tests that fulfill those requirements and all the testing/development and activities in one place helps increase visibility.

Thanks again for everyone who attended the webinar.

Leave a Reply

Your email address will not be published. Required fields are marked *

More Great Content

Get Started with qTest