What each check establishes
Model tests check validation and state transitions. Native interaction checks input, clicks and handlers. Screenshots help evaluate layout and appearance. Compilation does not establish working controls, and a screenshot does not establish a successful save.
Build a small regression set
Start with a success case, a failure case and recovery.
- Run CTest for SettingsState, including validation failure preserving the model.
- Type a name and click Save; inspect feedback and revision.
- Save blank input and check visible error with preserved state and count.
- Edit without saving and restore to the last successful values.
- Repeat key actions in wide/narrow windows and Chinese/English.
Wait for state through MCP
Inspect the DOM to find targets, perform actual input and clicks, then wait for expected text or attributes. Avoid fixed long delays as substitutes for assertions. Setting an attribute does not establish keyboard input support. Capture after state settles.
Record performance, layout and function separately
Record versions, viewport, scale, input method and observed limitations. Measure timing in dedicated performance scenarios and inspect layout changes visually. Preserve failure evidence instead of erasing it after a successful retry.
Something unclear?
Report an issue on this page →