Your one-stop platform to prepare, practice and ace your interviews.
Loading your questions…
20 hand-picked CI/CD for Testers interview questions with detailed answers. Open the interactive version above to search, filter by difficulty, run code, bookmark questions and track your progress.
CI (Continuous Integration) automatically builds and tests every code change. CD (Continuous Delivery/Deployment) automates releasing that change to environments/production with quality gates.
SDETs care because automated tests are quality gates in the pipeline — they catch regressions early on every commit/PR, not only at the end of a sprint.
Jenkins is a CI server that runs jobs/pipelines. For testing, a job typically: pulls code from Git, installs dependencies (Maven), runs TestNG/API suites, publishes reports/artifacts, and marks the build pass/fail.
stages:
- checkout git repo
- mvn clean test -Dsuite=smoke
- publish test report
- fail build if tests failPut the fastest, most reliable tests earliest so feedback is cheap.
PR pipeline → unit + API smoke
Nightly → API regression + UI critical paths
Release pipeline→ full regression packSDETs use Git to version test automation code: clone/pull, create feature branches, commit tests, open merge requests/PRs, and sync with main.
You should understand branch workflow, reviewing diffs, resolving simple conflicts in test code, and never committing secrets (tokens, passwords).
git checkout -b feature/add-order-smoke
# add tests
git add .
git commit -m "Add order smoke API tests"
git push -u origin HEADUseful CI outputs: TestNG/Surefire reports, pass/fail counts, failed test names, logs, screenshots/videos for UI failures, and optionally Allure/HTML dashboards.
Artifacts help developers understand failures without rerunning blindly on their machine.
Common stages: Checkout → Build/Compile → Unit tests → Package → Deploy to QA → API/UI smoke → (optional) broader regression → Publish reports → Notify.
checkout → mvn package → deploy qa → api smoke → ui smoke → reportA quality gate is an automated rule that blocks promotion if criteria fail — e.g. smoke tests must pass, no open Sev-1, coverage threshold on new code, critical lint/security checks green.
IF smoke == FAIL → block deploy to STAGEA Jenkinsfile defines pipeline stages in source control so CI is versioned with the app/tests. Changes to how tests run go through PR review instead of clicking around the Jenkins UI only.
pipeline {
stages {
stage('Smoke') { steps { sh 'mvn test -Dsuite=smoke' } }
}
}Useful parameters: environment (QA/Stage), suite type (smoke/regression), browser, branch/build number, and feature flags. Parameters let one job run many controlled variants without duplicating pipelines.
ENV=QA
SUITE=smoke
BROWSER=chromeStore secrets in Jenkins credentials/secret managers, inject at runtime as env vars, and never commit passwords/tokens into Git or Postman exports. Rotate credentials and use least-privilege test accounts.
export API_TOKEN=${JENKINS_SECRET_TOKEN}
mvn testTrack flakes, quarantine with a ticket if needed, fix root cause quickly, and avoid endless reruns as the default. Optional single retry can reduce noise temporarily, but repeated retries hide real instability.
Archived artifacts let anyone diagnose a failed build later without re-running. Keep HTML/XML reports, logs, and UI screenshots for a reasonable retention period tied to release needs.
Feature/PR branches: fast smoke (unit + critical API/UI). Main/release branches: broader regression and release gates. This balances developer feedback speed with release confidence.
PR → smoke
main nightly → regression
release tag → full gatePromotion moves a build through Dev → QA → Stage → Prod. Each stage has entry gates: deploy success + required test packs green. Testers validate in QA/Stage; prod relies on prior gates plus monitoring/canaries.
Build #1245 → QA smoke pass → Stage regression pass → Prod approveNightly jobs run broader regression that is too slow for every commit. They catch environment drift and integration issues overnight so the team sees failures in the morning before release activities.
0 2 * * * jenkins regression jobUse deterministic data, explicit waits, isolated environments, retries only with caution, good logging, and quarantine process. Prefer API checks for rules and keep UI thin. Measure flake rate and act on it.
Notify the right channel/people with build link, failed suite name, and quick summary. Avoid spamming every success to everyone. Critical release gates may email/Slack commit authors + QA leads.
SDETs own the test content and quality gates — suites, stability, reports, pass/fail meaning. DevOps often owns infrastructure agents, cluster permissions, and pipeline scaffolding. Best teams collaborate: SDET defines what must run; DevOps helps make it run scalably.