Skip to content
← All CTFL glossary terms

Continuous integration

Automatically building and testing software on every merged change, giving developers fast feedback on integration problems.

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

Continuous integration 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

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