Career Guide

7 QA Portfolio Projects That Get You Interview Calls

Seven portfolio projects for testers, from a manual test pack to a CI-driven automation suite, with what to build, how to present it and what recruiters look for.

✍️ By QA Jobs India📅 17 Nov 2026⏱ 7 min read

Recruiters and hiring managers see hundreds of resumes that list “Selenium, Postman, JIRA, SQL”. Very few of those resumes include a link that proves it. A small, well-presented set of QA portfolio projects changes that: instead of claiming skills, you show them, and the interviewer’s questions shift from “Have you used this?” to “Tell me about this decision you made.”

This guide describes seven projects that cover the skills most Indian QA job descriptions ask for. You do not need all seven. Freshers should aim for three, and experienced testers moving toward automation or SDET roles should aim for four or five. For each, you will find what to build, what to include and how to present it.

Key takeaways

  • A portfolio is evidence. Two or three well-documented projects beat ten half-finished ones.
  • Mix project types: at least one manual or exploratory project, one API project and one automation project.
  • Every project needs a README that explains what you tested, how to run it and what you found.
  • Run automation in CI so reviewers see a green badge and a report, not just code.
  • Mention portfolio links at the top of your resume and in your LinkedIn Featured section.

What makes QA portfolio projects stand out

Hiring managers usually spend only a few minutes on a candidate’s repository. In that time, they look for:

  • A clear README: purpose, scope, how to run, and results.
  • Real thinking: test design choices, risks considered, bugs found.
  • Clean structure: sensible folders and naming, no commented-out code everywhere.
  • Working execution: a CI run, a report or screenshots that prove it actually runs.
  • Honesty: known limitations and next steps listed openly.

A good README template:

# Job Portal Search - Test Automation

## What this project tests
Search, filters and job detail pages of a public demo job portal.

## Tech stack
Java 17, Selenium 4, TestNG 7, Maven, GitHub Actions

## How to run
mvn test

## Test design
- 24 UI tests covering positive, negative and boundary cases
- Page Object Model with explicit waits

## Bugs found
See BUGS.md for 6 documented defects with screenshots.

## Next steps
Add API tests for the search endpoint and run in parallel.

Project 1: Manual test pack for a real application

What to build: Pick one feature of a public web app, such as hotel search on a travel site or product filters on an e-commerce site. Write a test plan summary, 40 to 60 test cases and a short test summary report.

What to include:

  • Scope and out-of-scope items.
  • Test cases with IDs, preconditions, steps, test data and expected results.
  • Techniques used: boundary values for price filters, equivalence classes for date ranges.
  • A summary of what passed, what failed and the main risks.

Why it works: It shows you can think systematically, which is what manual testing interviews actually test. It is also the best first project for freshers trying to land a QA job without experience.

Project 2: Bug report collection from exploratory testing

What to build: Spend several time-boxed exploratory sessions on two or three public apps and document real defects.

What to include:

  • Session notes with a charter, such as “Explore checkout with invalid coupon codes for 45 minutes.”
  • Eight to twelve bug reports with clear titles, steps, expected and actual results, environment and screenshots.
  • Severity and priority with a one-line justification.

Only report genuine observed behaviour and keep the tone neutral. Our guide on how to write a bug report shows the level of detail recruiters expect.

Project 3: API test collection with Postman

What to build: A Postman collection against a free public practice API, with environments and tests.

What to include:

  • CRUD requests with variables and environments.
  • Tests for status codes, response time limits, response fields and error cases.
  • Chained requests that pass an id from one response to the next request.
  • A Newman command or CI run to execute the collection from the command line.

A simple Postman test script:

pm.test('status is 200', () => {
  pm.response.to.have.status(200);
});

pm.test('response has an id', () => {
  const body = pm.response.json();
  pm.expect(body).to.have.property('id');
  pm.environment.set('userId', body.id);
});

If you are new to Postman, start with our Postman API testing tutorial.

Project 4: UI automation framework

What to build: A small but properly structured automation suite against a practice website.

What to include:

  • Page Object Model, a base page with explicit waits and a config file for URLs and browser.
  • Fifteen to thirty tests across login, search and a form, with positive and negative cases.
  • Data-driven tests from a CSV or JSON file.
  • Reports and screenshots on failure.

Choose one stack and do it well: Selenium with Java and TestNG, or Playwright with TypeScript. Our Page Object Model in Selenium guide gives you a ready structure to start from.

Project 5: CI pipeline that runs your tests

What to build: Add GitHub Actions to Project 3 or 4 so tests run on every push and on a schedule.

A workflow for a Playwright project:

name: ui-tests
on:
  push:
  schedule:
    - cron: '30 2 * * *'
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - run: npx playwright install --with-deps
      - run: npx playwright test
      - uses: actions/upload-artifact@v4
        if: always()
        with:
          name: playwright-report
          path: playwright-report

Add the workflow status badge to your README. A visible, passing pipeline tells a reviewer in one glance that your project actually runs. The GitHub Actions documentation explains badges and scheduled runs.

Project 6: Performance test of a public demo API

What to build: A JMeter or k6 script that load-tests a practice API you are permitted to test, with a short report.

What to include:

  • A realistic scenario: think time, ramp-up and a mix of requests.
  • Thresholds such as an acceptable response-time percentile and error rate.
  • A one-page report with results, charts and your interpretation.

Never load-test a website you do not own or have explicit permission to test. Use demo APIs that are published for practice, or run a sample app locally in Docker. Our JMeter tutorial for beginners covers the basics.

Project 7: Accessibility audit of a website

What to build: A short accessibility review of a public website using free tools and manual checks.

What to include:

  • Keyboard-only navigation checks, focus order and visible focus.
  • Colour contrast, form labels, alt text and heading structure.
  • Results from a browser extension or Lighthouse accessibility audit.
  • Findings mapped to WCAG success criteria, with severity and suggested fixes.

Accessibility skills are less common among testers, so this project often starts conversations in interviews.

Which projects to choose for your level

Your situationRecommended projects
Fresher, manual focus1, 2, 3
Fresher, automation focus1, 3, 4, 5
Manual tester moving to automation3, 4, 5
Automation tester aiming for SDET4, 5, 6 plus a small tool of your own
Interested in specialisingAdd 6 for performance or 7 for accessibility

Mistakes that make a portfolio backfire

A weak portfolio can hurt more than having none, because it invites questions you cannot answer well. Watch out for these:

  • Copied frameworks. Cloning a popular template and changing the URL is easy to spot. Interviewers ask why you structured something a certain way, and “the tutorial did it” is not a good answer.
  • Broken builds. A red CI badge or a README command that fails tells a reviewer the project is abandoned. Fix it or remove the badge.
  • Secrets in the repository. Passwords, tokens or API keys committed to GitHub are a serious red flag for any testing role. Use environment variables and keep example config files without real values.
  • No results. Code without reports, screenshots or a bug list leaves the reviewer guessing what you actually found.
  • Too many unfinished repositories. Archive or make private anything you would not want discussed in an interview.

Before you share the link, ask a friend to clone your repository on a fresh machine and run it using only your README. Every question they ask is a gap in your documentation.

How to present your portfolio

  • Resume: Add a “Projects” section near the top with one line per project and a link.
  • LinkedIn: Add projects to Featured and write a short post when you finish each one.
  • Naukri: Mention project skills in your profile summary and key skills.
  • Interviews: Prepare a two-minute walkthrough for each project: goal, approach, a key decision, one bug or problem you hit and what you would improve.

Keep repositories tidy: meaningful commit messages, no secrets or API keys, and a .gitignore for build output and reports.

🚀 Ready to put your portfolio to work?

QA Jobs India shares 100+ fresh QA & software testing openings every morning — manual, automation, API and remote roles.

See today’s QA jobs →

FAQs

Do recruiters really look at QA portfolio projects?

Many do, especially for automation and SDET roles, and interviewers often open links during technical rounds. Even when they do not, a portfolio gives you concrete examples to discuss, which improves your answers.

How many projects should a fresher have?

Two or three solid projects are enough. A good combination is a manual test pack, an API collection and a small automation project.

Can I use public websites for portfolio projects?

You can test publicly available features as a normal user, as long as you follow the site’s terms. Use practice sites and demo APIs for automation and load testing, and never run load tests or security scans against sites without permission.

Should my portfolio be on GitHub?

GitHub is the most common place because it shows code, history and CI runs. Manual testing artefacts can also live there as Markdown, spreadsheets or PDFs.

Do portfolio projects count as experience?

They are not the same as paid work experience, but they are valid evidence of skills. List them under a separate “Projects” section and describe them honestly.

Conclusion

Choose the first project from the table for your level and give yourself two weekends to finish it, README included. Publish it, add the link to your resume, and start the next project only after the first is complete and polished.

SIGN UP ONCE
Once you sign up, you get all this
Sign up now
  • 100+ fresh QA jobs daily + Direct HR email IDsLive every morning at 9 AM — apply straight to HR
  • Weekly Mega Job Fair800+ QA jobs from India & around the world, every week
  • Certified QA coursesUp to 3 courses included · all 17 for ₹500
  • AI ATS Resume BuilderFree resume points included
  • Full LinkedQA feedEvery post, fully unblurred
  • Complete QA Material libraryInterview Q&A, cheat sheets, templates & roadmaps

Instant activation right after payment · One login for jobs, courses, resume & LinkedQA

💎 Get every QA opening, every day

Join QA Jobs India Premium for 100+ verified QA jobs daily with HR contact details.

✓ You're subscribed — job alerts arrive daily at 9 AM
Scroll to Top