Start with a notification preference on a test site. Assume a prepared test account has notifications disabled. The task is to enable them, reload the page, verify the saved value, and restore the initial setting. Record the original state before changing anything.
Define two separate observations
After clicking Save, capture the interface response. Then reload and read the actual preference again. The first observation covers feedback and the second covers persistence. If the route redirects to authentication, record the blocker and stop the scenario.
Make the check repeatable
- Open settings and note the URL and current preference.
- Locate the switch and Save button by accessible name.
- Change the preference, save, wait for feedback, and reload.
- Restore the initial value and verify it after a second reload.
Record the first failing step
Include the environment, browser, original value, expected result, and observed result. A screenshot can show the interface at failure time. Record the value read after reload to establish whether the change persisted. If Save is disabled, inspect required inputs, permissions, and pending requests before diagnosing a regression.
Use the linked webapp-testing skill to structure a Playwright check once the test environment and data are available. Read its upstream instructions for runtime requirements. This scenario describes an acceptance check you can run against your own application.