# SPOTHUB: manual testing to automation
Fictional browser-only exercise. No real customer data, payment or stored order.
Open https://www.spothub.in/labs/checkout.html
Rule: INR 100 per notebook; whole quantity 1–5; nonblank customer name.
Reset before each case. Use a fictional name such as Demo Learner.

| Case | Name | Quantity | Expected after Submit | Actual | Result |
|---|---|---|---|---|---|
| Lower valid limit | Demo Learner | 1 | Confirmation INR 100 | | |
| Upper valid limit | Demo Learner | 5 | Confirmation INR 500 | | |
| Below limit | Demo Learner | 0 | Quantity error; no confirmation | | |
| Above limit | Demo Learner | 6 | Quantity error; no confirmation | | |
| Fraction | Demo Learner | 1.5 | Quantity error; no confirmation | | |
| Missing name | empty | 1 | Name error; no confirmation | | |
| Whitespace name | spaces only | 1 | Name error; no confirmation | | |

## Review your work
Did you reset each time? Did actual behaviour match the rule?
Do not mark an error display as a defect when rejection is the expected behaviour.
If a check fails, record repeatable steps and actual versus expected results.
If everything passes, record that honestly.

## Move one check into automation
Choose one repeatable case. Describe its starting state, locator, action and assertion.
Use https://www.spothub.in/playwright/labs/locators-and-assertions for the existing runnable example.
Explain what a passing assertion proves and what this browser-only demo cannot verify.
Keep manual exploration for new questions, not just repeating scripted steps.
This is portfolio practice, not employment experience or a guarantee of job readiness.