e2e-testdino

What to do after a run of e2e, the agentic test runner from e2e.com (`e2e.config.ts`, `*.e2e.ts` files, `agent.act` steps), leaves the machine it ran on. Not for Playwright runs. Use when an e2e test failed in CI and its trace page is not in the local `.e2e/` folder, when deciding from run history whether an e2e test is flaky or broken, when quarantining a failing e2e test or checking that a fix held, when sharded e2e jobs need to show as one run, when agent steps cost more than expected or stop

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-analysis-optimization 456,474 ★
  Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserv
• rea-ci-tests-audit 456,474 ★
  Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for s
• diagnosing-bugs 323,337 ★
  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or r
• migrate-to-shoehorn 323,337 ★
  Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, w
• webapp-testing 194,218 ★
  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend