Skip to content
← All CTFL glossary terms

Shift left

Performing testing and quality activities earlier in the software development lifecycle, following the early-testing principle.

Syllabus chapters: 2

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Shift left in a practice question

Question 1

A team introduces continuous integration (CI): every commit is built, and the component tests and static analysis run before a merge is allowed. What is the impact on testing?

  1. Manual testing from the user's perspective becomes unnecessary once CI is stable
  2. Shift left occurs, because developers now submit code with component tests and static analysis
  3. Regression risk rises, because the automated checks replace the regression tests
  4. Test effort falls, because the CI setup needs little definition or maintenance
Show answer
  • Manual testing from the user's perspective becomes unnecessary once CI is stableEven with a high level of automated testing, manual testing from the user's perspective is still needed.
  • Correct answer: Shift left occurs, because developers now submit code with component tests and static analysisCI promotes shift left by having developers submit code accompanied by component tests and static analysis.
  • Regression risk rises, because the automated checks replace the regression testsDevOps minimizes regression risk through the scale and range of automated regression tests, rather than displacing them.
  • Test effort falls, because the CI setup needs little definition or maintenanceThe delivery pipeline must be defined and established, and the CI/CD tools introduced and maintained.

CI promotes shift left in testing by encouraging developers to submit high quality code accompanied by component tests and static analysis, which is exactly what this pipeline enforces. DevOps also gives fast feedback on code quality and minimizes regression risk through the scale and range of automated regression tests, but the pipeline itself must be defined and established and its tools maintained, and manual testing — especially from the user's perspective — is still needed.

Syllabus section 2.1.4

Question 2

A team currently runs its performance tests only once the whole system has been assembled in a representative test environment. Which change would achieve shift left?

  1. Begin non-functional testing at the component test level wherever that is possible
  2. Run the full regression suite immediately after each release to production
  3. Complete the static analysis of the source code only once dynamic testing has begun
  4. Assign a dedicated independent test team to the later test levels
Show answer
  • Correct answer: Begin non-functional testing at the component test level wherever that is possibleMoving non-functional testing down to component level is a named shift-left practice.
  • Run the full regression suite immediately after each release to productionTesting after release moves activity later, which is the opposite direction.
  • Complete the static analysis of the source code only once dynamic testing has begunStatic analysis should be completed prior to dynamic testing, not after it starts.
  • Assign a dedicated independent test team to the later test levelsStaffing the later levels moves no test activity earlier in the SDLC.

Performing non-functional testing starting at the component test level, where possible, is named among the good practices that achieve shift left, precisely because these non-functional test types tend otherwise to be performed late in the SDLC when a complete system and a representative test environment are available — which is the situation described.

Syllabus section 2.1.5

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.