shift left
Doing testing, quality and security checks as early as they work reliably in the software development lifecycle, instead of only before release.
In more detail
Examples include reviewing specifications, writing tests before code, running static analysis on every commit and checking pull requests automatically. Finding a problem earlier usually makes it much cheaper to fix, but later checks still stay because some problems only appear at runtime.
Related terms
- security gate — An automated check in a pipeline that stops a change going further when it fails, usually by exiting with a non-zero code.
- pre-commit hook — A Git hook that runs before a commit is created and can refuse the commit, for example when it contains something shaped like a secret.
- pull request — A request on a hosting service such as GitHub to merge one branch into another, with a page for review, discussion and automated checks.
- test-driven development — A software development technique in which the test cases are developed, automated and then the software is developed incrementally to pass those test cases.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- static analysis — Checking code for problems by reading it, without running it.
Taught in
- Shift-Left Security Principles & Automated Pipeline Gates — Cloud Security & DevSecOps Engineering
- Testing In Sequential, Iterative And Agile Lifecycles — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Test First, DevOps And Shift Left — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep