Testing Bindings

Test Dispatch Namespaces the way Devflare expects it to run

Dispatch namespace bindings let Workers for Platforms route requests to tenant Workers by name.

Test Dispatch Namespaces 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: platform Workers that dispatch to tenant Workers by name
Default harness: with
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.

Fixture tenant dispatch locally

import { expect, test } from 'bun:test'

import { createMockDispatchNamespace } from 'devflare/test'

test('dispatches to a configured tenant', async () => {

const dispatcher = createMockDispatchNamespace({

workers: {

default: async () => new Response('tenant-ok')

}

})

expect(await (await dispatcher.get('default').fetch('https://example.com')).text()).toBe('tenant-ok')

})

The helper surface to remember

Use with 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 dispatch namespace creation, tenant uploads, Worker metadata, and production routing.
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 Dispatch Namespaces, passing locally means the Devflare contract and app flow are correct. It does not automatically prove every hosted Cloudflare behavior.

Dispatch Namespaces internals

Dispatch Namespaces compiles from to Wrangler , with local/test behavior called out explicitly.

Dispatch Namespaces example

A compact Dispatch Namespaces recipe with config and worker usage in one application path.