Latest
Acceptance criteria Product can actually sign
Vague “done” creates UAT fights. How I write acceptance criteria as observable outcomes, so the people who have to approve them can do it without a translator.
Wearable QA when the phone is not enough
Watch and band journeys break in pairing, permissions and background sync, not in screenshots. What I verify before calling wearable work release-ready.
All notes
From functional tester to Test Practice Manager
How I went from executing cases on one slice to running the test practice on a global programme: what the role added, what it never replaced, and the traps on the way.
Stakeholder engagement without meeting inflation
Alignment does not need another calendar block. The written rhythm I use to keep Product, Engineering and business owners in the loop, and the few meetings worth keeping.
Figma vs functional: catching design/reality gaps early
Design files are intent. Production is behaviour. How I compare a Figma file with the running product, journey by journey, without turning the review into pixel policing.
A Quality Maturity Matrix leadership actually uses
Most QA maturity models become wallpaper. How I build a small matrix with Engineering and Product so each cell points at a planning decision and nobody chases a score.
Hiring a functional QA consultant: questions that expose theatre
If you are buying QA help, a tool list tells you very little. These are the five questions I would ask a functional QA consultant, and what good and bad answers sound like.
When more automation hides a broken user journey
Pipelines get greener while users still struggle. Why automated tests pass over a broken journey, and how I keep functional truth ahead of technical coverage.
Remote B2B QA: embed without becoming a bottleneck
I join European product teams remotely, as a B2B contractor. This is how I keep stories, questions and release calls from queuing behind one person: me.
Defects Product thanks you for (and ones they ignore)
Not every bug earns attention. How I write defect reports that name the user impact, the business risk and the next action, and how I tell when a finding is not a defect at all.
AI in QA without fake confidence
I use AI to speed up API and performance work. I do not let a model decide that a release is safe. Where it helps in QA, and where a fluent answer gets mistaken for evidence.
Defect backlog hygiene beats writing more cases
Stale bugs drain more engineering time than missing coverage. How I sweep a defect backlog, close what is dead with a reason and leave a board Product and Engineering both believe.
UAT without theatre
User acceptance testing fails when “done” was never shared. How I set UAT up so stakeholders make a ship-or-wait decision from evidence, not from the mood in the room.
Mobile QA beyond “run it on BrowserStack”
Device farms are useful. They are not a strategy. What a farm can tell you, what only a phone in the hand shows, and what I put in a mobile test plan.
Release readiness people can actually read
Most release packs list activity. I write the readiness note as a decision aid: what changed, what was verified, what is still open and whether to ship, readable in three minutes.
Mentoring QA without cloning yourself
Mentoring QA engineers by imitation creates dependency. I hand over the criteria behind my habits, so the judgement is still there when I am not in the room.
Reference
Prefer a reader? Subscribe by RSS.