15 discussions
Our flake rate is ~4% per test in CI (down from 9% after a big cleanup push). With 800 tests that means ~32 flaky…
We integrate with: Stripe (payments), SendGrid (email), Twilio (SMS), and Segment (analytics). Each has a sandbox/test…
We have a real-time dashboard that uses WebSockets and I'm struggling to write reliable tests for it. The main…
Our test suite hits a third-party API (Stripe sandbox) and we occasionally get 429s in CI, causing random test…
This is the most frustrating debugging scenario I encounter regularly. Test passes 100% locally, fails 30–80% in CI. My…
StaleElementReferenceException is the bane of our Selenium suite. We get maybe 20–30 per CI run across 800 tests,…
We had a bug where a function-scoped test was accidentally using a session-scoped fixture that mutated shared state.…
I had an idea: take our flaky test history (test name, failure messages, stack traces, timestamps) and feed it to an…
Flaky tests are killing our team's confidence in the test suite. We're seeing around 8–12% flake rate on our Playwright…
We have two camps on our team: Camp A (shared environment): Tests run against a shared staging server. Fast to set up,…
Our payments API calls Stripe, our notifications API calls SendGrid, and our geolocation API calls Google Maps. All…
We have engineers in India, UK, and US. Our tests occasionally fail due to timezone-dependent logic: - Date range…
We have 8 microservices. Testing strategy question: where do you draw the line between testing each service in…
We're an SDET team testing a service that uses a database we don't own — the schema is managed by a platform team and…
Most testing focuses on the output: did the API return the right response? But I've started treating observability as a…
