We have a 1,200-test suite built over 4 years. Good test coverage, but: - No documentation of test strategy or…
17 discussions
We have a 1,200-test suite built over 4 years. Good test coverage, but: - No documentation of test strategy or…
I'm based in Southeast Asia and targeting remote SDET roles at US/European companies. The job market feels opaque.…
I see test.step() mentioned in Playwright docs but I'm not clear on when it's worth the extra nesting. From what I…
Over the past few months I've been experimenting with Claude and GitHub Copilot for test case generation at work. Mixed…
The ecosystem moves fast — new Playwright releases, pytest plugins, AI testing tools, framework comparisons. I feel…
Before trace viewer, debugging a CI failure meant adding console.log, pushing, waiting 8 minutes for CI, repeat.…
We want to add test result notifications to our Slack channel after each CI run. Before I build this out I want to know…
We use pytest marks for test organisation: @pytest.mark.slow, @pytest.mark.integration, @pytest.mark.smoke. In theory:…
0 votes · select an option to vote
Our engineering director wants 80% code coverage enforced in CI. I understand the intent but I'm worried about…
0 votes · select an option to vote
Six months ago our test pipeline blocked PRs for 45 minutes. Today it's 8 minutes. Here's every change we made, in…
I've been systematically using Claude for test maintenance tasks (not generation) for 3 months. Honest findings: Tasks…
0 votes · select an option to vote
Test names are the first thing you read when a test fails in CI. After years of bad names, here's the convention our…
People often share CI setups. Here's my local setup for writing and debugging tests: VSCode extensions: - Playwright…
For the first 4 years of my QA career I wrote formal test plans for every feature. Last 2 years: I've written zero.…