A collection of well-documented, real-world style defect reports demonstrating defect reporting, severity/priority assessment, and reproducibility.
This repository is maintained by an SQA Engineer and showcases the kind of structured, evidence-driven bug reports logged in tools such as Jira during real testing cycles. All reports are generalized and contain no confidential data.
- Handman — A service marketplace connecting customers with home-service professionals (web & mobile).
- Africa Travel Hub — A travel booking platform for flights, tours, and holiday packages across Africa.
- Wanyumba — A property / real-estate listing and discovery platform.
- Clear reproduction steps — concrete, numbered, deterministic steps that let any engineer reproduce the defect.
- Severity vs Priority — each report separates technical impact (severity) from business urgency (priority), and justifies both.
- Evidence — references to screenshots, screen recordings, console logs, and network traces that support each finding.
- Environment details — browser/device, OS, build/version, and preconditions captured for every defect so issues are not "works on my machine".
- Variety of defect types — functional, UI, validation, data integrity, performance, security, and usability issues.
Bug-Reports-Repository/
├── README.md
├── templates/
│ └── Bug-Report-Template.md
├── handman/
│ ├── BUG-HM-001.md ... BUG-HM-007.md
├── africa-travel-hub/
│ ├── BUG-ATH-001.md ... BUG-ATH-006.md
└── wanyumba/
└── BUG-WNY-001.md ... BUG-WNY-005.md
Severity measures the technical impact of the defect on the system. Priority measures how urgently it should be fixed from a business perspective. They are assessed independently.
| Level | Severity (impact on system) | Priority (urgency to fix) |
|---|---|---|
| Critical | System crash, data loss/corruption, security breach, or a core flow (login, payment, checkout) completely blocked with no workaround. | Must be fixed immediately; blocks release or production use. |
| High | Major feature broken or incorrect results, but a workaround may exist; affects many users. | Fix in the current sprint / before next release. |
| Medium | Partial feature failure or noticeable functional/UI issue with an acceptable workaround; limited user impact. | Schedule for an upcoming sprint. |
| Low | Minor cosmetic, text, or edge-case issue with little to no functional impact. | Fix when convenient / backlog. |
Note: All bug reports in this repository are created for portfolio purposes using realistic but fictional data. They contain no confidential, proprietary, or production-sensitive information.