Follow steps below.
# Set up our bridge worker w/ default settings for testing
# --persist-to .wrangler/state
# --port 8787
# Uses the same `wrangler.toml` with `test-runner`
wrangler dev ../worker/index.js
# Set up test-runner worker w/ another cache storage
# If the same storage used, it ends up with SQL dead lock error...
# Also uses the same `wrangler.toml` with `bridge-worker`
wrangler dev ./runner-worker.js --persist-to .wrangler/_state --port 8686
# Run all specs
curl -sN 'http://127.0.0.1:8686?t=kv&t=r2&t=d1&t=queue&t=vectorize'
# Or specify which specs to run
curl -sN 'http://127.0.0.1:8686?t=kv'
curl -sN 'http://127.0.0.1:8686?t=service'If you test SERVICE bindings, extra steps are required in advance.
cd ./test-service
wrangler dev ./service.js --port 8585What should be tested is
- ACTUAL bindings: by our bridge implementation
and
- EXPECT bindings: by
wrangler dev
accept the same inputs and return the same outputs.
The results(e.g. delete() surely delete entry) is not our concern.
And support only the latest version of wrangler.