A test fails, someone reruns it, it passes, and the failure gets filed under "flaky" without anyone checking whether that's true, even though a test that fails one run in twenty and a test that fails
QA Engineer focused on users, not just test cases
I’m a QA engineer with a background in customer support, which gave me a strong sense for how bugs impact real users. I spend most of my time doing exploratory testing, working closely with developers, and building out automation with Playwright. I care about catching what actually matters, not just passing checklists.
Markdown supported · ⌘↵ to post
No responses yet.