Setting the file. One moment.
Subchapter 15.5
references/exploratory-testing.mdMarkdown3 KBView on GitHub
Exploratory testing is agent-driven: you navigate the app freely using browse commands, making decisions about what to click, what to try, and what looks wrong — like a human QA tester.
Unlike test suite execution (structured tests against specific routes), exploratory testing is open-ended. The agent uses browse snapshot to understand the page, makes a judgment call on what to do next, acts, and observes the result.
1. browse open "TARGET_URL"
2. browse snapshot → understand what's on the page
3. browse screenshot → see what it looks like (Read the screenshot)
4. Decide: what looks wrong? What should I try?
5. browse click/fill/press → interact
6. browse snapshot → observe result
7. Repeat 4-6, navigating through the app freelybrowse eval "JSON.stringify(window.__logs || [])")<script>alert('xss')</script>, "quotes", emoji 🎉For each finding:
FINDING: [brief description]
SEVERITY: critical / high / medium / low
ROUTE: /path/where/found
EVIDENCE: [screenshot path or snapshot excerpt]
RECOMMENDATION: [specific fix suggestion]Example:
FINDING: Settings page — "Regenerate API Key" button has no confirmation dialog
SEVERITY: high
ROUTE: /orgs/:slug/:projectId/settings/general
EVIDENCE: Clicked "Regenerate" and the key changed immediately with no warning
RECOMMENDATION: Add a confirmation dialog: "This will invalidate your existing key. Are you sure?"