Skip to main content

Module 9 · Final project

Project part 2: bug reports and test summary

Run your checklist, report what you find, and summarise the results honestly.

About 6 min reading and 90 min practice (estimates)

Loading progress…

Read

Learning objectives

  • Execute a checklist and record results.
  • Write reproducible bug reports for what you find.
  • Write a test summary that states coverage, results and remaining risk.

Explanation

Work through your checklist in the Practice shop. When something differs from the expected behaviour, reproduce it, then use Report a bug in Practice — it attaches the shop's state and your recent actions as evidence, and tells you whether you reproduced one of the planted defects. Practice also lets you export your reports as Markdown.

Finish with a test summary — usually less than a page. It helps the team decide what to do next, so it must be honest about what wasn't tested.

Test summary — <product>, <build>, <dates>
Scope: what was tested (and in which languages/browsers)
Not tested: what was out of scope or skipped, and why
Results: checks run / passed / failed; bugs found by severity
Open risks: what could still go wrong, and how likely/serious
Recommendation: e.g. "fix the two high-severity bugs, then release"
A compact template.

Example: a concise summary (fictional numbers)

Test summary — Dar Al Souq training shop, Practice, 26 Oct
Scope: catalogue, cart, codes, delivery, checkout; EN and AR; Chrome desktop and a 390 px emulated phone
Not tested: Safari, real devices, performance, security
Results: 31 checks, 27 passed, 4 failed → 4 bug reports
  (1 high, 2 medium, 1 low)
Open risks: totals with combined promotions only partly covered
Recommendation: fix the high-severity totals bug first; retest
  codes and delivery together afterwards

Common mistakes

  • Writing "everything works" when only part was tested.
  • Listing bugs without severity or links to the reports.
  • Hiding untested areas to make the summary look better.

Try

Practise what you just read. Answers are checked here; nothing is graded publicly or counts toward Bug Arena.

Exercise

Run your checklist in Practice, submit your bug reports there, then write your test summary using the template. Compare it with the sample solution.

Write your answer first, then compare it with the sample solution. It stays on this page only and isn't sent anywhere.

Review

Check yourself — you should now be able to:

  • Execute a checklist and record results.
  • Write reproducible bug reports for what you find.
  • Write a test summary that states coverage, results and remaining risk.

Practise in QA Lab

Continue

When you’re ready, mark the lesson complete in the Try step and move on.

Marked as read when you reach the end of the lesson.