Ask a handful of testers to define exploratory testing. Some will respond that it’s simply poking around - try something, see what breaks, and then try something else. Many will identify it as an iterative process of learning and experimentation. But ask about what makes exploratory testing hard, and you find that practitioners are challenged in knowing where to start, what to test, when to stop, and how to know if they’ve found a bug. What makes for good exploratory testing? Join Philip as he examines the techniques of the actors of the Commedia dell'Arte, the 16th century approach...
Philip Daye
Quality Architect
UKG
Philip Daye has more than two decades of experience in software development, testing, and delivery for companies of all sizes. From his earliest days as a software tester, Philip has pursued a passion for quality, which has led him to hone his craft by studying and researching the advances in the field, applying it to his current work, and then sharing it with others. Active in the testing community, Philip is a co-organizer of the South Florida Test Automation meetup and has presented at several meetups and conferences. Philip’s current role is Quality Architect for UKG, a leading developer and provider of cloud-based HRCM software, where he works with development teams across the company.