Behavior-driven development (BDD) has been around for a while and is here to stay. However, the added abstraction levels pose a technical problem for writing and managing tests. While BDD does a great job of marrying the nontechnical aspect of test writing to the technical flow of an application under test, keeping this information under source control becomes problematic. Frameworks such as JBehave, Cucumber, or Robot give subject matter experts that additional ability to write tests, but they are often restricted access from them; because people treat test cases as code, they get stored in source control repositories. Additionally, these given-when-then steps soon can grow to an extent where they are difficult to manage without an IDE, and nontechnical people lose interest. Using management tools, Max Saperstone shows how to manage these nontechnical steps and keep them in sync with the automaton in tools such as Git.

In a busy world, testing teams are asked to adopt new approaches to increase speed and flexibility of change. What methods and tools can help? Artem Golubev has seen many testing teams being told to use Docker. But for testers, this brings confusion. What it Docker and why is Docker useful to testers? How can Docker be used to increase confidence in our releases? To help you answer those questions, Artem shares his experience using this popular tool and approach. Starting with terminology Artem shares what is meant by Dockerfile, Docker Image, Docker Container, Compose, Kubernetes, and then explains the advantages and limitations of Docker. He shows how to build a Docker-based deployment in this session and gives Hands-on help. He shows how to add Docker to your own current project on your own machine and how-to setup Kubernetes on Google Compute Cloud.

To test a product, there are so many questions to ask, and so little time in which to ask them. More often than not, we get caught up in the who, what, when, and how, but Jane Jeffers from Riot Games explains that “why…?” questions can be the most important ones to ask when it comes to QA work. When missing the whys, we can wind up only focusing on specific details like who needs to do the work or when our deadlines are, and subsequently lose the bigger picture of why a project matters, and why we do what we do. Learn some of the key ways that you can ask why for product, for process, and for people, and how the answers you get will help you with everything from how to devise your overall test strategy to how you communicate with your teammates to get them thinking about quality.

[video:https://youtu.be/Bm_rtOmpIqg width:300 height:200 align:right]

Emerging technologies such as the internet of things (IoT) and cloud computing have introduced a significant software variety and complexity. Wendy Siew Wen Chin and Heng Kar Lau explain that testers are challenged to support a wide product portfolio within harsh time, resource and budget constraints. More test automation may seem to be a solution to test efficiency, however there are many inefficient hot spots throughout the test automation life cycle. Join Wendy and Heng Kar as they share their experiences from the Intel IoT team. They share how to make use of artificial intelligence (AI) tools to leverage opportunities throughout a testing project. They show how to blend test data analytics, test automation, test coverage analytics and test case selection. Learn how software testing, AI and data analytics can be combined to transform your testing, by helping you focus your testing on what matters most.