Governs Gradle test delegation, edit freezes, and fixture regeneration for XTDB.
npx skills add https://github.com/xtdb/xtdb --skill xtdb-testing
Please help me install this Agent Skill. Skill: xtdb-testing Source: https://github.com/xtdb/xtdb/tree/main/.claude/skills/xtdb-testing Command: npx skills add https://github.com/xtdb/xtdb --skill xtdb-testing
Running tests in the XTDB repository involves non-obvious rules — delegating to the gradle-tests agent, respecting the mid-run compile freeze, choosing the right Gradle task and iteration property, and handling simulation tests and golden fixtures — and getting any of them wrong produces bogus failures or false green results.
Read this skill before running or delegating any XTDB test run, then delegate the run to the gradle-tests agent with an explicit instruction not to modify any files.
High-intent search queries and answers about installing and using this skill.
Delegate every test run to the gradle-tests agent via the Task tool, stating explicitly that it must run and report only without modifying files. Never run tests yourself or use repl-explorer, and launch only one gradle-tests agent at a time.
Use ./gradlew :test --tests 'xtdb.api_test*' with underscores instead of dashes in the namespace pattern. Add --rerun-tasks when re-executing the same invocation, since Gradle caches repeated --tests runs as UP-TO-DATE.
-Piterations only drives the Clojure test.check properties; Kotlin simulation tests read -PsimulationIterations instead. Passing -Piterations=500 to a simulation run still executes 100 iterations per method, so verify the actual count in the test output.
No — editing files the build compiles during the compile phase causes bogus cross-language type errors. Either wait, or pre-run ./gradlew :testClasses yourself, then delegate the test run so its compile tasks are up-to-date and you can edit safely.
Treat the failure as caused by your change: all tests pass on main and there are no pre-existing failures. The only exception is a matching open GitHub issue labelled flaky; otherwise investigate your diff and fix the bug without disabling assertions.
Uncomment the #_aet/wrap-regen line in the namespace's use-fixtures, run with --rerun-tasks, then copy the regenerated files from build/resources/test back into src/test/resources. Re-comment the toggle and re-run to verify, since a regen run is trivially green.
himattmWrite a failing Android Kotlin/Java test that reproduces a bug before production changes.
QwenLMClassify stale PR CI failures and choose rerun, comment, or no-action responses.
metabaseEvaluate Clojure code against a running nREPL server using clj-nrepl-eval.
runbear-ioDelegate tasks between agents through an asynchronous inbox queue.
