Verify State after Reload
verify_persistenceAfter any change, force a fresh page load to confirm whether text appears or disappears, verifying true server-side persistence.
Instructions
Force a fresh page load and report whether target_text is present
or absent — your tool for catching the "Saved!" toast that lied.
After any destructive or persistence-changing action (delete, edit, save, submit, toggle, payment, etc.), the success toast is not proof. Only a fresh GET on the relevant page is. This tool does that GET and reports presence — you decide whether the result matches what you expected.
Examples: verify_persistence("absent", "Buy groceries", "/tasks") — after deleting "Buy groceries", confirm it's gone from the list. verify_persistence("present", "EDITED-VALUE-XYZ", "/tasks/1/edit") — after editing, confirm the new value reloads.
Argus does not auto-record a bug here. If presence does not match your expectation, call record_bug.
Args: expect: "present" or "absent" — what state the target_text should be in after the fresh page load. target_text: The text or value you're checking for. after_url: Page to load and inspect. Defaults to the current URL. clear_storage: When True, wipe localStorage/sessionStorage before the reload so you test TRUE server persistence — a "Save" that only wrote client storage will read absent (data would be lost on another device/browser). Default False keeps client storage (proves server-backed truth without logging out). Use True when the feature is supposed to persist to a server/account. If clearing logs the app out, the result is unreliable — re-check without it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| expect | Yes | ||
| after_url | No | ||
| target_text | Yes | ||
| clear_storage | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |