Build a feature as a complete user action with clear inputs, state changes and feedback. Keep data operations testable outside the screen where practical.
Before you begin
Use a supported development setup and a small sample app. Record the toolchain, target and test device or simulator.
Work through the idea
Define a user task and the states the interface must represent. Test normal, empty and failed states as applicable, and consider larger text, narrow layouts and interrupted operations. Keep sample data fictional. Distinguish simulator checks from features that require validation on the intended physical device.
- Define acceptance criteria
- Implement a small vertical slice
- Test failure and empty states
Practice task
Add a fictional task-creation feature with a validated title and visible saved state.
Check your result
Test empty input, successful save and failed persistence without misleading confirmation.
A mistake to avoid
Do not show success before the underlying operation succeeds.
Keep a review note
Save the inputs or scenario, your reasoning and the result you checked. Explain one assumption and one case that needs more work. Revise the exercise after feedback and distinguish what you demonstrated from what remains untested.
Official reference for further study
Explore the related learning path · Choose another worksheet