What Did You Test?

Title: What Did You Test?
It’s a simple enough question, but the answer depends.

Was there an escape defect that caused an outage and now you’re tasked with determining where the hole in the death star is? Where do you start?

Or maybe you’re about to take a new product from stealth to general availability and your stakeholders are asking about coverage? What do you tell them?

Maybe you did all the “best practices” and feel confident that you’re covered. But how can you be sure? And how can you easily articulate it to the business in a way that will land? And how are you keeping up with the dramatic increase in automated test code coming out of AI that requires human-in-the-loop verification?

Turns out it’s not a simple question to answer. But it can be. In this talk we’ll discuss how, and show an example in practice using an AI native approach with a free and open source project called wdyt (pronounced “wah-dit”, which is short for “What did you test?”).

6-6:30p.m. - food & drinks
6:30-7:30p.m. - Presentation
7:30-8:00p.m. - Q&A

About the speaker:
By his own admission, Dave Piacente has spent far too much time in test automation.

Over the past 17 years, he has worked across engineering, product, consulting, and leadership roles. Most relevant to this talk, he has:

* Built test automation tools, including work as a maintainer of Selenium IDE and as a product engineer at Applitools
* Run a management consulting practice where he observed and coached hundreds of development teams across multiple Fortune 100 companies
* Earned a Master’s degree in the Management of Information Technology from UVA’s McIntire School of Commerce

Dave's current project, wdyt, grew out of a recurring frustration: even when tests are passing, teams often struggle to explain what behavior those tests actually covered.