You know what a test case is. You've read about boundary value analysis. Maybe you've even completed an ISTQB course.

But when someone asks, "Can you show me how you test software?", what do you actually show them?

If you're learning manual QA and don't have commercial experience yet, your portfolio doesn't need to be huge.

It needs to demonstrate how you think as a tester.

Here are three things I'd start with.

1. A Small Set of Well-Designed Test Cases

Don't start by writing 100 test cases.

Pick one feature, read its requirements, and identify meaningful scenarios.

For example, imagine an application with this requirement:

A quantity field accepts whole numbers from 1 to 10.

What would you test?

  • Minimum valid value: 1
  • Maximum valid value: 10
  • Below minimum: 0
  • Above maximum: 11
  • Decimal value: 1.5
  • Empty input
  • Non-numeric input

Now document each scenario with its expected result.

The goal isn't to create a long checklist. It's to demonstrate why you selected those test cases.

2. A Bug Report Someone Could Actually Reproduce

A screenshot with "It doesn't work" isn't a useful bug report.

For your portfolio, demonstrate how you would document a defect.

Here's a fictional example:

Title: Cart accepts a quantity below the permitted minimum

Precondition: The cart contains one product.

Steps to reproduce:

  1. Open the cart.
  2. Change the product quantity to 0.
  3. Confirm the change.

Expected result: The application rejects the invalid quantity according to the requirement.

Actual result (hypothetical): The cart accepts 0 and updates the total.

Evidence: Screenshot or short recording showing the input and result.

This is an illustrative example, not a defect found in a real application.

When testing a real project, only report issues you've actually reproduced.

3. A Short Test Execution Summary

This is something beginners often overlook.

After completing your tests, write a short summary:

  • What feature did you test?
  • What requirements did you use?
  • Which scenarios passed or failed?
  • Were any tests blocked?
  • What remains untested?
  • What would you recommend testing next?

You don't need a complicated enterprise test report.

A clear one-page summary can already demonstrate that you understand testing as a process, not just clicking buttons.

The Most Important Part: Show Your Reasoning

Your portfolio should answer three questions:

  1. What were you trying to verify?
  2. Why did you choose those tests?
  3. What did you discover?

Use a small demo application, an open-source project, or a purpose-built practice environment.

And be transparent: if the work was a personal learning exercise, label it that way. Don't present simulated defects as real discoveries or practice work as commercial experience.

Want Something to Practise On?

I created a free Boundary Value Analysis exercise for people learning manual software testing.

You can use it to practise choosing test data and thinking about expected behaviour.

👉 Try the free QA exercise

It's part of my broader project, QA Practice Kit, focused on hands-on software testing practice.

No purchase is required for the free exercise.

If you're already working in QA: what would you want to see in a junior tester's portfolio?