Name: tessl-labs/api-testing-first-steps
Rating: 94 (1 reviews)
Author: tessl-labs

Blog Docs Log in Get started

tessl-labs/api-testing-first-steps

Get test coverage on an Express/Node API fast — the first 5 tests that catch

1.26x

Quality

90%

Does it follow best practices?

Impact

100%

1.26x

Average score across 5 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

10%

Expand Test Coverage for Order Status and Filtering

PATCH routes and query parameter testing

Criteria

Without context

With context

PATCH creates resource first

100%

PATCH verifies updated value

100%

PATCH rejects invalid status

100%

query filter test exists

100%

query filter verifies all results

50%

100%

supertest used

100%

45%

Audit Error Response Consistency in a Booking API

Error format consistency testing

Criteria

Without context

With context

tests multiple error types

100%

error.message checked

100%

consistent shape assertion

75%

100%

supertest usage

100%

error-format-spec created

100%

no Express internals tested

100%

19%

Add First Tests to an Inherited Express API

Test prioritization for existing project

Criteria

Without context

With context

vitest installed

100%

supertest installed

100%

test script is vitest run

100%

test:coverage script

100%

app exported

100%

conditional listen

100%

5 tests or fewer

100%

tests subscriptions route

100%

happy path test

100%

validation test

100%

404 test

100%

state-focused rationale

60%

100%

deliberate scope limit documented

100%

no private function tests

100%

Add Testing to a Bookmarks API

All three npm test scripts

Criteria

Without context

With context

test:coverage script

100%

test:watch script

100%

test script

100%

vitest installed

100%

supertest installed

100%

vitest globals enabled

100%

vitest node environment

100%

conditional listen

100%

app exported

100%

in-memory SQLite

100%

no database mock

100%

beforeEach reset

100%

supertest usage

100%

5 or fewer tests

100%

22%

Add First Tests to a Maintenance-Heavy Support Ticket API

High-churn route prioritization

Criteria

Without context

With context

High-churn route tested

100%

Strategy: git history rationale

100%

Strategy: state/money routes prioritized

100%

Strategy: deliberate exclusions named

100%

Strategy: no 100% coverage goal

37%

100%

Strategy: approach documented

75%

100%

5 or fewer tests

100%

test:coverage script

100%

test:watch script

100%

Conditional listen

100%

In-memory SQLite

100%

No database mock

100%

Evaluated: 17 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Expand Test Coverage for Order Status and Filtering Audit Error Response Consistency in a Booking API Add First Tests to an Inherited Express API Add Testing to a Bookmarks API Add First Tests to a Maintenance-Heavy Support Ticket API