A test is no better than the data that drives it. Fuzz testing is a great way to find buggy, exploitable, or otherwise bad code – and if you’re working with a native application that operates on file input, it’s a solved problem. Grab AFL or some other all-in-one suite, hit go, and profit!

Jessie Shternshus shares her innate and learned curiosity, and how it fueled her exploration of the subject. She walks you through how she has learned to ask more inquisitive questions, looks for new and different ways to connect people, and connects the dots between ideas.

In this practical and inspiring talk, Jess Ingrassellino will share how she developed collaborative test charters when she started working as the first exploratory tester at Salesforce.org.

A decade ago Microsoft had over twelve thousand full-time testers, and when you added up all the contract and outsourced testers too, there were more software test engineers than developers. The test automation solutions alone had more than a hundred million lines of code. However, that process was built for a company that would release a new version of a monopoly-scale product once every three years and ship it on a CD. That world had already begun to change, and Microsoft was missing the boat. When Microsoft tester Ken Johnston first encountered agile development and DevOps, he realized his vision of testing needed to change—and so did he. Ken set out on the path of big data, and that led his to his new career in data science. Testers have always been the masters of product quality data, and now with connected services and telemetry, there is more data than ever.