QA strategy: what it decides and how to write one
A QA strategy sets which risks matter, which testing answers each, who owns every check and what a release must show. What the document holds, with an example.
Notes on feedback, evidence and shipping
How we build Notarus, what we learn from bug reports, and guides for teams that want fewer “which browser?” threads.
How to write a user story a tester can check
How to write a user story backwards: name who would notice it going wrong and what they would see, then write the As a, I want, so that sentence last.
More posts
- A HAR file is a credential dump
- Acceptance criteria examples, by format
- A code freeze is a regression test you skipped
- Regression testing in software testing
- Regression vs integration testing
- Which browser is the wrong cross-browser question
- QA team structure is who reads the reports
- Conflicting stakeholder feedback is two pages
- Match a test environment where the bugs live
- A client approval must say what it covers
- A creative review that ends in notes has not ended
- A design approval with no version approves nothing
- Usable design feedback names a goal and a place
- Improve software quality by classifying escapes
- Three QA best practices carry a small web team
- QA in agile happens at three sprint boundaries
- Testing metrics that count activity prove nothing
- Acceptance criteria vs definition of done
- How to write acceptance criteria a build can fail
- How to write test cases worth a second run
- A test case review looks for the missing case
- Bug vs feature is settled by what was written down
- Bug triage is a decision per ticket, not a meeting
- Bug priority is a decision you defend, not a score
- A QA process is a set of gates, not stages
- Why we made the MCP server a rule, not a feature
- Logging an object runs code, or loses data
- What a third-party script leaves behind
- A notification outlives its permission
- What redaction cannot reach
- An anchor records what was pointed at
- Regression testing in agile needs a column
- When an export stops being a download
- Manual regression testing is a filing problem
- A plan limit has three surfaces
- UAT best practices end where the finding starts
- A bounded buffer is a triage policy
- Two-way sync needs an authority
- Consent is checked in a console
- Audit storage, not cookies
- What a rate limit can key on
- An audit trail writes before it knows the answer
- The second attack surface in a ticket export
- The gap in a ticket's evidence has an owner
- The hard part of session replay
- The bypass role is the one that proves nothing
- Screenshots are a second render
- Reporter identity is a ladder, not a gate
- The Host Isolation Contract
No newsletter yet, but there is a feed
It carries every post, in the same order as this page, and nothing else.
Fewer threads, more evidence.
Try the widget on the Free plan.