QA in CI/CD interview questions

Gating pipelines, test data management, parallelisation, environment strategy, and quality metrics.

3 questions in QA & Testing.

QA and TestingA 24-minute read on how the topic fits together, before the questions.QA and testing fundamentals59 short answers on one page, for revising rather than studying.

medium2

mediumConceptDesignScenario

Which tests should run on every commit and which should run nightly, and how do you decide?

Give the blocking stage a fixed time budget and put only fast, deterministic, developer-diagnosable tests inside it; everything slow, environment-dependent or exploratory moves to a scheduled run with a named owner. Use this ci cd answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects test automation to the point an interviewer is testing.

7 minmid, senior, lead

mediumScenarioDesign

Your test suite takes fifty minutes and every merge waits for it. How do you fix that?

Profile before cutting: suite time concentrates in a few tests, and the cause is usually repeated setup or real waiting rather than work. Parallelise what is independent, move the slow and rarely-failing out of the merge path, and treat deleting redundant tests as legitimate.

5 minmid, senior, lead

hard1

hardDesignScenario

Your pipeline gates every code change. What else reaches production without passing through it?

Configuration, feature flags, content and reference data, schema migrations, infrastructure definitions and dependency updates all change production behaviour, and most organisations ship them through channels that were designed to be faster than the release pipeline.

6 minsenior, staff, lead