wd-test-format

Guia detalhado para criar arquivos .wd-test no workerd, com exemplos de bindings, Durable Objects, configurações de múltiplos serviços, testes TypeScript e acesso à rede.

npx skills add https://github.com/cloudflare/workerd --skill wd-test-format

.wd-test File Format

.wd-test files are Cap'n Proto configs that define test workers for workerd's test framework. They use the schema defined in src/workerd/server/workerd.capnp.


MANDATORY: Load Reference File When Relevant

This skill is split across multiple files for context efficiency. The core patterns below cover standard single-service tests. Advanced configuration patterns live in a reference file.

You MUST read the reference file before writing or reviewing test configs that involve its subject matter. Do not guess at advanced config syntax — the reference file contains the exact patterns and fields required. Skipping it WILL lead to incorrect configs that fail at runtime.

FileMUST load when...
reference/advanced-configs.mdTest involves Durable Objects, multiple services
communicating via service bindings, outbound network access,
external services/sockets, or TypeScript source files

When in doubt about whether the reference file is relevant, load it — the cost of reading is far less than the cost of a broken test config.


Basic Structure

using Workerd = import "/workerd/workerd.capnp";

const unitTests :Workerd.Config = (
  services = [(
    name = "my-test",
    worker = (
      modules = [(name = "worker", esModule = embed "my-test.js")],
      compatibilityFlags = ["nodejs_compat_v2"],
    ),
  )],
);

Key rules:

  • The const name (e.g., unitTests) must match what the test runner expects
  • modules uses embed to inline file contents at build time
  • The first module should be named "worker" — this is the entry point
  • compatibilityFlags control which APIs are available. Use the compat-date-at tool to look up available flags and their enable dates.
  • compatibilityDate should not be used in wd-test; use specific flags instead

Module Types

modules = [
  (name = "worker", esModule = embed "my-test.js"),           # ES module (most common)
  (name = "helper", esModule = embed "helper.js"),            # Additional ES module
  (name = "data.json", json = embed "test-data.json"),        # JSON module
  (name = "data.wasm", wasm = embed "module.wasm"),           # WebAssembly module
  (name = "legacy", commonJsModule = embed "legacy.js"),      # CommonJS module
],

Bindings

Bindings make services, data, and namespaces available to the worker via env:

bindings = [
  # Text binding — env.MY_TEXT is a string
  (name = "MY_TEXT", text = "hello world"),

  # Text from file
  (name = "CERT", text = embed "fixtures/cert.pem"),

  # Data binding — env.MY_DATA is an ArrayBuffer
  (name = "MY_DATA", data = "base64encodeddata"),

  # JSON binding — env.CONFIG is a parsed object
  (name = "CONFIG", json = "{ \"key\": \"value\" }"),

  # Service binding — env.OTHER_SERVICE is a fetch-able service
  (name = "OTHER_SERVICE", service = "other-service-name"),

  # Service binding with entrypoint
  (name = "MY_RPC", service = (name = "my-service", entrypoint = "MyClass")),

  # KV namespace — env.KV is a KV namespace
  (name = "KV", kvNamespace = "kv-namespace-id"),

  # Durable Object namespace — env.MY_DO is a DO namespace
  (name = "MY_DO", durableObjectNamespace = "MyDurableObject"),
],

Test JavaScript Structure

Test files export named objects with a test() method:

// Each export becomes a separate test case
export const basicTest = {
  test() {
    // Synchronous test
    assert.strictEqual(1 + 1, 2);
  },
};

export const asyncTest = {
  async test(ctrl, env) {
    // ctrl is the test controller
    // env contains bindings from the .wd-test config
    const resp = await env.OTHER_SERVICE.fetch('http://example.com/');
    assert.strictEqual(resp.status, 200);
  },
};

BUILD.bazel Integration

wd_test(
    src = "my-test.wd-test",
    args = ["--experimental"],      # Required for experimental features
    data = ["my-test.js"],          # Test JS/TS files
)

Additional data entries for fixture files:

wd_test(
    src = "crypto-test.wd-test",
    args = ["--experimental"],
    data = [
        "crypto-test.js",
        "fixtures/cert.pem",
        "fixtures/key.pem",
    ],
)

Test Variants

Every wd_test() automatically generates three variants:

Target suffixCompat dateDescription
@2000-01-01Default, tests with oldest compat date
@all-compat-flags2999-12-31Tests with all flags enabled
@all-autogates2000-01-01Tests with all autogates enabled

Run specific variants:

just stream-test //src/workerd/api/tests:my-test@
just stream-test //src/workerd/api/tests:my-test@all-compat-flags

Scaffolding

Use just new-test to scaffold a new test:

just new-test //src/workerd/api/tests:my-test

This creates the .wd-test file, .js test file, and appends the wd_test() rule to BUILD.bazel.

Mais skills de cloudflare

workerd-api-review
cloudflare
Otimização de desempenho, design e compatibilidade de API, vulnerabilidades de segurança e conformidade com especificações de padrões para revisão de código workerd. Abrange tcmalloc-aware…
official
workerd-safety-review
cloudflare
Segurança de memória, segurança de threads, concorrência e padrões críticos de detecção para revisão de código workerd. Abrange riscos de limite V8/KJ, gerenciamento de tempo de vida,…
official
module-registry
cloudflare
Carregar ao trabalhar com o registro de módulos no workerd — lendo, modificando, depurando ou revisando a resolução, compilação, avaliação ou registro de módulos…
official
reproduce
cloudflare
Reproduzir um problema do GitHub cloudflare/agents criando um projeto mínimo de Agents/Worker e implantando-o em uma conta temporária do Cloudflare, depois relatar…
official
local-explorer
cloudflare
Como adicionar produtos/recursos ao explorador local ou API local. Use ao implementar novas APIs locais ou rotas de interface sob…
official
commit-categories
cloudflare
Regras de categorização de commits para changelogs e resumos de "novidades". DEVE ser carregado antes de categorizar commits em comandos de changelog ou whats-new. Fornece…
official
architecture
cloudflare
Use ao navegar pelo código-fonte pela primeira vez
official
changesets
cloudflare
Use ao criar um changeset, preparar um release ou atualizar versões. Abrange quais pacotes referenciar, como escrever descrições de changeset voltadas ao usuário,…
official