Happy paths should be automated, and that part isn't up for debate. A suite that runs the same core flows on every commit is what actually keeps a release stable, and there's no version of "we'll just
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.