Regression test
A check for unwanted effects of a change on behaviour that is still required.
Check existing behaviour after changes
Regression tests look for unwanted effects of a change on behaviour still needed. They can run manually or automatically at different test levels. Scope should follow potential impacts and risks.
In a fictional example, request-list sorting changes. Opening existing requests and previous approval permissions are checked too. Retesting an original sorting defect specifically and looking for further effects have different test objectives. Select relevant cases through affected dependencies and keep them current as changes continue. An executed regression test does not automatically make untested areas defect-free.
Sources
Related terms
- Unit testA focused check of a small, defined part of software, such as a rule or function.
- Integration testA check that selected software parts work together as intended through their interfaces.
- End-to-end testA check of an agreed workflow across the system parts essential to it.
- Test automationTools perform defined testing tasks, such as execution and comparison with expected results.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps