browser-test

To automate E2E browser tests from code changes, you generate and maintain YAML browser test prompts tied to frontend pages, routes, and API resolvers. This automatically validates new UI and API updates without requiring manual test writing.

Managing YAML browser test prompts for modern web apps is best handled by storing tests under a dedicated directory like tests/browser/. This approach integrates with code-change pipelines to automatically create, update, and execute tests for user-facing features.

Yes, browser-use supports dry-run workflows for YAML browser tests alongside create and list workflows. It parses and executes tests safely by enforcing non-blocking operations, environment checks, and clear validation before running.

You can generate browser tests automatically when API resolvers or frontend routes change by triggering a workflow that detects code changes. This auto-generates and updates YAML browser test prompts to validate the modified user-facing features.

Yes, you need browser-use to parse and execute the YAML browser test prompts. The automation requires browser-use to run the tests via its CLI, ensuring safe, non-blocking operation with proper environment checks and validation.

You should not use automated YAML browser tests if your environment fails the required safety checks, as the tool enforces non-blocking, safe operation with strict validation. It is specifically designed for modern web apps and may not suit non-browser contexts.