Before agile, regression testing was simple. The testers would take all the ideas for regression testing that were created during a release cycle, add them to the existing ideas, and then run each one until the entire stack was complete. The time it would take to ship software was easy to calculate when it was released once a quarter or every six months. Software teams today aim to release software every two weeks or faster. Agile teams test every function during the release cycle. They may do some light poking one day before shipping and then give their approval. They could also do nothing, and the software still ships. A regression testing strategy is a better approach to this problem. How to Develop a Regression Testing Strategy Each new software update can introduce new problems. A user might be presented with a new page, and asked to submit a date format that the programmer didn't expect. The user might get an error messag...