Trace a CI Failure Before Asking for a Fix
Use Five Whys to move from CI symptom to fixable root cause in an agent-assisted debugging task.
An agent PR passes locally but fails Playwright in CI: Save button not visible on the billing settings page. Five Whys: symptom -> environment difference -> patch assumption -> controllable cause The common trap is to rerun CI or increase a timeout before checking whether the failure reveals a real viewport, data, order, or environment assumption. Why 1 Why did CI fail? The Save button was not visible when the test tried to click it. Start with the observable failure, not a theory. Why 2 Why was it hidden? The new billing banner pushed the button below the fold. Connect…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in