QA & Software Testing
CI Test Integration
6 practice questions. Free questions open a full answer guide; the rest unlock with Pro.
- Why do teams run automated tests automatically in a CI pipeline on every change, instead of just having developers run them locally before they push?
- Your team requires every pull request to pass CI before merging, yet main still occasionally goes red right after a merge. How can a PR pass all its checks and still break main, and how would you prevent it?Go Pro
- Your CI pipeline has gotten slow and untrustworthy: builds take 40 minutes and the team has learned to just re-run red builds until they go green. As a senior engineer, how do you reason about restoring trust in CI, and what do you tackle first?Go Pro
- A flaky integration test fails roughly one run in ten and is blocking merges. One engineer wants to wrap it in an automatic retry so the pipeline goes green; another wants to delete it. As the senior on the team, how do you decide what to actually do with it?Go Pro
- How would you decide which tests run on every pull request versus later in the pipeline, and what keeps the per-PR suite fast as it grows?Go Pro
- What does it mean for a test to be flaky, and why are flaky tests a problem when they run in a CI pipeline?Go Pro
Want questions matched to your role? Paste a job title, job description, or CV for a personalized set, or go Pro to unlock the full bank.