edu-demo-evaluator-tests

Automate end-to-end testing for educational demos by running a local HTTP server to host problem assets and executing test_cases.json files against multiple agent simulations. The pipeline orchestrates Chrome E2E tooling in a single tab to execute steps and capture screenshots for each agent.

To run Chrome E2E test automation, you need a local HTTP server hosting your problem assets, a Chrome automation context, and a valid JSON test_case schema defined in your problems directory. These prerequisites allow the pipeline to execute agent simulations and generate results.

Multi-agent test simulation reporting works by playing back test_cases.json definitions across multiple agent configurations. It outputs agent-level results with PASS, PARTIAL, or FAIL statuses and accompanies each outcome with screenshots for quick visual review of bugs and blockers.

You can run multiple agent simulations in a single Chrome tab using this E2E testing approach. Single-tab orchestration minimizes resource usage while executing test steps, capturing screenshots, and generating per-agent PASS, PARTIAL, or FAIL results for your educational demos.

The best way to verify educational demos and identify bugs is to apply automated Chrome E2E testing against test_cases.json definitions. This approach executes deterministic test steps across multiple agent configurations and generates per-agent results with screenshots to quickly highlight blockers.

Educational demo test automation requires a local HTTP server because the E2E pipeline needs to host and serve problem assets locally. The Chrome automation context then accesses these assets to execute test_cases.json steps and generate per-agent results.