1. Quality Gates intermediate

    A 12-year-old service has 4% test coverage and no tests for its core logic. It changes twice a year. Do you apply your quality gates to it?

    2 min answer legacypragmatismgovernance
  2. Quality Gates advanced

    A security vendor's release process gates sensor code behind staged rollout with canaries, and ships detection content through a separate path validated by a content checker and pushed to every customer within minutes. In July 2024 CrowdStrike's own root cause analysis describes exactly this shape, and a mismatch between 21 fields supplied and 20 fields read produced an out-of-bounds read that crashed around 8.5 million Windows hosts. Review the process. What would you remove, what would you add, and what would you leave alone?

    3 min answer crowdstrikerelease-gatesstaged-rolloutconfig-as-code
  3. Quality Gates intermediate

    An organisation's quality gates have accumulated and now block releases without reducing defects. How should the gate set be rationalised?

    2 min answer quality-gatesevidenceblockingrationalisation
  4. Quality Gates intermediate

    Leadership mandates 80% code coverage across all services. What do you say?

    2 min answer metricstestinggovernance
  5. Quality Gates intermediate

    Which automated quality gates are worth blocking a release on, and which are ceremony?

    2 min answer quality-gatescoveragestatic-analysisci
  6. Quality Gates intermediate

    Your CI suite fails about one run in four, and roughly 80% of those failures pass on a re-run. Developers now re-run by reflex, including on real failures. JetBrains ships flaky-test detection in TeamCity based on flip rate. Design the gate, and say what you refuse to do.

    3 min answer jetbrainsteamcityflaky testsquality gates