15 discussions
Our Playwright suite has 200+ tests and login takes 3–4 seconds each time. Running everything serially we're losing ~15…
I'm writing a test for an admin action that should be visible to admins but hidden from regular users. The test needs…
I need to test that a CSV export button downloads the correct file with the right data. Our app generates the file…
Playwright now supports component testing (React/Vue/Svelte) which blurs the line with E2E tests. In practice I'm…
We have a real-time dashboard that uses WebSockets and I'm struggling to write reliable tests for it. The main…
We have several user flows triggered by emails: registration confirmation, password reset, order confirmation. I need…
Starting a new web app project next month and we're deciding between Playwright and Cypress for E2E. The app is a React…
We want to add accessibility testing to our suite. We have a React app with ~60 pages. Current thinking: - axe-core +…
We have a handful of E2E tests that take 4–6 minutes each. They cover complex user journeys (onboarding flow,…
We want to add visual regression tests for our design system components (50+ components) and a few key pages. Tools…
We have 8 microservices. Testing strategy question: where do you draw the line between testing each service in…
The classic answer is 70% unit / 20% integration / 10% E2E. But I've never worked on a team that actually hits that…
Most people run headed during development and headless in CI. But I'm curious about the exceptions: - When do you run…
My new company uses Cucumber for all E2E tests. Feature files are written in Gherkin, step definitions in Java. After 2…
Theoretically we should test Chrome, Firefox, Safari, Edge. In practice: - Chrome is 65% of our user base - Safari is…
