Testing Bindings

Test Artifacts the way Devflare expects it to run

Artifacts bindings let Workers create and manage Git-compatible repos and repo tokens.

Test Artifacts 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-managed repo metadata, temporary tokens, and artifact namespace workflows
Default harness: with artifact 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 Artifacts repo test

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

import { createMockArtifacts } from 'devflare/test'

test('creates an in-memory artifact repo', async () => {

const artifacts = createMockArtifacts()

const repo = await artifacts.create('run-logs')

expect(repo.name).toBe('run-logs')

})

The helper surface to remember

Use with artifact 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 Git protocol, durable namespace storage, permissions, and remote URLs.
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 Artifacts, passing locally means the Devflare contract and app flow are correct. It does not automatically prove every hosted Cloudflare behavior.

Artifacts internals

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

Artifacts example

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