Testing Backwards-Compatible Additive Changes
A field that looks optional can still break a client that parses its responses strictly.
Read articleAuthor
A field that looks optional can still break a client that parses its responses strictly.
Read articleA cache rule is only as good as the stale and revalidation cases.
Read articleA matrix that only proves the admin can do everything has not really been tested.
Read articleA client that gives up at the wrong millisecond either waits forever or drops a request that was about to succeed.
Read articleA race that appears once a week is a test waiting to be made deterministic.
Read articleA user in a distant region waits on a different clock than your local machine.
Read articlePact and Prism both touch contracts and mocks, but they start from opposite ends.
Read articleA token expires at a moment in time, so the mock should judge it on the clock.
Read articleA multipart request can fail on one part while the rest are valid.
Read articleThe row at the page edge is where one-off errors show up.
Read articleA mock is a frozen snapshot; the real API keeps moving, and the two can quietly diverge.
Read articleOne GraphQL response can hold both successful fields and failed fields at once.
Read article