# SPOTHUB — Practise reviewing software behaviour
Understand the problem. Check the evidence. Explain your decision.

Fictional learning exercises. No real customer, payment or employer data.
You can complete this worksheet in a text editor. No signup required.
Reference: https://www.spothub.in/playwright-projects

## Exercise 1: Is the response correct?
Contract: GET order demo-42 returns HTTP 200, id demo-42, status pending, total 200.
Observed: HTTP 200, id demo-42, status confirmed, total 100.

Fill in:
| Check | Expected | Actual | Pass/fail |
|---|---|---|---|
| HTTP status | | | |
| Order ID | | | |
| Order status | | | |
| Total | | | |

Defect title:
Steps/data needed to reproduce:
Customer impact:
Two questions about the service contract:
What this response does NOT prove:

## Exercise 2: Review a browser test
Requirement: each notebook costs INR 100; no tax or delivery.
Action: set quantity to two.
Weak test: change quantity and finish, without checking the total.

Expected total:
Assertion you would add:
How you would deliberately make the assertion fail:
What a passing browser test does NOT prove:

## Exercise 3: Explain the failure
Fault-mode trace exercise: expected INR 100; received INR 200 after quantity two.
Requirement:
Observation:
Hypothesis:
Evidence supporting or rejecting the hypothesis:
Correction:
Rerun command and result:

## Reviewer notes — read after attempting
Exercise 1: HTTP status and ID match. Status and total do not.
An HTTP 200 does not establish correct business data, durable storage or authorisation.
Ask about unknown IDs and unauthorised requests before deciding expected responses.
Exercise 2: INR 200. An awaited locator assertion should check the displayed total.
Changing the expected value to INR 100 in your own copy should fail; restore it afterward.
Browser checks do not prove a database write or payment settlement.
Exercise 3: The supplied requirement supports INR 200. In this deliberate exercise, the test expectation is wrong.
Fix the expectation, not the timeout; record the rerun outcome.

## Keep as portfolio practice
Save your completed table, report and reasoning. Label it as a practice exercise.
Do not present it as client work or employment experience.
Official references:
https://playwright.dev/docs/test-assertions
https://playwright.dev/docs/api-testing
https://playwright.dev/docs/trace-viewer