Why these exist
Development evidence should be inspectable.
These cases document a known input, the media facts it was designed to expose, the expected rule behavior and the safe troubleshooting advice. Each downloadable fixture can be identified by its published SHA-256 checksum.
- 1Download a fixture
The files are generated test patterns with synthetic audio.
- 2Run the relevant checker
Use the same browser-local analyzer as any other file.
- 3Compare the verdict
The case explains which result is expected and why.
- 4Keep limitations visible
A rule-engine test is not a guarantee of editor performance on every machine.