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.

A pattern of design commonly used and conceptually intuitive that is otherwise known to be ineffective, sub-optimal, or counter-productive to the goal.Examples include Spaghetti Code, the Testing Ice Cream Cone, Code Coverage Mandates, Unfalsifiable Test, Skip The Test, and Watchmen Tests

Cultivate professional trust and accountability by using detailed documentation to demonstrate due diligence and quantify risk for stakeholders.