find-and-run-tests
How to find, build, and run tests in workerd. Covers wd-test, kj_test target naming, bazel query patterns, and common flags. Also covers parent project integration tests if workerd is used as a submodule. Load this skill when you need to locate or run a test and aren't sure of the exact target name or invocation.
Install
git clone https://github.com/cloudflare/workerd /tmp/workerd && ln -s /tmp/workerd/.opencode/skills/find-and-run-tests ~/.claude/skills/find-and-run-testsFrom README
Finding and Running Tests workerd Tests Test types | Type | File extension | BUILD macro | Target suffix | | ----------------- | -------------- | ----------- | ------------------------------ | | JS/TS integration | .wd-test | wdtest() | None (target name = rule name) | | C++ unit | -test.c++ | kjtest() | None | Finding targets Running Common flags | Flag | Purpose | | ------------------------ | ------------------------------------------- | | --testoutput=streamed | Stream test output to terminal in real time | | --nocachetestresults | Force re-run, don't use cached results | | --testtimeout=120 | Override default test timeout (seconds) | --- Parent Project Integration Tests If workerd is used as a submodule in a parent project, that project may have its own integration test framework with different conventions. Load the parent-project-skills skill to discover those conventions. General principles that apply to any integration test framework Target naming with variant suffixes.
More from this repo
bazel-test-hygiene
Mandatory rules for running bazel tests during development.
commit-categories
Commit categorization rules for changelogs and "what's new" summaries.
dad-jokes
After completing any task that took more than ~5 tool calls, or after long-running builds/tests finish, load this skill...