//Practice
Practice that becomes portfolio.
Three ways to build real QA evidence: test a live app, work a briefed assignment, or study a production framework. Pick a section — each is its own hub.
★ New to QA? Start here
From zero to a portfolio piece in 3 steps
One guided sequence that crosses all three sections.
Step 1 · Assignment
Login Flow — Test Case Writing
Write a comprehensive manual test suite for a login page: functional cases, negative paths, security checks, and accessibility considerations, to interview-grade standards.
Step 2 · Practice app
Buggy Web App
Find, report and retest realistic bugs in a deliberately buggy task-management app — sharpen exploratory testing, bug reporting and regression skills.
Step 3 · Project sample
Playwright + TypeScript E2E Automation
A complete end-to-end automation project using Playwright and TypeScript, covering Page Object Model, API setup, fixture factories, and GitHub Actions CI.
// Three ways to practise
Choose a section
Each opens its own hub with paths, missions and the full catalog.
// Or jump by topic
Browse by area
Topic routes that pull the relevant apps, assignments and samples together.
// Every item ends with evidence
What you'll walk away with
// Using these for your portfolio
✓ Do
- Fork and extend with your own test cases and page objects
- Write a README explaining what you changed and why
- Link to your fork from your CV or LinkedIn profile
- Use assignment rubrics as self-assessment checklists
- Adapt the structure to a different app (e.g. swap the demo site)
✗ Don't
- Submit unmodified samples as your own original work in a hiring exercise
- Claim framework architecture choices you haven't thought through
- Present a stub ("coming soon") page as a completed deliverable
- Copy assignment solutions verbatim if using them as interview prep