Your Green Test Suite Is Hiding Real Bugs
Handling unexpected alerts or removing assertions to make tests pass doesn't fix anything — it buries bugs. Here's how to spot and stop these patterns.
Hi, I'm
Senior SDET specializing in test automation at enterprise scale
10+ years at Fortune 500 companies — Telecom, Insurance, Retail, Financial Services
I write about test automation, CI/CD pipelines, Java, and QA best practices. Building quality into software, one test at a time.
Handling unexpected alerts or removing assertions to make tests pass doesn't fix anything — it buries bugs. Here's how to spot and stop these patterns.
How a 'flaky' Playwright test exposed a shared test user race condition in our parallel suite, and the isolation patterns that fixed it for good.
Why onceDialog stays registered when no dialog fires, silently eating the next dialog from an unrelated action — and the onDialog/offDialog pattern that fixes it.
Set up a standalone Allure report portal with Docker that any CI tool can push to, so the whole team can review results without logging into Jenkins daily.
Replace emailed Extent Report HTML files with a persistent Allure portal on Jenkins, so the team gets one URL, full history, and zero downloads to manage.
How onceDialog fixes permanent handler leaks from onDialog — and the one case where it creates a new problem. Includes the onDialog/offDialog pattern for dialogs that might not fire.