QABattle

Test Automation / Scenario

CI Pipeline: Red Alert

Main is red, three suspects, forty minutes of logs. Trace the failure to its true cause without blaming the wrong commit.

Difficulty
Hard
Format
Scenario
Points
200
Estimate
15 min

// MISSION BRIEF

Your Mission

06:12 AM. The nightly e2e run against main is red: 14 failures, all in checkout suites. Yesterday it was green.

Three commits landed overnight. You have the CI log, the failure summary, and the commit list. Play detective: what actually broke, and what do you do about the pipeline design that let it hide?

// FIRST CONTACT

Battle teaser

First artifact

CI failure summary

What is the root cause of the 14 failures?

  1. AThe order-summary refactor broke the data-testid
  2. BPayment-service v2.31's new default pool size (5) is too small for e2e parallel load → 503s → checkout page never renders the summary
  3. CThe quarantined wishlist tests destabilized suite ordering
  4. DStaging was down for all services during the run
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

cidebuggingroot-causepipelines