Six months ago our test pipeline blocked PRs for 45 minutes. Today it's 8 minutes. Here's every change we made, in…
24 discussions
Six months ago our test pipeline blocked PRs for 45 minutes. Today it's 8 minutes. Here's every change we made, in…
Before trace viewer, debugging a CI failure meant adding console.log, pushing, waiting 8 minutes for CI, repeat.…
This is the most frustrating debugging scenario I encounter regularly. Test passes 100% locally, fails 30–80% in CI. My…
Our test suite: 1200 Playwright tests, currently runs serially in ~55 minutes. Target: under 10 minutes for the PR…
0 votes · select an option to vote
Starting a new performance testing initiative. Our stack: Node.js microservices, REST APIs, ~50k requests/day in…
Theoretically we should test Chrome, Firefox, Safari, Edge. In practice: - Chrome is 65% of our user base - Safari is…
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're moving off Jenkins and evaluating GitHub Actions vs GitLab CI (we're already on GitLab for source control). For…
My company is adding basic security testing requirements. Leadership wants SDETs to own it since we already own…
We have two teams: one owns a user service (Python/FastAPI), one owns a frontend (Next.js). The user service API is the…
We have two camps on our team: Camp A (shared environment): Tests run against a shared staging server. Fast to set up,…
Most load test examples I see just report numbers (p95, p99, RPS) without failing the test definitively. I want our…
We have test credentials (API keys for sandbox environments, DB passwords, OAuth tokens) that need to be available in…
We have a handful of E2E tests that take 4–6 minutes each. They cover complex user journeys (onboarding flow,…
We're running Selenium Grid 3 on 6 VMs and it's a maintenance headache — node crashes, session leaks, version…
We need to parallelise a 600-test pytest suite. Current serial runtime is ~22 minutes, target is under 8 minutes. I've…
We want to add test result notifications to our Slack channel after each CI run. Before I build this out I want to know…
Our test suite hits a third-party API (Stripe sandbox) and we occasionally get 429s in CI, causing random test…