Test Media Transformations the way Devflare expects it to run
Media Transformations bindings let Workers transform video or audio from protected sources.
Test Media Transformations by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.
The first test should prove application control flow. Escalate to Wrangler remote binding or deployed tests only when the Cloudflare-hosted behavior is the thing under test.
- Best for
- video/audio transformation paths where the Worker calls Cloudflare Media Transformations
- Default harness
- or with media fixtures
- Escalate when
- The assertion depends on Cloudflare-hosted product behavior rather than the app calling the binding correctly
Start with the default test loop
Keep the first test small. Name the binding, call the one method your route uses, and assert the behavior your app owns.
When Cloudflare owns the interesting behavior, mark that as a remote/deployed lane instead of building a local fake that claims too much.
Pure Media chain-shape test
The helper surface to remember
- Use or with media fixtures for config-backed local worker tests.
- Use / for pure unit tests.
- Use or an explicit integration lane when the test needs Cloudflare credentials or a local Docker/Podman engine.
When to move beyond the default harness
- Cloudflare owns real codecs, output fidelity, duration handling, cache behavior, and billing.
- Do not let a low-fidelity mock become product documentation. Keep mocks framed as application-flow tools.
- If a test would mutate paid or remote Cloudflare state, gate it separately from ordinary unit tests.
Local tests should be honest
For Media Transformations, passing locally means the Devflare contract and app flow are correct. It does not automatically prove every hosted Cloudflare behavior.
Previous
Media Transformations internals
Media Transformations compiles from to Wrangler , with local/test behavior called out explicitly.
Next
Media Transformations example
A compact Media Transformations recipe with config and worker usage in one application path.