Q&ATrending
How do you onboard new team members to a large legacy test suite?We have a 1,200-test suite built over 4 years. Good test coverage, but: - No documentation of test strategy or…
1.2k viewsBe the first to answer
17 discussions
Q&ATrending
Where do you find remote SDET roles and what terms are actually negotiable?I'm based in Southeast Asia and targeting remote SDET roles at US/European companies. The job market feels opaque.…
1.9k viewsBe the first to answer
Q&A
Is test.step() worth using in Playwright? What does it actually give you?I see test.step() mentioned in Playwright docs but I'm not clear on when it's worth the extra nesting. From what I…
453 viewsBe the first to answer
DiscussionTrending
AI-assisted test generation — real productivity boost or just hype?Over the past few months I've been experimenting with Claude and GitHub Copilot for test case generation at work. Mixed…
936 views
Q&ATrending
How do you actually stay current with the test automation ecosystem?The ecosystem moves fast — new Playwright releases, pytest plugins, AI testing tools, framework comparisons. I feel…
1.3k viewsBe the first to answer
DiscussionTrending
Playwright trace viewer completely changed how I debug failing CI testsBefore trace viewer, debugging a CI failure meant adding console.log, pushing, waiting 8 minutes for CI, repeat.…
2.2k views
Q&ATrending
What test metrics do you actually report from CI to Slack or Teams?We want to add test result notifications to our Slack channel after each CI run. Before I build this out I want to know…
927 viewsBe the first to answer
Q&ATrending
How granular is your test tagging strategy and does it actually get used?We use pytest marks for test organisation: @pytest.mark.slow, @pytest.mark.integration, @pytest.mark.smoke. In theory:…
817 viewsBe the first to answer
Q&ATrending
How do you balance test coverage percentage targets vs meaningful test quality?Our engineering director wants 80% code coverage enforced in CI. I understand the intent but I'm worried about…
2.4k viewsBe the first to answer
DiscussionTrending
How we cut CI from 45 minutes to 8 minutes — a practical breakdownSix months ago our test pipeline blocked PRs for 45 minutes. Today it's 8 minutes. Here's every change we made, in…
5.3k views
DiscussionTrending
Three months using Claude for test maintenance — what I actually foundI've been systematically using Claude for test maintenance tasks (not generation) for 3 months. Honest findings: Tasks…
4.6k views
PollTrending
What percentage of your time is writing new tests vs maintaining existing ones?0 votes
3.1k views
DiscussionTrending
Test naming conventions that actually communicate intent — what works for our teamTest names are the first thing you read when a test fails in CI. After years of bad names, here's the convention our…
3.8k views
DiscussionTrending
My local test development environment setup — VSCode extensions and tools I actually usePeople often share CI setups. Here's my local setup for writing and debugging tests: VSCode extensions: - Playwright…
3.3k views
DiscussionTrending
Why I stopped writing formal test plans and what replaced themFor the first 4 years of my QA career I wrote formal test plans for every feature. Last 2 years: I've written zero.…
4.3k views