If you’ve been in the industry for a long time, you’ll probably remember when test teams sat in their own secluded area, idly waiting for code handoff, and were discouraged from “bothering” developers. There may have been a lot of running around to qualify builds, do smoke tests, verify bug fixes, and comb through the build notes for feature changes.
For as long as I have been in software testing, there has been a constant demand to grow technology, grow skills, automate more, and do it all faster (that is a given). What has been so remarkable recently is the rate at which these demands shift gears and move in different directions, new products, and evolving technologies.
Agile’s most defining qualities are speed of delivery and testing friendliness. Automating the tests and building a sustainable, low-maintenance framework is the key to maximizing Agile’s benefits. Doing it right requires new thinking and strategic methods—not old or random test automation practices. When coupled with testing and driven by Action Based Testing (ABT), Agile practices will improve system development and test development.
Just when you thought you were safe from more process improvement for a while-not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most concerning test teams.