mcpField
A
api-testing

api-testing

github.com/oakossTesting & quality20137 installsUpdated 11w ago
Repository

About api-testing

A skill for testing HTTP APIs, aimed at developers validating endpoints and mocking external services. It covers Supertest integration tests and MSW network-level request interception, with patterns for response assertions, schema checks, and error cases.

Key features

  1. 01Supertest endpoint testing
  2. 02MSW HTTP and GraphQL mocking
  3. 03Status, header, and body assertions
  4. 04Response schema validation
  5. 05Cookie persistence and framework test clients

Use cases

  1. 01Testing REST API integration
  2. 02Validating request and response contracts
  3. 03Mocking third-party services in tests
  4. 04Checking error responses and edge cases

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/oakoss/agent-skills --skill api-testing

After installing, type/api-testingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
assertion-patterns.md
msw-handlers.md
supertest-patterns.md
test-organization.md

Details

From the project README

API Testing

Overview

API testing validates HTTP endpoints by sending requests and asserting responses, covering status codes, headers, body content, and error handling. Supertest provides a fluent chainable API for integration testing against Express, Fastify, and Hono apps without starting a real server. MSW (Mock Service Worker) v2 intercepts outgoing HTTP requests at the network level, enabling realistic mocking of external services in both Node.js tests and browser environments.

When to use: Integration tests for REST APIs, testing middleware pipelines, validating request/response contracts, mocking third-party APIs in tests, testing error handling and edge cases.

When NOT to use: Unit testing pure functions (use direct assertions), E2E browser testing (use Playwright/Cypress), load/performance testing (use k6/Artillery), testing static file serving.

Quick Reference

PatternAPIKey Points
GET requestrequest(app).get('/path')Returns supertest Test object
POST with bodyrequest(app).post('/path').send(body)Automatically sets Content-Type
Auth header.set('Authorization', 'Bearer token')Chain before .expect()
Status assertion.expect(200)Chainable with body assertions
Body assertion.expect({ key: 'value' })Deep equality check
Header assertion.expect('Content-Type', /json/)Accepts string or regex
MSW HTTP handlerhttp.get('/api/users', resolver)Intercepts matching requests
MSW GraphQL handlergraphql.query('GetUser', resolver)Intercepts by operation name
MSW responseHttpResponse.json(data, { status })v2 response format
MSW error simulationHttpResponse.error()Simulates network failure
MSW one-time handlerhttp.get(path, resolver, { once: true })Auto-removed after first match
MSW per-test overrideserver.use(handler)Override default handlers in specific tests
Schema validationschema.parse(response.body)Validates response structure with Zod
Cookie persistenceconst agent = request.agent(app)Maintains cookies across requests
Fastify injectapp.inject({ method, url })Built-in testing without supertest
Hono test clienttestClient(app)Type-safe request builder

Common Mistakes

MistakeCorrect Pattern
Not awaiting supertest requestsAlways await request(app).get('/path')
Sharing server state between testsReset handlers with server.resetHandlers() in afterEach
Mocking fetch/axios directlyUse MSW to intercept at the network level
Forgetting server.listen() in setupCall in beforeAll, resetHandlers in afterEach
Passing Fastify instance to supertestUse fastify.server (the underlying Node server)
Asserting before response completesUse await or return the supertest chain
Hardcoding test data across many testsUse factories or fixtures for test data
Not testing error responsesTest 4xx and 5xx paths alongside happy paths
Using server.close() in afterEachUse afterAll for close, afterEach for reset only
Ignoring response headers in assertionsValidate Content-Type, Cache-Control, CORS headers
Not using onUnhandledRequest: 'error'Catch unhandled requests to prevent silent test gaps
Testing implementation instead of behaviorAssert on response shape, not internal function calls

Delegation

  • Test structure review: Use Task agent
  • Code review: Delegate to code-reviewer agent
  • Pattern discovery: Use Explore agent

If the vitest-testing skill is available, delegate general Vitest configuration and patterns to it. Otherwise, recommend: npx skills add oakoss/agent-skills --skill vitest-testing

References

Comments

Markdown supported