Build · 7 min read
Browser and local preview
Open local or remote pages, keep browser profiles separate, and verify UI work with evidence.
On this page
Open the relevant page
Use the in-app browser for a local development URL or remote page. State the expected behavior and viewport or account state before testing.
Use an existing development server when available. Do not restart a shared server unless required because that can hide the state producing the bug.
Browser profiles
Profiles keep separate cookies, storage, permissions, downloads, and sessions. Use separate profiles for work and personal accounts or different test roles.
Confirm the active profile before submitting forms, publishing, purchasing, or changing remote data.
Verify visually and behaviorally
Compare visual changes at the affected size. For behavior, reproduce the failure, perform the corrected flow, and inspect visible errors or console and network evidence when available.
Record
- URL and viewport.
- Test role or profile without credentials.
- Expected and actual behavior.
- Screenshot or captured error.
Remote actions remain controlled
Reading differs from changing remote state. Purchases, publication, deletion, account changes, and other consequential actions require clear scope and can require approval even with Auto-approve.
Related articles