If there’s one fundamental challenge about testing in Agile, it’s keeping up with the speed of developers. But while you don’t want bottlenecks, you don’t want to sacrifice quality, either. So, how do you make sure your testers don’t fall behind? Automate as much as you can—then automate a little more.
With a lengthy implementation period and a focus on long-term gains over static, unchanging tests, most people’s idea of test automation seems to be incompatible with the fluid, iterative Agile development methodology. Are these two really incompatible, or are we just not thinking about it the right way?