Although Selenium has become the open source standard for simulating user interactions with the browser, Andrew Krug likes to think of it as more than one tool in your toolbelt. Andrew says Selenium is like the Craftsman Bolt-On tool—with one battery and one grip, it can become a circular saw, drill, jig saw, or even a tire inflator. He’ll cover thirty or more Selenium hacks in this fast-paced session. Find out how you can employ Selenium for security testing, visual testing, email testing, easy content testing, performance testing, load testing … you get the drift. Briefly touching on each Selenium hack, Andrew has one goal for this session: for all participants to learn one thing that they can use immediately upon return to their workplace. As a bonus, all code covered in this presentation will be put up on GitHub.

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 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 past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the risk of software failures. Given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery), how can software testing keep pace with modern application delivery? Enter continuous testing. Wayne Ariola explores the three main differences between continuous testing and test automation.

The key to creating high-performing teams is psychological safety—the ability to be vulnerable in front of others even when they hold diverse viewpoints, and the opportunity to take risks and trust that everything will be OK. However, creating this safety is easier said than done. Maaret Pyhäjärvi shares her story of working with software development and test teams to enable them to be awesome. She explains how to reinforce the positive while enabling great software product development by empowering others in your team. Maaret explores how to be brave when others are not, and how to care for and build safety for others. She describes being a catalyst for your team, emphasizing learning—always with safety as a prerequisite. Today, Maaret uses her position as a tester not only to test every part of the software but also to build the collaboration habits of the team, delivering actionable information to improve product quality.