Top 3 Ci Interview Questions
Browse 3 real-world technical and behavioral interview questions about Ci. Review scenarios, edge cases, and architectural best practices.
Two teams own two services that talk to each other. How do you stop one breaking the other without running both together in a shared environment?
Contract testing has each side verify itself against a shared description of the interaction, so consumer expectations are checked against the provider's real behaviour without the two ever running together. Mismatches surface in each team's own pipeline, not in a shared environment days later. It also connects api testing to the point an interviewer is testing.
A test fails in CI and all you get is 'expected true, got false'. What should the framework have given you instead?
A failure has to be diagnosable from its artefacts alone, because nobody can attach a debugger to a CI run: that means assertions that report the compared values, a message naming the business expectation, and captured evidence of the state at the moment of failure. Use this automation answer to show the decision, trade-off, and evidence rather than a memorised definition.
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.