SPOTHUB / PLAYWRIGHT LEARNING LIBRARY

Playwright project ideas with clear acceptance criteria

These illustrative briefs help you plan practice work. Use an application you own or are authorised to test, with synthetic users and no real payments.

Free learning resource · Official references below

Run a practical lab

01

Project 1: checkout confidence

Scope: one item, quantity changes and required customer fields. Define expected totals before running checks. Cover successful confirmation and rejected incomplete input; explain what payment behaviour is outside the project.

02

Project 2: order-service contract

Scope: create and retrieve a synthetic order in a controlled service. Define expected status and required response fields with the service contract. Keep setup and cleanup explicit so repeated runs do not pollute shared data.

03

Project 3: investigate a failure

Scope: introduce a deliberate change in your own sample application that breaks one expected result. Capture the failed run and identify whether the requirement, implementation or check needs to change.

04

Prepare a portfolio walkthrough

Describe the user risk, your contribution, how to reproduce the work and what remains untested. Separate your own reasoning from generated code or mentor suggestions. A small reproducible project is easier to evaluate than unexplained screenshots.

API review lab: a 200 response is not the whole result

Fictional contract: a GET request for order demo-42 must return that order ID, status pending and total 200. Sample response: HTTP 200 with body { id: 'demo-42', status: 'confirmed', total: 100 }.

Compare your reasoning with the review checklist
  • The HTTP status matches the sample contract, and the returned ID is correct.
  • The status and total violate the contract: expected pending and 200, observed confirmed and 100.
  • For a real test, assert the agreed HTTP status and parsed response fields. A successful status alone does not validate business data.
  • A GET response does not independently prove durable storage, payment processing or authorisation. Those require separate evidence and agreed scenarios.
  • Ask what an unknown order and an unauthorised caller should receive before writing negative tests. Do not invent the service contract.

Work to keep: Submit a field-by-field expected/actual table, a concise defect report and two unanswered contract questions.

Download the free review worksheet (.md text file)

Compare with the checkout review exercise →

Official Playwright reference · Illustrative SPOTHUB exercise; not a student or client result.

Official references

Use these sources for current API behaviour and setup requirements. SPOTHUB is an independent training provider.

Continue learning

Find My IT Career Path