All Stories
Tester got blamed
- A Small Minority
- Accepted Risk
- Appropriate Error Message
- Blocked by QA
- Flaky Checkout
- It Was in the Requirements
- Just Test the Happy Path
- More Evidence
- No QA Required
- Please Retest
- PowerPoint Recovery
- Production-Like Test Data
- Read-Only Access
- Regression Scope
- Safari Support
- Severity Negotiation
- Signed Off
- Tested by the Developer
- Testing Delayed the Project
- The Bug That Became a Feature
- The Controlled Demonstration
- The Defect Workshop
- The Feature Flag
- The Friday Defect Count
- The Friday Release
- The Green Status
- The Known Issue
- The No-Blame Review
- The Risk Owner
- The Tester Who Broke Nothing
- The Two-Day Estimate
- UAT Sign-Off
- User Error
- We Don’t Need Testers
- Works on My Machine
- Wrong Build
Tester actually did it
- A Genuine Tester Update
- Fastest Regression Ever
- Forty-Seven Defects
- From a Developer
- My Finest Test Case
- The Automation Suite
- The Copied Defect
- The Defect Filter
- The Environment Defect
- The Final Evidence Pack
- The Financial Defect
- The Missing Button
- The Payment Stub
- The Production Email Test
- The Shared Password
- The Smoke Test
- The Test Customer
- The Two-Pixel Defect
Testy Tips
- Ask What Changed Before Retesting
- Ask What Else Uses the Component
- Challenge Works on My Machine
- Check the Response Body
- Check the Test Data Before Blaming the Code
- Get the Business Rule from the Business
- Group Defects by Root Cause
- Make Automated Tests Fail
- Name the Release Decision-Maker
- Put the Build Number in Every Defect
- Record the Exact Time
- Record the Recommendation and Decision Separately
- Reproduce from a Clean Starting Point
- Save the Original Requirements
- Separate Severity from Priority
- Test How Users Abandon the Journey
- Test Retry Behaviour Deliberately
- Test with the Weakest Permissions
- Verify the Deployment Before Retesting
- Write Expected and Actual Results