Do you remember sitting in front of the television as a kid enjoying your favorite Saturday morning cartoons? Chris Loder shows you how the lessons we learned from those cartoons apply to our everyday work in test automation. Wait until you hear what we’ve learned from the likes of Scooby Doo®, Wile E. Coyote®, and many other favorites! Like Bugs Bunny®, maybe we should “have taken that left turn at Albuquerque” and possibly done things a little differently. Discover how the animators in Spiderman® didn’t redraw every background but reused the animation cells, similar to our reusing pieces of test code. And see how Scooby Doo taught us that with the right team, we can solve anything! Chris talks about the automation that he is building at InGenius and how all those hours in front of the TV are helping make it successful. Come for the ‘toons, leave with the lessons!

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.

The DevOps movement is front and center across enterprises. Companies with mature systems are breaking down siloed IT departments and federating them into product development teams and departments. Testing and its practices are at the heart of these changes. Traditionally, development organizations have been filled with mostly manual testers and a limited number of automation and performance engineers. Adam Auerbach says this has to change. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding in order to stay relevant and add more value to the business. Based on his experiences at Lincoln Financial and Capital One, Adam explores what the DevOps movement is all about, its core values, and proven patterns for how testing must evolve.

The testing community is caught between a rock and a hard place when it comes to exploratory testing. Although exploratory testing has been around for ages, it often leads to more confusion than clarity. Is exploratory testing an activity-something that you do? Or is it an approach-a way or a style of doing something? Isn't all testing exploratory? When do you do it? How do you do it properly? How does it relate to the entire software lifecycle? To answer these questions, join Ingo Philipp as he shares the most common confusions and controversies on this topic. He explains what exploratory testing is, why to use it, how and when to practice it. Ingo discusses specific heuristics and techniques/tours of exploratory testing, especially useful in fast-paced development environments, to get the most out of exploratory testing in your daily work.