The Scenario
You are applying for junior QA roles. Hiring managers want proof you can write a bug report that a developer can actually act on. Without work experience, your portfolio is the only evidence.
The Brief
Pick a publicly accessible SA app or website (Takealot, FNB or Capitec banking app, MyGov, gov.za services, a local retailer). Use it the way a curious user would, looking for genuine defects. Document each bug as a structured report.
Deliverables
- Five bug reports, each containing: title, environment (browser, OS, app version), preconditions, steps to reproduce, expected result, actual result, severity, and priority
- For at least three of the bugs, include a screenshot or short screen recording link
- A short cover note explaining your overall approach: which areas you focused on, which test heuristics you used (boundary values, error handling, navigation), and what you would test next if you had more time
Submission Guidance
Severity is technical impact (does it crash, lose data, look broken). Priority is business urgency (how soon must it be fixed). They are independent. Be ready to defend why you assigned each one separately.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.