test

Running behavioral tests simulates real user interactions across CLI, web, and API interfaces to catch bugs automated unit tests miss. The process analyzes code changes, builds test plans covering happy paths and edge cases, and uses local configurations without mocking. Playwright is required for web UI testing.

Behavioral testing catches bugs standard unit tests miss by simulating real human user interactions across CLI, web, and API interfaces. It builds comprehensive test plans including happy paths and edge cases from code changes, adhering to strict no-mocking policies using actual local configurations.

You need Playwright installed to execute behavioral tests against web UI interfaces. The testing approach requires Playwright specifically for browser automation, discovers existing local environment configurations automatically, and adheres to strict no-mocking policies during CLI, web, and API testing.

This testing method attempts to fix bugs discovered during the behavioral simulation across CLI, web, and API interfaces. After analyzing code changes and building test plans, it executes tests, attempts to fix identified issues automatically, and reports success or failure for each bug fix.

The testing process handles local environment configurations through automatic environment discovery, finding and using existing local credentials without mocking. It builds test plans from code changes, executes behavioral tests across interfaces, and attempts to fix issues found during the simulation.

The testing approach does not support mocking due to strict no-mocking policies. It validates API and web interfaces by discovering and using actual local environment configurations and credentials to simulate real human user interactions, ensuring behavioral tests reflect true application behavior.