Test @rangojs/router apps across unit, integration, RSC Flight, and Playwright e2e layers.
npx skills add https://github.com/rangojs/rango --skill testing-rangojs
Please help me install this Agent Skill. Skill: testing Source: https://github.com/rangojs/rango/tree/main/packages/rangojs-router/skills/testing Command: npx skills add https://github.com/rangojs/rango --skill testing-rangojs
runLoader/runMiddleware/runInRequestContext for node unit tests, renderRoute for DOM client components, renderServerTree/renderToFlightString/renderHandler for real Flight renders, and dispatch for response routes. - Dev/prod and progressive-enhancement e2e parity: parityDescribe generates both dev and production describes from one body, and expectParity asserts JS and no-JS flows produce identical observable results. - Cache, SWR, and prerender assertions: assertCacheStatus reads the X-Rango-Cache header while createCacheSink/assertCacheDecision capture telemetry events with zero production surface. - Use Case: You need to test a loader that reads env.DB, sets a cookie, and throws a redirect. Use runLoaderResult with a D1 double injected via the env option, then assert the thrown redirect's Location header and the Set-Cookie output. ## Quick Start Ask the assistant to write a unit test for a loader or middleware in your @rangojs/router app, or to set up a dev-and-production e2e test for a route using parityDescribe.High-intent search queries and answers about installing and using this skill.
Use runLoader from @rangojs/router/testing to execute a loader against a real RequestContext in plain node. Seed params, env, vars, and search data via options; use runLoaderResult instead when you need to assert cookies, headers, redirects, or handle writes.
Use renderServerTree or renderToFlightString from @rangojs/router/testing/flight under the react-server vitest project. A real async Server Component cannot run in a plain node test — it requires the react-server condition, the index.rsc.ts alias, and files named *.rsc-test.ts run via the RSC test project.
No, rango ships no doubles for platform bindings by design. You build your own double matching the driver contract (e.g. drizzle-orm/d1 needs positional row arrays from .raw() and { success, meta } from .run()) and inject it through the env option every testing primitive accepts.
Use parityDescribe from @rangojs/router/testing/e2e, which registers a dev describe and a production describe from a single test body. This structurally enforces the rule that every e2e covers both modes, since a dev-only e2e is not acceptable.
The Flight serializer only loads under the react-server node condition, so importing @rangojs/router/testing/flight elsewhere throws. Configure a separate vitest project with resolve.conditions including react-server, the @rangojs/router to index.rsc.ts alias, and NODE_ENV=production.
Use renderRoute from @rangojs/router/testing/dom for client components reading router context like useParams or useReverse, where loader data is seeded rather than executed. Navigation lifecycle states, hydration, Flight serialization, and progressive-enhancement parity require a Playwright e2e test.
yonderlabConfigure React Router 7 framework-mode routing with type-safe loaders and actions.
thermiteauRun lint, typecheck, and tests locally before pushing and monitor GitHub Actions results.
AgentiveCityAutomate wrangler.toml configuration for Hono/TypeScript apps on Cloudflare Workers.
david-nossebroRun black-box manual QA on web apps via Playwright CLI and return findings-only reports.