10 Playwright Portfolio Project Ideas That Impress Interviewers
Ten Playwright portfolio project ideas from beginner to advanced, with what each proves, a scoring rubric, a README template and the mistakes that hide your skills.

Quick answer: build three Playwright projects, not ten. One small UI suite that shows clean locators, one API test suite, and one larger project that mixes API and UI tests and runs in CI. Finish each one, add a clear README, and you will have more to talk about in interviews than most applicants.
Below are 10 ideas grouped by level. For each one you will see what it proves to a hiring manager, which Playwright features it uses, and how to make it stand out. Every idea uses public demo sites or practice APIs made for testing. Do not automate a real company's live site without permission.
What a reviewer looks for in a Playwright portfolio
Hiring managers usually spend a few minutes on a portfolio. In that time they check:
| Signal | Strong | Weak |
|---|---|---|
| Locators | getByRole, getByLabel, getByTestId | Long XPath or CSS chains |
| Waiting | Web-first assertions like toBeVisible() | waitForTimeout(5000) |
| Structure | Fixtures or page objects, tests read like sentences | One huge test file |
| Coverage | Happy path plus negative and edge cases | Only the happy path |
| Running | CI badge, HTML report, one command to run | “Works on my machine” |
| Explanation | README with scope, decisions and known gaps | No README |
The Playwright locators guide recommends user-facing locators first; following it is an easy way to look experienced.
Beginner Playwright project ideas (1 to 3)
1. Login page test suite
What it proves: you can turn rules into test cases, not just record clicks. Build: 10–15 tests on a public demo login page: valid login, wrong password, empty fields, locked user, logout, and session after refresh. Stand out: drive negative cases from one data table with a loop instead of copying tests. Our guide to login page test cases gives you the case list.
2. Form validation suite
What it proves: boundary value thinking. Build: tests for a sign-up or contact form with length limits, email format, required fields and error messages. Stand out: test exactly at each boundary (minimum, minimum minus one, maximum, maximum plus one) and name tests after the rule they check.
3. Search and filter tests
What it proves: you can assert on lists, not single elements. Build: search, sort by price, filter by category and empty results on a demo shop. Stand out: check that every result really matches the filter, and avoid strict mode errors with scoped locators (see how to fix strict mode violations).
Intermediate Playwright project ideas (4 to 7)
4. REST API test suite
What it proves: you test below the UI. Build: use Playwright's request fixture against the free QA Practice API: list with paging, create, read, delete, 401 with no token and 422 on bad input. Stand out: log in once in a worker fixture and reuse the token. Our Playwright API testing guide walks through a version we ran ourselves.
5. E-commerce checkout flow with page objects
What it proves: you can structure a growing suite. Build: add to cart, change quantity, apply a coupon, checkout on a demo shop, with one page object per page. Stand out: keep assertions in tests, not in page objects, and explain that choice in your README.
6. Saved login state and multiple roles
What it proves: you understand test speed and isolation. Build: log in once per role in a setup project, save storage state, and run admin and normal-user tests in parallel. Stand out: show the run time before and after in your README.
7. Network mocking project
What it proves: you can test error states the real server rarely returns. Build: use page.route() to return a 500, an empty list and a slow response, and check the UI shows the right message. Stand out: one short paragraph on when mocking is risky (it can hide real integration bugs).
Advanced Playwright project ideas (8 to 10)
8. Full framework with CI
What it proves: you can deliver something a team could adopt. Build: combine ideas 4–6 with environment config, custom fixtures, tags (smoke, regression), retries only in CI, HTML report, and a GitHub Actions workflow based on the official CI guide. Stand out: a green CI badge at the top of the README and a link to the latest report.
9. API plus UI hybrid tests
What it proves: you know how to make UI tests fast and stable. Build: create test data through the API, check it in the UI, then clean it up through the API. Stand out: explain why setting up data through the API removes flaky UI steps.
10. Accessibility and visual checks
What it proves: you think beyond functional testing. Build: add automated accessibility scans to key pages and a few screenshot comparisons with toHaveScreenshot(). Stand out: state clearly that automated scans catch only some accessibility issues and list what you checked by keyboard yourself.
Which projects should you pick?
| Your situation | Pick these | Why |
|---|---|---|
| Fresher, first automation job | 1, 4, 5 | Covers UI, API and structure without overreaching |
| Manual tester moving to automation | 2, 4, 9 | Shows your test design skill plus new technical skill |
| Selenium user switching to Playwright | 6, 7, 8 | Shows Playwright-specific features you would not use in Selenium |
| Aiming for SDET roles | 8, 9, 10 | Framework design, CI and wider quality thinking |
Worked example: turning idea 4 into a strong repo
Here is how one test in the API project might look. This snippet is illustrative and was not run as written; the working, tested version is in our Playwright API guide. Replace the placeholder base URL with your own practice workspace URL.
import { test, expect } from '@playwright/test';
test('rejects a product with no price (422)', async ({ request }) => {
const res = await request.post('products', {
headers: { Authorization: `Bearer ${process.env.API_TOKEN}` },
data: { name: 'Portfolio mug' }, // price deliberately missing
});
expect(res.status()).toBe(422);
expect(await res.text()).toContain('price');
});Notice three things a reviewer will like: the test name states the rule, the token comes from an environment variable instead of the code, and the comment explains the missing field. A suggested repo layout:
playwright-api-portfolio/
tests/
products.spec.ts
auth.spec.ts
fixtures/
auth.ts
playwright.config.ts
.env.example # names only, no real values
.github/workflows/tests.yml
README.mdREADME template for each project
- What this tests: one sentence and the app or API used.
- How to run: install and run commands.
- Test scope: a short table of features and the cases covered.
- Design decisions: why fixtures or page objects, why these locators.
- Known gaps: what you did not test and why. Honesty here reads as seniority.
- Report: CI badge and a screenshot of the HTML report.
How to talk about your project in an interview
“I built an API and UI suite in Playwright with TypeScript. I log in once per worker with a fixture, create test data through the API, and check it in the UI, which cut flaky steps. Tests run in GitHub Actions on every push. One thing I'd improve is test data cleanup when a run fails halfway.”
Likely follow-ups: Why getByRole over CSS? How do you handle flaky tests? Why did you choose fixtures over page objects? If an AI assistant helped you write code, say so and show you understand it.
Practice exercise
Take idea 3 (search and filter). Write down five test cases before writing any code, including at least two negative or edge cases.
Show sample answer
- Search for an existing product name shows it in results.
- Search with mixed case returns the same results.
- Search for a nonsense word shows the empty-results message.
- Filter by category: every result card belongs to that category.
- Sort by price low to high: each price is less than or equal to the next.
Next step
Pick your three ideas from the table above and start with the smallest one this week. If you want structured lessons with assessments, see the Playwright course. For portfolio tips beyond Playwright, read how to build a QA testing portfolio, and share your repo for feedback in the QA Community.
Key takeaways
- 1Three finished projects beat ten half-built ones.
- 2Use public demo sites or practice APIs built for testing, never a real company's production site.
- 3Show stable locators (getByRole, getByTestId), fixtures, API tests and CI, not only clicks.
- 4A README that explains what you tested and why is often read before your code.
- 5Be ready to explain every line in an interview, including code an AI assistant helped write.
Common mistakes to avoid
- Copying a tutorial repo and changing only the name.
- Using fixed waits (waitForTimeout) instead of Playwright's auto-waiting assertions.
- Committing passwords or tokens to a public repository.
- Testing a real company's live site without permission.
- No README, so reviewers cannot tell what the project proves.
References
- 1Playwright docs: Writing tests— playwright.dev
- 2Playwright docs: Locators— playwright.dev
- 3Playwright docs: API testing— playwright.dev
- 4Playwright docs: Continuous Integration— playwright.dev
