Hi everyone,
I’m doing a small non-sales research exercise about how solo QA/test-automation practitioners handle CI failures in browser/API automation.
I’m especially interested in cases where tests pass locally but fail intermittently in CI, and how people decide whether the failure is a real regression, flaky test, environment issue, test-data issue, or something else.
I’m not selling anything, and I’m not asking for confidential logs, screenshots, company names, customer data, or proprietary examples. Negative answers are useful too: if this is rare, solved, or not a meaningful problem for you, that is valuable signal.
If you currently maintain or heavily own browser/API automation and personally triage CI failures, I’d be grateful for either:
- a high-level reply here about your current triage workflow; or
- a structured async response / short call if you volunteer for that.
Useful high-level questions:
- In the last 90 days, did you have any CI automation failure where the cause was unclear?
- What did you check first, second, and third?
- How often does this interrupt normal work?
- What do you currently do with tests that fail intermittently but still seem valuable?
- What information do you wish you had immediately when a CI failure appears?
Please keep examples anonymized and avoid sharing anything sensitive.