The card below is the “product under test”. Use guided mode to see the bug list upfront, or blind mode to find them yourself first.
Techniques: State transition testing, Use case testing
Membership application
1. Personal
3. Payment
2. Confirm
Step 2 of 4
Your findings
0 / 0 bugs foundTick each bug as you confirm it on the page above. Progress saves automatically.
Write down every bug you find. Be specific — where it is, what’s wrong, what it should be.
Planted bugs (6)
- The progress bar steps are out of order: 1, 3, 2. The correct order should be 1. Personal → 2. Payment → 3. Confirm.
- The text says 'Step 2 of 4' but the progress bar shows only 3 steps. Either the step count or the indicator is wrong.
- The card number input has
value="4111 1111 1111 1111"— a test card number left in a production form. - CVV fields should use
type="password"orautocomplete="off"to prevent the value from being visible or saved by the browser. - Both step 1 (Personal) and step 2 (Payment/current) use the same dark blue background — no visual distinction between completed and current steps.
- Multi-step forms should warn users if clicking Back will lose unsaved data. No such indication exists here.
Multi-step form bugs: check step order, current step highlighting, step count consistency, pre-filled values, and security of sensitive fields.
Level complete
Ready for advanced testing?
The senior level covers accessibility, responsive layouts, async states, and cross-browser quirks.
Start the senior bootcamp →