Guides
Use stable fixtures with less guesswork.
Patterns for testing clients, parsers, importers and download flows with small known inputs, and for pointing coding agents at fixtures that do not change.
For coding agents
Give your coding agent fixed sample data URLs instead of letting it write fixtures from memory. A v1 Payloads file never changes and has a published SHA-256, so the tests it writes stay reproducible.
Read guide GuideDeterministic API fixtures
A practical pattern for using stable public fixture URLs in repeatable client and parser tests.
Read guide GuideCross-format test data
Use one canonical users, projects and tasks dataset across formats to test conversions and parser consistency.
Read guide GuideFile download testing
Exercise real HTTP downloads without generating throwaway files or depending on a stateful fixture service.
Read guide GuideNDJSON parser testing
A repeatable way to exercise NDJSON parsing without generating input during the test.
Read guide GuideMessagePack and CBOR testing
Known binary inputs for testing buffers, media types, scalar preservation and decoder interoperability.
Read guide GuideFrontend prototype data
A minimal fixture-data pattern for prototypes that should not depend on a dynamic fake API.
Read guide