Isn’t it amazing? Stakeholders drop software on our desks and expect us to test it—without any requirements, design, or product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust, and heroically test quality into a product we have never heard of before. But testing in the dark is not impossible, and as Rob Sabourin shows, it can even be a very valuable and fun experience. Learn strategies to emerge from a murky fog into clear, meaningful quality insights and leverage unlikely sources about what stakeholders care about and what users really need the software to do. Rob introduces you to methods of reconnaissance-style, charter-driven, and session-based exploratory testing and help you provide meaningful estimates to stakeholders with minimal hard information about the software under test.

Are you confronted with automating tests of large, complex systems? Are there more conditions to test than you can do in a lifetime? Are auditors demanding compliance to a never-ending collection of regulations? Do stakeholders want slick dashboard...

"Move fast and break things” tells quite a story of the relationship between speed and agile. Speed has been a driver in our industry before it was even an industry. Books promise that certain frameworks can deliver twice as much in half the time, yet teams still struggle delivering what's expected of them. This session describes a six-month case study of a multi-team transformation. The orders were to make the teams deliver faster, but they were consistently missing deadlines. Frustration was on the rise. Only after taking the time to understand what they meant by "faster" could the teams improve—and the solution ended up being to slow down. Chris Murman will help you learn how to make the case to slow down, work in increments, deliver frequently, and delight customers. He will explain which metrics to use to measure progress, patterns of successful teams, and the necessary coaching stances.

Automation fails frequently in companies due to a variety of reasons, including poor team communication, lack of skills, flaky tests, and inadequate understanding of test coverage. Even when things are going well, the automated tests sometimes grow to a size where the test suites take too long to execute for the run to be viable. James Farrier is a test automation architect who will show you ways to leverage machine learning to address these challenges. You'll learn how to determine which tests are valuable to run after each commit or build in order to cut down the suite run time, how to automatically close and open defects based on test run results, and how to separate a test into different test runs to keep track of tests in different states. Finally, he will show you how to create a results dashboard that allows for team collaboration and a better understanding of test coverage so that testing can be further streamlined.