Have you ever found yourself hesitating, your cursor over the “deploy” button, with sweat pouring down your face because you know who will be blamed if (or let’s be honest: WHEN) everything explodes? You’re a QA engineer, of course, you have. If only there were some way to have a higher degree of confidence in those pesky devs you’re working with!

The more astute of you will know what’s coming next: THERE IS! And that “some way” is your test suite.

Couple questions for you:

• If your test suite is green, can you push to prod RIGHT NOW with a high degree of confidence that nothing will explode?
• If your test suite is red after running your e2e tests ONLY ONCE APIECE, do you have a high degree of certainty that something is wrong?

If you answered “no” to either of those questions, then it’s likely you dread deploy day. And what does that mean? Your test suite isn’t doing its job.

A test suite’s entire purpose is to buy you confidence — a high degree of confidence — that there are no regressions with the latest updates to your codebase. Anything less and it’s not just underperforming, it’s misleading.

In this session, we’ll talk about what a solid test suite should look like and how it’ll give you more confidence than you’ve ever had in your deploys. It might even mean deploy days stop being sweat-inducing stress mares that keep you up at night!

Takeaways from the talk:

• By the end of this talk, you’ll be properly equipped to evaluate and transform your current test suite into a confidence-boosting tool that will make you smile when the time comes to click that deploy button.