Software Testing
Build proof of your skillsPremium · free during launch5 min readPublished November 12, 2026

How to build a QA portfolio with no experience

Without a job in testing, your portfolio is your experience. Here's exactly what to include: a test plan, test cases, bug reports, an exploratory session, API tests and a small automation project, where to practise legally, and how to present it.

On this page

Key takeaways

  • A portfolio turns "I've learned about testing" into "here's testing I've done". It's often what moves a career changer from the CV pile to an interview.
  • Include six pieces: a short test plan, test cases, 5–10 strong bug reports, exploratory session notes, a Postman collection and a small Playwright project, all for the same product so they tell one story.
  • Practise only where you're allowed: demo sites built for testing, your own projects, crowdtesting platforms, or apps you use, without attacking them. Then present it all from one link.

Why a portfolio matters

A hiring manager reading a junior CV has one question: can this person do the job? Courses and certificates say you studied. A portfolio shows how you think, how you write and how you use tools.

It also gives you material for interviews. "Tell me about a bug you found" is far easier when you can open it and walk through it.

The six pieces

Pick one product for most of your portfolio, such as a public demo shop or an app you know well, so the pieces connect.

1. A one-page test plan

Scope (what you'll test and what you won't), approach, environments and browsers, risks, and entry/exit criteria. Keep it to a page. See test case, test plan and test strategy.

2. Test cases for one feature

15–25 test cases for a feature like login, search or checkout, showing equivalence partitions, boundary values and negative cases. Mark which ones you'd automate and why.

3. Five to ten bug reports

Your strongest pieces. Each with a clear title, steps, expected vs actual, environment, severity and evidence (screenshot, video, the failing request from DevTools). See how to write a great bug report. Quality beats quantity: five excellent reports beat thirty sloppy ones.

4. An exploratory testing session

A charter ("Explore the cart with discount codes to find calculation errors"), a 60-minute time box, notes of what you tried, what you found and what you'd test next. It shows how you think. See exploratory testing.

5. A Postman collection

10–15 API requests with tests: happy paths, not-found, validation errors. Export it to GitHub with a README. See your first API test with Postman.

6. A small Playwright project

5–10 UI tests on GitHub, with a README explaining what's covered and how to run them. Bonus: run them in GitHub Actions so there's a green badge. See your first automated test.

Where to practise

KindExamplesGood for
Demo sites built for testingSauce Demo (saucedemo.com), The Internet (the-internet.herokuapp.com), DemoQA, Automation ExerciseTest cases, automation, bug hunting on purpose-built flaws
Practice APIsJSONPlaceholder, Restful Booker, ReqResPostman collections, API tests
Open-source projectsProjects on GitHub that welcome bug reportsReal bugs, real developers, public history
Crowdtesting platformsuTest, Testlio, Test IO and similarReal products, sometimes paid per valid bug
Apps you use every dayYour bank, shop, public transport appExploratory testing and bug reports, using the app normally

How to present it

  1. One link on your CV and LinkedIn: a GitHub profile with a pinned "QA portfolio" repository, or a simple page (Notion, Google Sites) that links to everything.
  2. A README that says, in three lines: what product you tested, what's in the portfolio, and what you'd show first.
  3. Documents as PDFs or Markdown, readable without downloading special tools.
  4. Clean commit history and clear names: login.spec.ts, not test1-final-FINAL.ts.
  5. Write in English if you're applying to companies that work in English, which most do.
Real-world exampleOne afternoon, one interview

Mihai (an illustrative example) was applying for junior QA roles with a CV listing two online courses. After 30 applications, he had no replies.

He spent three weekends on a portfolio around one demo shop: a one-page test plan, 20 test cases for checkout, 7 bug reports with videos, an exploratory session on discount codes, a Postman collection, and six Playwright tests running in GitHub Actions. He pinned it on GitHub and added the link to the top of his CV.

The next interview invitation came within two weeks. The interviewer had opened the repository before the call, and spent half the interview asking about his bug reports and why he had chosen those six tests to automate.

Lesson: a portfolio gives interviewers something concrete to talk about, and it's something you control.

Do

Show a small, coherent body of work around one product, with clear READMEs, and be ready to explain every decision in it.

Don't

Upload a course's example project unchanged, or 50 generated test cases you can't explain. Interviewers ask "why", and copied work can't answer.

Check yourself

You find what looks like a security problem on a real company's website while practising: by changing an ID in the URL, you can see another customer's order. What should you do with it?

Show answer

Stop testing it, don't access more data, and don't put it in your public portfolio. Report it privately to the company, through its security contact or responsible disclosure page if it has one, with minimal details needed to reproduce it. In your portfolio you can describe, later and only with permission, that you found and responsibly reported an access-control issue, without the details.