integration-testing – Page 7 – Türker Yıldırım

Recording a real response, including the ugly ones

NoteMarch 2, 20212 min read

Hand-written fixtures encode what you believe the provider returns, and providers return things nobody believes. The 502 with an HTML body is the one that reaches production, because…

An OpenAPI document that is the test suite’s source of truth

Deep diveFebruary 23, 202110 min read

3.1 lands in February with real JSON Schema. Generating docs from code fixes half the problem; making the document the contract fixes the other half.

The migration that squashed two hundred files

Deep diveNovember 5, 20209 min read

A test suite spending ninety seconds replaying six years of schema history. Squashing is a good idea with two failure modes worth knowing first.

A golden master, for the report nobody can specify

NoteOctober 24, 20202 min read

A legacy report with no specification and forty branches cannot be unit tested, and it can be pinned: record what it produces today and fail when that changes.…

An integration test needs the real database

NoteOctober 12, 20202 min read

A repository test against a mocked connection asserts that the code calls the methods you expected, which is a restatement of the code rather than a check on…

Run a Postman collection in CI with Newman

SnippetSeptember 14, 20201 min read

Idempotency for an endpoint that takes money

Deep diveJuly 27, 202014 min read

The client timed out, retried, and the customer was charged twice. A timeout tells the client nothing about what the server did.

Compose in CI, and the service the tests need

Deep diveJuly 16, 202010 min read

The tests need MySQL and Redis, and CI gives you an empty machine. Service containers, where they differ from compose, and the readiness nothing does for you.

Asserting on the job dispatched, and on the job itself

NoteJune 30, 20202 min read

Testing that a controller queued something by starting a worker is slow and flaky; testing it by reading the queue table couples the test to the driver. Splitting…

Mutation testing, and the tests that assert nothing

Deep diveJune 18, 202010 min read

94% coverage, and a suite that passes with the logic inverted. Coverage measures execution rather than verification, and there is a tool that measures the difference.