Regression Testing

Agile Regression Testing: How to Do It Well

For teams following agile software development practices, regression testing is a must. Agile teams constantly make changes to live software that can introduce regressions (or, code changes that break the functionality of part of an app). Regression testing can keep teams from shipping critical bugs to production by confirming the most important parts of an app are still working every time new code is pushed.

Performance Regression Testing

Regression Testing, as all Quality Assurance professionals know, is ensuring that previously developed and tested software continues to operate after a change. Performance Regression being a subset of regression testing as a discipline is therefore ensuring that previously developed and tested continues to meet its performance criteria after a change.

How to Overcome Common Regression Testing Challenges

Many stakeholders see software development as a linear process — the software is written, tests are run, and the code is deployed. On the other hand, many developers know that seemingly benign changes to a piece of code can have a ripple effect across the application. Regression testing is the only reliable way to make sure that everything works. Small changes to a piece of code can have a ripple effect across an application, which makes regression tests important to ensure everything works.