Testing Bindings

Test Pipelines the way Devflare expects it to run

Pipelines bindings let Workers send event records into Cloudflare-managed ingestion pipelines.

Test Pipelines 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: Worker-side event ingestion into Cloudflare Pipelines
Default harness: or
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.

Assert recorded Pipeline sends

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

import { createMockPipeline } from 'devflare/test'

test('records sent pipeline rows', async () => {

const pipeline = createMockPipeline()

await pipeline.send([{ message: 'signup' }])

expect(pipeline._getRecords()).toEqual([{ message: 'signup' }])

})

The helper surface to remember

Use or 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

Devflare records local sends but does not create pipelines, manage R2 sinks, or emulate production batching.
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 Pipelines, passing locally means the Devflare contract and app flow are correct. It does not automatically prove every hosted Cloudflare behavior.

Pipelines internals

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

Pipelines example

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