Module 5 · Working like a QA engineer Lesson 14 of 15
Bug triage, metrics and the words that get read
A tester is judged by the bugs that got fixed, not the bugs that got filed. Triage is short, ordered by severity and priority, and every report names the person who needs to act.
The concept
Track escape rate too: bugs found in production that the tests should have caught. It is the honest measure of whether the suite is doing its job.
Never blame in the report. "The form accepts a bad date" moves a fix; "the developer forgot to validate" moves nothing and costs you the next conversation.
Week 32 - triage note
Raised 12 · Fixed 9 · Open 3 (2 x S1, 1 x S3)
Oldest open: S1 login cookie, 5 days - blocked on staging config
Escape this week: 1 (date validation) - added a regression case
Ship recommendation: hold until the two S1s are closed.Worked example
A weekly note: 12 raised, 9 fixed, 2 S1, oldest open 5 days - three numbers that show whether the build is safe to ship.
Your practice task
Write a one-paragraph triage note for a week of testing, with the counts and the oldest open bug.
Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.
Key takeaway
Track escape rate too: bugs found in production that the tests should have caught.
Keep your place in this course
A free account saves which lessons you have finished and unlocks the certificate. The lesson itself stays free to read.
Create free account or sign inCourse complete
You finished every lesson.
Your certificate is ready, and the projects you built are the proof to attach to an application.
Almost there
15 lessons left of 15
Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.