The card below is the “product under test”. Use guided mode to see the bug list upfront, or blind mode to find them yourself first.
Techniques: Defect analysis, Test planning
Junior tester’s report: Sprint 18 test summary
Review this report as a test lead. Identify what the junior tester did well, missed, or got wrong.
What I tested
I tested the new customer search feature. I searched for customers by name and it worked. I also searched for nothing and it showed all customers which I think is fine.
Bugs found
- BUG-A: The search results page is slow (severity: Low)
- BUG-B: When you type a name with a capital letter it finds the customer but lowercase doesn’t — so searching “aroha” returns nothing but “Aroha” works (severity: Low)
- BUG-C: The page title still says “Customer list” instead of “Customer search” (severity: Critical)
What I didn’t test
I didn’t test on mobile or other browsers because I didn’t have time.
Your findings
0 / 0 bugs foundTick each bug as you confirm it on the page above. Progress saves automatically.
Write down every bug you find. Be specific — where it is, what’s wrong, what it should be.
Planted bugs (5)
- Case-sensitive search means users can't find customers unless they know the exact capitalisation. This is a usability defect that would affect every user — Low severity is too low.
- A wrong page title has no impact on functionality. Critical is reserved for data loss, security issues, or complete feature failure. This is Low severity.
- A performance bug without a measurement is not actionable. The report should state the observed response time and the expected threshold (e.g. 'loads in 8 seconds, expected under 2 seconds').
- Returning all customers on empty search may expose customer data that shouldn't be visible to all users. The tester should have verified this is the specified behaviour, not assumed.
- The summary only covers normal name searches. Missing: special characters (apostrophes in te reo Māori names), SQL injection, numeric input, very long strings, and empty/whitespace-only input.
Coaching: acknowledge what they did right (found BUG-B), correct the severity ratings with explanation, and give specific guidance on what to test next time — don't just say 'you missed edge cases', name them.