e2e-testinglisted

# E2E Testing with @matware/e2e-runner ## Overview `@matware/e2e-runner` is a JSON-driven E2E test runner. Tests are defined as JSON files with sequential browser actions — no JavaScript test code. Tests run in parallel against a Chrome pool (browserless/chrome via Docker) using Puppeteer. **Key capabilities:** 13 MCP tools for running tests, creating test files, capturing screenshots, analyzing network traffic, verifying GitHub/GitLab issues, and querying a learning system for stability insights. ## Prerequisites Before running any tests, verify the Chrome pool is available: ``` e2e_pool_status → check "Available: yes" and session capacity ``` If the pool is not running, the user must start it via CLI (not available via MCP): ```bash npx e2e-runner pool start ``` ## Core Workflow The standard test execution flow: 1. **Check pool** → `e2e_pool_status` — confirm Chrome pool is ready 2. **List suites** → `e2e_list` — discover available test files and modules 3. **Run tests** → `e2e_run` — execute with `all`, `suite`, or `file` parameter 4. **Interpret results** — check `summary`, `failures`, `narratives`, `networkSummary` 5. **View screenshots** → `e2e_screenshot` — retrieve error/verification screenshots by `ss:HASH` 6. **Drill into network** → `e2e_network_logs` — use `runDbId` to inspect requests/responses 7. **Check learnings** → `e2e_learnings` — query stability trends, flaky tests, error patterns ### Interpreting Run Results The `e2e_run` response includes: -