Skip to main content
Automation Juice 🥤
Log inBrowse courses

Test framework and CI interview questions, 2026

For mid-senior roles. Demonstrates engineering hygiene.

Framework and CI questions sort senior QA candidates from junior ones. Interviewers want to see that you have actually built and maintained a test framework: layered structure, fixtures, no selectors in tests, reports, screenshot-on-failure, CI integration with GitHub Actions or GitLab CI. Talk about real decisions and tradeoffs; vague answers about "best practices" lose.

2 questionsIndia context · 2026
  1. Q1What does a good QA test framework structure look like?
    What the interviewer is really listening for

    Looking for: layered separation, fixtures, no selectors in tests, reports, screenshot-on-failure.

    Sketch answer (adapt, do not memorise)

    Layered: `tests/` (story-level assertions), `pages/` (POM), `api/` (clients), `data/` (factories), `utils/` (config, logging). Driver is a fixture (one per test). Tests contain zero selectors. Reports via pytest-html or Allure. Screenshot-on-failure hook in conftest.py. Markers (`@pytest.mark.smoke`) for CI subsets.

  2. Q2How would you set up CI for a Python test suite?
    What the interviewer is really listening for

    Looking for: pipeline-as-code, fresh environment each run, fast feedback, artifact storage.

    Sketch answer (adapt, do not memorise)

    GitHub Actions workflow: checkout → setup-python with pip cache → install deps → run pytest → upload report artifact. The pipeline runs on every push and PR from a fresh VM. Smoke subset under 5 min; full suite via a separate workflow nightly. Failures attach the HTML report.

More interview prep