TechRasta QA portfolio templates
Published 29 October 2026
Guide: https://techrasta.com/blog/qa-portfolio-for-freshers

Use the blank Test cases, Bug reports and API checks sheets for your own project. The separate examples are fictional teaching material. Proposed test and API checks have not been executed. The fictional bug is not a real finding. CSV downloads contain blank entry rows and no dropdown formatting.

Record your application build, browser/API client and OS versions. Describe exact input, steps and expected behaviour before execution. Add actual results, run date and evidence only after execution. Status: Not run, Pass, Fail or Blocked. A blocked test needs a reason. Keep original evidence and record the fix build and retest separately. Severity describes impact; priority describes urgency and needs triage. Do not invent findings or present the examples as completed work.

Proposed local Task Tracker contract (implement locally or adapt to your API):
- Title is required after trimming; 1–100 characters. Use ASCII for this boundary exercise.
- POST /tasks accepts JSON with title. Valid input: 201 and JSON {id: non-empty string, title: trimmed title}.
- GET /tasks/:id: 200 and JSON {id, title} for an existing task; 404 and JSON {error: non-empty string} for an absent ID.
- GET /tasks: 200 and a JSON array of task objects.
- Invalid POST (empty, whitespace-only or 101 ASCII letters): 400 and JSON {error: non-empty string}. No task is saved. Compare the list count before and after.
- These are proposed local endpoints, not public TechRasta endpoints. Set up your local API before running. Save returned IDs; use an ID confirmed absent for the 404 check.

Suggested run: establish baseline list; create a uniquely named task; retrieve it; reject invalid inputs individually; check persistence; check absent ID; reset data and repeat. Publish setup and reset steps with a credential-free request collection. Use synthetic data. Never include secrets or real customer records in screenshots or exports.