cloudflare-workers:test-setup

Workers Test Setup Command

Set up comprehensive testing for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers.

Execution Workflow

Phase 1: Detection - Analyze Current Setup

Read the project to understand its current state:

1. Check if package.json exists
2. Check if vitest.config.ts or vitest.config.js exists
3. Check if wrangler.jsonc or wrangler.toml exists
4. Detect bindings used in the Worker (D1, KV, R2, DO, Queues, AI)
5. Check if any tests already exist (**/*.test.ts, **/*.spec.ts)

Store findings for later phases.

Phase 2: User Preferences - Ask Questions

Use AskUserQuestion to gather preferences:

Question 1: "What type of tests do you want to set up?"

• Options:
  • Unit tests only (fast, isolated function testing)
  • Integration tests only (full request/response testing)
  • Both unit and integration tests (Recommended)

Question 2: "Which bindings do you need to mock?"

• MultiSelect: true
• Options (based on detection):
  • D1 (SQLite database)
  • KV (key-value storage)
  • R2 (object storage)
  • Durable Objects (stateful coordination)
  • Queues (message queues)
  • Workers AI (AI inference)
  • Vectorize (vector database)
  • None (no bindings used)

Question 3: "Do you want code coverage reporting?"

• Options:
  • Yes, with coverage thresholds (Recommended)
  • Yes, without thresholds
  • No

Phase 3: Validation - Check Prerequisites

Before proceeding, validate:

1. Node.js/Bun installed: Run node --version or bun --version

   • If neither exists, abort with error: "Node.js or Bun required. Install from https://nodejs.org/ or https://bun.sh/"

2. package.json exists:

   • If not, abort with error: "No package.json found. Run npm init or bun init first."

3. Wrangler configured:

   • If no wrangler.jsonc/toml, warn: "No wrangler config found. Tests may need manual binding configuration."

4. No existing vitest.config:

   • If exists, ask: "vitest.config already exists. Overwrite?"
   • If user says no, abort gracefully