Browser Testing
Create robust end-to-end browser tests with accessibility and visual checks.
Overview
Exercise the actual user journey in an explicitly approved test environment. Use stable accessible locators, isolated state, and observable assertions. Capture failures without exposing credentials or personal data.
Referenced source
Microsoft PlaywrightBrowser testing practicesDraft. Independent runtime review pending.
Reference linked; draft instructions are original.
0.1.0, pinned in this draft.
Explicit permissions and limits below.
Claude Code, Codex, Cursor
Use an approved local or test browser. No production writes or real purchases.
Capabilities
- Test a complete critical user journey
- Use accessible roles and labels for locators
- Keep test state isolated between scenarios
- Check keyboard navigation and visible focus
- Observe failed requests and browser console errors
- Capture responsive visual evidence
How it works
- Confirm the test URL and permitted actions.
- Identify stable user-visible landmarks and expected results.
- Run the happy path and a meaningful failure or empty state.
- Report evidence, failures, and untested environments.
This is an original Reporadars draft, informed by the linked source. Compatibility has not been independently runtime-tested; inspect the instructions, permissions, and placement for your agent before use.