Article archive

Story type: Tester actually did it

The Defect Filter

I reported that there were no open defects assigned to testing. The test manager congratulated the team. Then someone opened Jira without my saved filter. There were 63 open defects. My filter had been set to: Assignee = Current User I was not assigned any of them.

Read article

The Test Customer

I created a test customer called DO_NOT_USE_TEST_ACCOUNT. It appeared in the executive demonstration. The programme director asked why our most valuable customer was called Do Not Use. The product owner said it was a data-quality issue.

Read article

The Copied Defect

I copied an old Jira defect to save time. I changed the title, steps and screenshots. I forgot to change the environment from Production to Test. The developer escalated it as a live incident before I noticed.

Read article

The Final Evidence Pack

I rejected a developer’s deployment because the release files were badly named. Then I sent the test evidence. The attachment was called: FINAL_Test_Evidence_v6_USE_THIS_ONE_REAL_FINAL2.zip

Read article

The Financial Defect

I raised a critical defect because the system total was £12,000 higher than my expected result. Finance checked the application. Development checked the calculation. I checked my spreadsheet. I had hidden twelve rows before pressing Sum.

Read article

The Shared Password

I changed the password on the shared UAT account to test password history. I forgot to tell anyone. Within ten minutes, the whole project reported that UAT was unavailable. I joined the investigation and asked whether anything had changed recently. Technically, that was a very good question.

Read article

Forty-Seven Defects

The same label was misspelled on 47 screens. I raised 47 separate defects. The developer corrected one shared component. At the weekly report, I announced that 47 defects had been fixed.

Read article

The Production Email Test

The tester ran the notification suite using production SMTP credentials. Five thousand customers received: TEST EMAIL. PLEASE IGNORE. Support received hundreds of replies asking whether they should ignore it.

Read article

The Environment Defect

I raised a blocker because the new feature was completely missing. I attached screenshots and browser logs. DevOps replied: “The deployment failed. You are testing the old release.” I changed the defect title to Deployment failed and kept my screenshots.

Read article

The Two-Pixel Defect

The designer raised a blocker because the Submit button was two pixels too low. The same button deleted the customer record. The alignment defect was fixed first because it came with a clearer screenshot.

Read article