Imagine you’re caught speeding. In one scenario, you get a ticket and $100 fine one month after the fact, and in another scenario, the police stops you immediately and you must pay $100 on the spot. In which situation is it more likely that you change your way of driving?
In the “principle of immediate feedback” – the closer that feedback to an action is received, the greater impact it has on your behavior. It is the same principle in software development and testing – with some additional advantages. In this session, we’ll look a typical manual test and staging process, and how to decrease the time it takes to deliver feedback and the mean time to repair.
“Test early, test continuously” is a mantra of Agile development. It’s also rapidly becoming the mantra for DevOps as the business demands frequent releases of compelling functionality. Continuous integration is critical for making this mantra a reality—enabling immediate quality feedback after a developer task is done. However, testers’ efforts to “shift left” and integrate testing into CI are commonly disrupted by a number of factors, including constrained access to dependent system components.