When software projects frequently miss release dates and go over-budget, unplanned rework is often the culprit. So why aren’t more companies Shifting Left to get testing and QA involved earlier during sprints?
Despite the widespread adoption of Agile, some testing and QA teams still find themselves falling behind. With time-to-market more important than ever, is shifting left the key to getting beleaguered QA teams back up to speed?
As thought leaders in software testing/QA, we like to keep ourselves up-to-date on the latest cutting-edge insights and industry trends. That’s why we sent our best and brightest to StarEast 2017. Here’s the second half of their two-part report. (Check out part one here!)
Here at Lighthouse, we’re awful passionate about software testing and quality assurance. But even as thought leaders, we like to keep ourselves up-to-date on the latest cutting-edge insights and industry trends. In that spirit, here are some of the most interesting things we heard at StarEast 2017.
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?