1. End-to-End Test Economics advanced

    Your 800-test end-to-end suite takes 90 minutes and fails roughly half the time for reasons unrelated to the change. The team re-runs until green. What do you do?

    2 min answer testingreliabilitystrategy
  2. Environment Parity intermediate

    A change passes every test in staging and fails immediately in production. Staging is a faithful copy of the topology. What are the most likely causes, and what would you change?

    2 min answer environmentsparitytesting
  3. Environment Parity advanced

    A platform has already been through the failure Fastly published in 2021 - a defect shipped on 12 May that a customer's valid configuration armed on 8 June - and has since implemented per-point-of-presence staged activation of customer configurations plus grammar-based fuzzing of the configuration surface. Six months later the same class recurs in a different subsystem. Which gap did that action list never close?

    3 min answer fastlyenvironment-paritylatent-defectcontinuous-verification
  4. Environment Parity intermediate

    A team spends a quarter making staging match production: same instance types, same data volume, same topology, same configuration management. Six months later, escapes to production are down by much less than expected. What did parity actually buy, and what did it not?

    3 min answer environment paritystagingtestingcost
  5. Environment Parity advanced

    On 14 March 2023 Reddit upgraded a Kubernetes cluster from 1.23 to 1.24 after the same upgrade had already succeeded elsewhere, and was down for 314 minutes. The upgrade removed a node label that a hand-configured Calico route reflector selected on. Which parity assumption failed?

    2 min answer redditkubernetesparityconfiguration-drift
  6. Environment Parity intermediate

    Which dimensions of environment parity actually matter, and which are safe to differ?

    1 min answer parityenvironmentsconfigurationdeployment
  7. Flaky Test Management intermediate

    A CI pipeline runs 2,400 tests in 18 minutes and fails about one run in four for reasons unrelated to the change. To stop the interruptions, the team enables automatic retry: any failing test is re-run twice, and the build is green if it passes on any attempt. What happens over the following six months?

    3 min answer flaky-testsciretriessignal-loss
  8. Flaky Test Management intermediate

    A suite has persistent flaky tests. Why is tolerating them worse than deleting them, and what policy works?

    2 min answer flakinesstrustquarantinepolicy
  9. Flaky Test Management intermediate

    A team's CI suite fails roughly one run in three for reasons unrelated to the change. Everyone reruns until green. How do you recover the situation?

    2 min answer testingflakinesscisignal
  10. Flaky Test Management intermediate

    A test suite has a 4% flake rate. The team re-runs failed builds. What is the actual cost, and what policy fixes it?

    2 min answer browserstackflakytrustpolicy
  11. Flaky Test Management beginner Multiple choice

    One integration test fails only in CI, only on Tuesdays, only in the 00:30 UTC scheduled run. It passes locally and on every pull-request run. What do you look at first?

    2 min answer flaky-testsclockdiagnosisquarantine
  12. Flaky Test Management intermediate

    Write the policy for handling flaky tests. What are the rules?

    2 min answer testingcipolicy