Software QA & Testing · 75–120 min

Find a risk, report it, protect the fix

Experience the reasoning behind QA: choose risks, gather reproducible evidence and automate a useful regression check.

01 · Setup

What you need

A tiny local app you own, such as a notes list, with source access. For automation, basic JavaScript and Playwright installed; setup time is separate. No third-party testing.

You may stop when the timebox ends. An incomplete result is still useful evidence.

02 · Task

01
Write three acceptance criteria for saving a note. Name the most harmful failure, such as silently losing text.
02
Spend 15 minutes exploring empty input, long text, repeated save and reload. Record conditions and actual behavior, not just pass/fail.
03
If you find a defect, report steps, expected/actual results and impact. If not, report the coverage and remaining uncertainty honestly—do not invent a bug.
04
Write one automated save-and-reload check from the acceptance criterion. Temporarily introduce a local defect to confirm the check fails for the right reason.
05
Restore or fix the app, rerun the check and explain what it still cannot test. Have a peer reproduce your report.

03 · Pay attention

Did choosing what to test require more thought than writing the click steps?
Can you describe release risk without blaming a developer or promising zero bugs?

Plot twist

Difficulty does not mean the career is a bad fit. The useful question is whether curiosity returned after the difficulty.

04 · Reflect

Would you voluntarily spend another five hours on this kind of problem? Why?

Which part gave you energy, and which part drained it?

What evidence—not a salary video—would you gather before choosing this path?

This site does not save your answers. Put them in your own notebook if useful.

05 · Where to go next