Verify before you commit
Use this page to sanity-check Supertest V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 27, 2026
Freshness
Updated 2026-03-27T05:48:07.867+00:00
Mar 27, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 8.5 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 8.2 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 8.3 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
The API is fluent: request(app).get('/api/users').expect(200).expect('Content-Type', /json/).expect({ users: [] }). Works with Express, Fastify, Koa, and any HTTP-compatible server handler. Async/await friendly with .then().
Supertest is a local testing library with no platform auth. Test requests go directly to the in-process app; no network involvement. Application-level auth can be tested by including tokens in request headers.
Supertest is the standard library for testing Node.js HTTP servers in integration tests. Rather than starting a real server and making network requests, Supertest passes requests directly to the app handler -- making tests fast, isolated, and port-free. Confidence is docs-derived.
Operationally, Supertest tests run fast because they avoid network overhead. The in-process model enables testing against an app instance with test database connections injected. Cleanup is the responsibility of the test setup/teardown.
Documentation is GitHub-README-level but sufficient given the simple API. The community has extensive examples. Developer experience is good; the fluent assertion chain is readable and well-understood across the Node.js testing community.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
8.3 / 10.0
No alternatives captured yet.