agentleFS
utopia-riseutopia-rise/godot-kotlin-jvm/.claude/skills/run-harness-tests/SKILL.md

run-harness-tests

Skill1k starsChanged 10 days agoMITView on GitHub

Run the gdUnit4 integration tests of harness/tests against the current sources - in the editor, as a native image, or from a debug or release export - in the order CI uses. Use to verify a change end to end.

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the utopia-rise/godot-kotlin-jvm repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about utopia-rise/godot-kotlin-jvm

The biggest 5 of 49 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 49

Talked about on GitHub and Bluesky (49 times).

On GitHub · 48

43 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run only this project. Bunnymark, Bulletmark and the stress test are for explicit requests.

    line 17
  2. Very specific:

    After the last importResources, search its output for Version mismatch or couldn't be fully initialized and fix that first: the suites …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the harness tests

Work in harness/tests/. It builds against the repository sources through included builds: nothing to publish.

Before

  • Native library: build the host editor target in this checkout (build-native skill). Exports also need template_debug or template_release. Never copy a library from another checkout or worktree: even on the same commit it may have been built from an older godotJvm version, and the JVM then refuses the jars.
  • Fresh git worktree: godot-cpp is empty; clone it from the main checkout without touching the shared config with git -c protocol.file.allow=always -c submodule.godot-cpp.url=<main checkout>/godot-cpp submodule update --init godot-cpp. Export GIT_DIR to the main repository's .git for every gradlew call, or Gradle fails with "head(...) must not be null".
  • Godot editor: the official editor of the version in kt/gradle/libs.versions.toml, placed in harness/tests/bin/ or named by an absolute GODOT_EDITOR.
  • Embedded JRE, once: ./gradlew generateEmbeddedJre.
  • Run only this project. Bunnymark, Bulletmark and the stress test are for explicit requests.

Sequence

Harness tasks never depend on one another, and Gradle may start the editor before a build in the same invocation has copied the new jars. Run each line as its own invocation:

VariantSteps
editor./gradlew build → ./gradlew importResources → ./gradlew runGDTests
graal./gradlew build → ./gradlew buildGraalNativeImage → ./gradlew importResources → ./gradlew runGraalGDTests
export-debug./gradlew build → ./gradlew importResources → ./gradlew exportDebug → ./gradlew runExportedGDTests
export-release./gradlew build → ./gradlew buildRelease → ./gradlew importResources → ./gradlew exportRelease → ./gradlew runExportedGDTests

After the last importResources, search its output for Version mismatch or couldn't be fully initialized and fix that first: the suites cannot pass without a running JVM.

Native-image exports use exportGraalDebug / exportGraalRelease after the matching buildGraalNativeImage[Release].

When it goes wrong

  • Version mismatch! C++ module is X / Jar is Y: the native library is stale; rebuild it.
  • "Could not find type X" or "Identifier X not declared" across many unrelated suites: the JVM never started, so no script class exists. Look for the cause in the importResources output, usually a version mismatch; clearing caches will not help.
  • GDScript "Could not find type X" or "Identifier X not declared" only for a new or renamed script class: delete .godot/global_script_class_cache.cfg and .godot/editor/filesystem_cache*, then run importResources twice.
  • NoSuchMethodError from Scala tests only: compileScala was served from cache; rerun with ./gradlew compileScala --rerun build.
  • "Can't open GDExtension dynamic library": a Godot editor left open on the project holds the library; ask the user to close it.
  • The build regenerates the API with LF endings: git checkout generated files whose diff is empty before committing.

Report the gdUnit4 statistics line of every suite run, and any [ERROR] or JVM exception in the output even when the suites pass.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.