Regression Test
Re-testing of existing functions after a change in order to detect newly introduced errors.
A regression test re-checks, after a code change, functions that should actually not be affected by the change. The aim is to detect a regression – that is, the case where something that worked before has broken because of the change.
In practice, a regression test suite usually consists of automated tests that are run again in full with every change, instead of limiting themselves to the supposedly affected portion. This is necessary because the effects of a change cannot always be fully foreseen – especially in code that is used in many places in the program.
What Provimedia uses it for
Provimedia runs the regression test suite automatically with every change, before a deploy is even possible.
Want to use Regression Test for your project?
In a free conversation, let's find out how we can implement this for you.
More from Software quality
Clean Code
Guiding idea for code that is designed to be understandable for humans and not just for the compiler.
Learn moreCode Review
Systematic examination of code by other developers before it is merged into the main branch.
Learn moreCode Smell
Conspicuous pattern in code that is not necessarily wrong but points to a deeper problem.
Learn moreDefinition of Done
Written list of criteria agreed in the team that a task must meet in order to count as done.
Learn moreLinting
Automated checking of code for style and formatting errors according to fixed rules.
Learn moreMutation Testing
Technique that deliberately introduces small errors into the code to check how meaningful the tests are.
Learn moreQuality Gate
Check stage in the development pipeline that lets a change pass only if fixed criteria are met.
Learn moreRefactoring
Targeted restructuring of existing code without changing its external behavior.
Learn more