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
28 discussions
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
Building a QA portfolio from scratch — what actually got me interviewsI spent 8 months building a QA portfolio while working a non-technical job. Here's what got callbacks vs what was…
7.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
DiscussionTrending
Why I now write integration tests before unit tests — a shift in my testing philosophyI used to follow the orthodox TDD approach: unit tests first, then integration. I've reversed this for most of my work…
5.2k views
DiscussionTrending
The 5 test anti-patterns that cost our team the most time — and how we fixed themAfter a test suite audit last quarter, we identified the problems causing the most maintenance pain. In order: 1. Tests…
8.5k views
DiscussionTrending
Using observability (logs, metrics, traces) as part of your testing strategyMost testing focuses on the output: did the API return the right response? But I've started treating observability as a…
3.6k views
DiscussionTrending
Lessons from a complete test suite rewrite — what we would do differentlyWe rewrote our entire test suite (600 tests → 800 tests, Selenium Java → Playwright TypeScript) over 8 months. Honest…
7.0k views