Testers make difficult decisions with minimal information in turbulent times on critical projects.  Independent consultant, Fiona Charles, suggests that testers must learn to draw a line in the decision-making process between trained intuition and careless assumption.  In this...

When the atmosphere is hostile to QA, and yet the demands on the QA Team are increasing, how do you transform a team where everything is tested and deployed manually, to an organization that delivers great software multiple times a day? Where do you start and how do you create the strategy for implementing Continuous Testing? Join David Lumpkin as he shares his company's journey to answer these questions and the team's evolution along the way. Over a three-year period, Craftsy went from an environment hostile towards QA, to one that embraces automation and exploratory testing, achieving the right level of coverage for every use case, device and browser. It wasn’t easy though and David shares their experience through many experiments, failures and revisions that finally made Continuous Testing a reality.

The testing community is caught between a rock and a hard place when it comes to exploratory testing. Although exploratory testing has been around for ages, it often leads to more confusion than clarity. Is exploratory testing an activity-something that you do? Or is it an approach-a way or a style of doing something? Isn't all testing exploratory? When do you do it? How do you do it properly? How does it relate to the entire software lifecycle? To answer these questions, join Ingo Philipp as he shares the most common confusions and controversies on this topic. He explains what exploratory testing is, why to use it, how and when to practice it. Ingo discusses specific heuristics and techniques/tours of exploratory testing, especially useful in fast-paced development environments, to get the most out of exploratory testing in your daily work.

In an agile world where having dedicated testers can be a controversial idea, manual testing is a tough sell. Not all contexts have their testing automated, so what is a manual tester to do when it comes time to release? Your team starts asking about regression testing, requests estimates, and expects justifications for the time being spent. Intuition isn't the answer, and retesting everything is not an option. In this session, seasoned tester Brendan Connolly will share his five core values for focusing your regression testing efforts: consistency over correctness, behaviors over bugs, intent over implementation, conformity over complexity, and common over complete. These values not only help with decision-making, but also serve as a heuristic foundation for understanding and communicating about regression testing, as well as define a clear intent and context for all your future regression tests.