Why the route matters more than the file
Inspecting deliverables one at a time is expensive and answers a question about one file. Testing a delivery route answers the same question for everything that will ever pass through it, and routes change rarely. As of 2026-09-12.
| What is tested | What it covers |
|---|---|
| One file, inspected | That file |
| One route, tested end to end | Everything through that route until it changes |
| A vendor page, read | What the vendor published on a date |
| Nothing | Whatever anybody assumes |
Inclusion rule. Ways of establishing what a published asset carries. Order. From the narrowest coverage to the broadest, then the two that cover nothing.
1A route is the unit that decides outcomes
Export settings, an editor, an upload, a platform's own processing and whatever derivatives it builds. Each step either preserves something or does not, and it does the same thing to every asset.
So a route is a small number of steps with a fixed behaviour. Establishing that behaviour once is the cheapest complete answer available to anybody publishing at volume.
2How to run the test
Produce one asset with everything a normal delivery carries, send it through the whole route including the platform, and inspect the copy an audience would receive. Not the master, and not the export.
Record what arrived and what did not. That record is worth more than any vendor page, because it describes the pipeline actually in use rather than a component of it.
3Retest when something upstream is replaced
A new editor, a new export preset, a new distribution partner or a platform change can each alter the outcome for everything. Nothing announces these events in terms a production would notice.
Which argues for a cheap test rather than a thorough one. Something that takes an afternoon gets repeated; something that takes a week gets done once and then quietly relied on for years.
4What a route test cannot tell you
It describes what survives, not what was there to begin with. If a tool applies nothing, a perfectly preserving route still delivers nothing, and the test will look identical to a stripping route on a marked file.
So the two questions have to be answered separately: what the tool applies, which is a documentation question, and what the route keeps, which is not.
Background on mechanism and practice. Nothing here is attributed to a product, and nothing here is a reading of any instrument. The sourced material is on the generator table. Related: Version fields, Re-render is not repair.