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

Assertions about shape, not about values

NoteJune 11, 20201 min read

A collection asserting that the total is 4900 fails whenever the seed data changes, which is every sprint — and gets deleted rather than fixed. Asserting on presence…

An HTTP client that is part of the framework

Deep diveMarch 17, 202010 min read

Four services, four hand-rolled clients, four retry policies. 7.0 wraps Guzzle, and the wrapper is the point rather than the transport.

Transactions per test, until a second connection

NoteMarch 5, 20202 min read

Truncating every table between tests costs a statement per table per test; a transaction and a rollback is one of each. The second-connection case produces a genuinely confusing…

Contract tests that live in the repository

Deep diveMarch 3, 202010 min read

The collection lived in one person’s account, which is not version control. An endpoint changed and the client team found out from an error.

PHPUnit 9 and the assertions that finally went

Deep diveFebruary 25, 20209 min read

What 8 deprecated, 9 removes, and the deadline was a year. Rector does the renames; the one it cannot decide is the one that changed behaviour.

Newman runs the collection in CI, which is the point

NoteFebruary 19, 20201 min read

A manual test is a memory, and memories are per person. The same collection run by a machine on every push is a test. The –env-var override is…

An API document that is generated, not maintained

Deep diveJanuary 9, 202014 min read

The documentation was written in January and the API changed in March. Documentation written by hand is a copy, and copies drift — usually within a sprint.

A baseline is what makes static analysis adoptable

Deep diveDecember 10, 201914 min read

0.12 shipped in December and the ignoreErrors list can be deleted. A generated debt register, a ratchet that only shrinks, and a level to stop at.

An integration test needs the real database or it proves nothing

NoteNovember 19, 20192 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…

Transactions per test beat truncation, until a second connection

NoteOctober 10, 20192 min read

Truncating every table between tests costs a statement per table per test, which on forty tables and four hundred tests is sixteen thousand statements; a transaction and a…