The Scenario
Most SA QA teams now use a mix of scripted and exploratory testing. Hiring managers want testers who can find bugs that pre-written test cases miss. The deliverable here is the structured session note that proves you can do that.
The Brief
Pick a SA web app or mobile app you have access to. Write a charter (a one-paragraph mission for the session), then run an actual 90-minute exploratory test session, then write up a session report.
Deliverables
- A test charter: a one-paragraph mission statement (what you are exploring, why, and what you are not exploring)
- A session report including: areas covered, areas skipped and why, test ideas you explored, defects found (with full bug report format), and questions raised for the team
- A timesheet breakdown: setup time, test design, execution, bug investigation, reporting (the standard "session-based test management" breakdown)
- A reflection paragraph: what surprised you, what you would charter next, and what you learned about the product
Submission Guidance
Exploratory does not mean unstructured. The charter constrains what you focus on. The session report proves the work. If you cannot remember what you did 90 minutes after the session, it is not a useful artefact.
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.