Artificial Intelligence (AI) is making it possible for computers to diagnose some medical diseases more accurately than doctors. Such systems analyze millions of patient records, recognize underlying data patterns, and generalize them for diagnosing previously unseen patients. A key challenge is determining whether a patient's symptoms and history are attributed to a known disease or other factors. Software testers face a similar problem when triaging automation failures. They investigate questions like, Is the failure due to a defect, environmental issue, or nondeterministic test script? Is there current or historical evidence to support one belief over another? Join Tariq King as he describes how test failures and flakiness can be modeled for machine learning (ML) as causal disease-symptom relations.

Sometimes we allow ourselves to drown in work… Mary Thorn hears it all the time: testers complaining at retrospectives to their teams that they do not have enough time to test everything. She often sees testers work overtime the last week of a sprint to ensure the definition of done is accomplished. Why do they do this? Why do we, as testers, enable the bad behaviors of “Scrummerfall” or a lack of whole-team ownership of quality? Mary aims to arm testers with techniques that allow them to test smarter, not harder, and enable the testers and the team to have better conversations that make it clear what they are testing in the sprint. Most importantly, she wants you to come out of her session being able to answer the question, “What are you not going to test this sprint?” Take home some approaches that allow you to swim, not sink, by focusing your own and your team’s efforts.

Testing is shifting left, moving closer to testing the code itself before the full product is ready for release. While the backend world already has established methodologies for testing, frontend developers and testers are still trying to figure out how to work together to effectively test the code. Gil Tayar suggests testers need to communicate with the frontend developers to understand the framework by which frontend code is tested, the various kinds of testing that can be performed on frontend code, and which tools can be used. During this session, Gil helps ease your fear of the unknown by teaching you how to test developer code. He discusses various test methodologies you can use and how they fit together in a coherent way. Gil also includes sample code that you can use as a template in your own project. If time permits, we'll get hands on and do a bit of live coding.

Is testing a bottleneck in your company? Do you uncomfortably squeeze testing into projects? Can you show stakeholders how testing adds value? Sophie Benjamin has spent the last fifteen years answering these questions, transforming testing into add...