Shawn Vernier
Quality Engineer
He/Him
The answer to quality is context.
Open To
Work
Write
Teach
Speak
Mentor
CV Reviews
Podcasting
Mentee
Review Conference Proposals
Achievements
Certificates
Level up your software testing and quality engineering skills with the credibility of a Ministry of Testing certification.
Activity
achieved:
This badge is awarded to members who join a Ministry of Testing Chapter.
earned:
Joined TWiQ — This Week in Quality chapter
joined:
Meet quality people at This Week In Quality. Tune in for the latest news, discussions, and insights from across the world of software quality, testing, and community.
Join a live audio-only session as we connect with the people behind the practice, tackle emerging trends, and celebrate the passion and expertise of those shaping the future of quality.
In quality we gather.
earned:
Why software testers should write documentation even if no one else reads it
earned:
Creating a resilient test framework with the Playwright Page Object Model (POM)
Contributions
I've never done a proper podcast, yet here I am.20 episodes in.Weekly cadence.Great quality conversations.Catching up with old friends.Making some new ones.100% stepping outside of my comfort zone....
Sometimes the most effective guardrail isn't the most sophisticated one
AI needs guardrails to play by the rules and work better
An exploration of how epistemology underpins quality thinking, helping quality people examine what they know, how they know it, and how that shapes their quality choices.
Partially back from a two month hiatus - apologies this took forever but it never left my backlog!From the original moment: AMA about Epistemology - the practice of testingAdy asked: "Through simil...
Partially back from a two month hiatus - apologies this took forever but it never left my backlog!From the original moment: AMA about Epistemology - the practice of testingDemi asked: "What is the ...
Partially back from a two month hiatus - apologies this took forever but it never left my backlog! From the original moment: AMA about Epistemology - the practice of testingSimon asked: "Can you sh...
Partially back from a two month hiatus - apologies this took forever but it never left my backlog!From the original moment: AMA about Epistemology - the practice of testingAdy asked: "If quality pr...
With SQEC now fully live, the community swaps stories about new roles, flaky tests, accessibility audits, and why shared language, pairing, and “being the duck” can make quality work easier.
QA usually owns the automated tests. When a company mandates a level of automation, QA spends a part of their time growing the number and scope of the automated tests. Over time, maintenance of these tests can become expensive, and most of a QA teams time can be spent maintaining the existing automation while adding all new tests into the automation. This becomes a perpetual treadmill of building test automation that can take time and energy away from other valuable QA tasks such as design and specification review, functional testing, exploratory testing, interactive testing, etc. "Now, here, you see, it takes all the running you can do, to keep in the same place" - The Red Queen, Through the Looking Glass
Master the RICCE framework to transition from manual testing to AI-augmented automation by leveraging structured prompting and the Playwright MCP agent ecosystem.
Implement the Playwright Page Object Model (POM) to build maintainable, resilient test suites by centralizing page interactions and separating them from test logic.
