Browser submission workflow
Prepare a form, review external writes, and verify what the target accepted.
Use a test account and a staging destination with disposable records. Start with a browser route that supports the required actions and the intended session. Public-page navigation can use a different provider from a logged-in upload or submission. Check each capability and its authorization.
| Step | What to verify |
|---|---|
| Navigate and observe | The expected domain, page, session, and stable target descriptors. |
| Fill or upload | The exact fields and files. Place approval before any step that autosaves or transmits data, including an upload. |
| Review and submit | Confirm the proposed content, account, and destination. Configure a distinctive success message or URL to check after submission. The capability may require its own approval. |
| Collect evidence | Inspect the verified submit receipt and target record. Capture a screenshot with sensitive information excluded where possible. |
If a native file picker needs a handoff, complete it only in the intended test session and verify the attachment before proceeding. If a submit outcome is uncertain, locate the target record before resuming or retrying. For evidence from a desktop app, check its separate runtime route and permission.
Start with the browser submission example. See browser capabilities and runs and approvals.