Shift Left Without Burning Out
Shift left usually gets implemented as 'the tester does more, earlier'. Here's what it should mean instead, and how to push back when it doesn't.
Open to QA and test automation roles
Software Testing Engineer. I build test automation that teams actually trust.
Six+ years of manual and automated testing across web, mobile and APIs. I work mainly with Playwright, Pytest and Selenium, and I write here about what holds up in real projects and what doesn't.
Frameworks that stay readable after six months and a dozen contributors.
Exploratory testing and bug reports developers can act on immediately.
Deciding what to test where, so the pipeline stays fast and honest.
Tests running on every pull request, with reports the whole team reads.
Shift left usually gets implemented as 'the tester does more, earlier'. Here's what it should mean instead, and how to push back when it doesn't.
Four performance test shapes, what each one is actually looking for, and the k6 configuration for all of them.
Folder layout, fixtures instead of page objects, and the conventions that keep a shared test suite readable once more than one person is writing in it.
I reply to every message within 24 hours.