UA Ledger · Playable Test Bench · draft for review

Treat a resolved HTTP error as a failed asset request

Teaching laboratory. Cases run in this page against the authored functions. This is not a device panel, network approval, analytics-delivery proof or campaign result. Inputs are synthetic.

A loading screen can announce ready after receiving an error page if it treats a resolved fetch promise as success. This fixture checks the response status explicitly.

Primary documentation: MDN: http status (body read 2026-09-19).

Cases

CaseInputExpectedFixedBroken

What a pass does not prove

The test establishes status handling for a response object. A successful status still does not prove that a downloaded file is the expected asset, can be decoded or matches its manifest. A production loader needs the next acceptance stage as well, particularly when an HTML error page can arrive with an unexpected success status.