Testing Apps Built with Windsurf
Short answer
Windsurf (Cascade) ships code quickly across your repo. TestChimp adds QA orchestration—markdown plans, Playwright SmartTests, /testchimp test on PRs, and TrueCoverage—so Cascade output stays verified in CI.
Who this is for
Teams using Windsurf Cascade for multi-file refactors who need E2E that tracks auth, checkout, and API changes across autonomous edits.
How teams ship with Windsurf
Multi-file edits, terminal commands, and flow-aware refactors from Cascade. Speed is high; regression risk rises with each autonomous edit to middleware and routes.
Common QA gaps
| Risk | What goes wrong |
|---|---|
| Happy-path-only tests | Generated in-session without probe Assert |
| Cross-file changes | Auth or checkout middleware updated without E2E refresh |
| Missing fixtures | Refactors break Arrange layer silently |
| No production feedback | TrueCoverage gaps invisible until incidents |
Why E2E with probes is non-negotiable
Cascade can rename routes and components faster than manual QA tracks. Probe-backed SmartTests catch backend regressions UI clicks hide—flaky E2E patterns.
The TestChimp loop on every PR
TestChimp does not replace your builder—it orchestrates QA on what agents ship:
| Phase | Command | Outcome |
|---|---|---|
| Bootstrap | /testchimp init | Seed/probe routes, fixtures, Playwright CI, TrueCoverage (init) |
| Per-PR QA | /testchimp test | Agents read markdown plans, author/repair SmartTests, wire // @Scenario: (test) |
| UX risk | /testchimp explore | ExploreChimp on SmartTest pathways (explore) |
| Post-deploy | /testchimp evolve | Close TrueCoverage and plan gaps (evolve) |
Install the TestChimp skill in your agent IDE. SmartTests remain Playwright in Git—standard traces, reporters, and CI (SmartTests).
Three realities TestChimp aligns
| Reality | Without orchestration | With TestChimp |
|---|---|---|
| Planned | Scenarios live in chat or Notion | Markdown plans in Git (test planning) |
| Tested | Session-scoped agent tests | CI SmartTests + test runs (test runs) |
| Production | Unknown coverage holes | TrueCoverage RUM ↔ runs (TrueCoverage) |
Mismatch signals drive the next /testchimp test cycle—not another ad hoc prompt.
Example scenario
Situation: Cascade refactors auth middleware; unit tests pass.
Expected outcome: Checkout session cookies remain valid; order completes.
Why UI-only automation breaks: Session cookies break silently; checkout fails only in E2E path.
- Arrange: Seed authenticated session via API after middleware change.
- Act: Playwright completes checkout with session cookie.
- Assert: Probe confirms order row and session still linked.
TestChimp workflow: ExploreChimp flags UX drop on checkout after auth refactor.
Same Arrange/Act/Assert pattern as expired-coupon checkout.
Worked example
Cascade refactors auth middleware; unit tests pass but session cookies break checkout. Per-PR SmartTests with probe session state fail in CI before merge.
Related
Cursor · Agent workflow · ExploreChimp
Frequently asked questions
Cascade already writes tests—why add TestChimp?
Cascade refactors quickly; tests authored in isolation often miss backend Arrange and probe Assert when auth or checkout middleware changes. TestChimp ties SmartTests to markdown scenarios and runs them in CI on every PR, with TrueCoverage highlighting journeys that regressed in production even when unit tests stayed green.
Does TestChimp replace Windsurf?
No—it orchestrates QA for what Windsurf builds—SmartTests, plans, and TrueCoverage on every PR.
We already use coding agents—do we still need TestChimp without QA?
Agents alone produce session-scoped tests. TestChimp orchestrates Windsurf with markdown plans, CI history, ExploreChimp, and TrueCoverage—`/testchimp test` on every PR so developers drive QA without a separate org.
Agent-written tests failed overnight—how does TestChimp recover?
Because SmartTests live in Git with scenario links, the next `/testchimp test` run sees CI history and TrueCoverage gaps, then opens a fix PR—not a fresh chat thread. Deterministic Arrange/Assert steps fail fast; hybrid AI steps absorb copy or layout churn without rerunning entire agent sessions.
Apply these patterns in your repo
Run `/testchimp init` to connect TestChimp to your repo, then `/testchimp test` on PRs to turn these patterns into maintained SmartTests. Use `/testchimp evolve` when you want to expand coverage as your app grows.