TASK · beginner · 2-3 hours
Write 30 test cases for a checkout flow
Write test cases that stop critical bugs reaching production
01
Why it matters
Test cases are the QA proof of work recruiters can judge fastest: clear, complete, structured.
02
Steps
- Pick the checkout flow of one app you use
- Write 10 happy paths, 10 negative cases, 10 edge cases (coupons, empty stock, failed network)
- Give each case an ID, priority, and expected result
- Execute 10 cases and log pass/fail
- Record 1 bug on Loom with written steps
03
Expected output
Sheet of 30 test cases plus 1 complete bug report
04
Checklist
- IDs and priorities filled
- Negative and edge cases present
- Specific expected results
- At least 1 documented bug
05
Evidence
Sheet link (view-only) plus bug video
06
Self review
Could someone else execute your tests without asking questions?
WORKED EXAMPLE · 6 OF 30 CASES
Copy this shape, fill 30 rows
Each row: ID, priority, explicit steps, specific expected result. Vague "it works" fails review.
| ID | PRIORITAS | LANGKAH | EXPECTED |
|---|---|---|---|
| TC-01 | Critical | Bayar sukses via transfer, nominal Rp150rb | Muncul order ID + struk, stok berkurang 1, email <1 mnt |
| TC-07 | High | Terapkan kupon valid HEMAT10 | Diskon 10% tampil sebelum bayar, total berkurang tepat |
| TC-14 | High | Bayar pakai kartu declined-test | Error "kartu ditolak (51)", order TIDAK terbentuk, stok utuh |
| TC-17 | Critical | Klik Bayar 2x cepat saat network lemot | Satu order saja, tidak double-charge |
| TC-23 | Medium | Stok habis TEPAT saat klik bayar | Error "stok habis", pembayaran dibatalkan otomatis |
| TC-28 | Medium | Kupon + promo digabung sekaligus | Aturan gabung tertulis; salah satu ditolak dengan jelas |
NEXT TASKS
TOOLS USED
TURN IT INTO PROOF
STUCK OR UNSURE?
bring your learning to a 1-on-1All materials are free to study. If positioning, portfolio, or apply strategy stalls, we dissect it together.