regression test
A test run to check that behaviour which used to work still works after a change.
In more detail
Regression tests can be automated or done by hand. A manual regression pass before each release adds both work and waiting to lead time. Automating the checks and running them on every change moves that feedback much earlier.
Example
The course turns each exploit into a regression test that asserts the effect, such as rows returned or state changed, rather than only a status code.Related terms
- regression — A bug where something that used to work stops working, or works worse, after a change.
- test suite — A collection of tests run together to check a piece of software.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- exploit — A piece of code or a technique that takes advantage of a vulnerability to make a system do something it should not.
- dynamic application security testing — Testing a running service for security problems by sending it crafted requests and observing the responses and state changes.
Taught in
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- SDLC: From Request To Running Software — DevOps & Site Reliability Engineering
- SQL Injection: The Exploit — Application Security & Threat Modeling for Engineers
- SQL Injection: The Fix — Application Security & Threat Modeling for Engineers
- Dynamic Scanning — Application Security & Threat Modeling for Engineers