Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ivanmurzak/tests-run
Execute Unity tests (`EditMode` or `PlayMode`) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
Passed 20 of 21 test cases with the skill, and 10 of 21 without it.
and 10 more in the full report
12 fixed9 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/18/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to run all tests inside the UI.Menu.Tests namespace in EditMode without details for passing tests, but including failure stack traces. Formulate the CLI tool call.
| Checked | Without skill | With skill |
|---|---|---|
| unity-mcp-cli run-tool tests-run | Missed | Passed |
| sets testNamespace to UI.Menu.Tests and includeStacktrace to true | Missed | Passed |
The instructions your model reads when the skill loads.
Execute Unity tests and return detailed results. Supports filtering by test mode, assembly, namespace, class, and method. Recommended to use 'EditMode' for faster iteration during development. Precondition: every open scene MUST be saved (no unsaved changes). If any open scene is dirty, this tool throws an InvalidOperationException listing the dirty scenes; save them and retry.
testMode (default EditMode) — EditMode or PlayMode. EditMode is faster; prefer it during iteration.testAssembly / testNamespace / testClass / testMethod — optional, layered filters. Namespace and class filters become regex groupNames so the validation count and Unity's execution stay in sync. testMethod must be fully qualified (Namespace.FixtureName.TestName).query — RQL over the tests source instead of the four filters: any selection, run as ONE Test Runner run, e.g. tests | where fixture == "PlayerTests" or categories contains "Smoke". One mode per run; the mode comes from the selected tests. Explore first with rql-query: tests | where fullName contains "Spline" | select fullName mode.result — RQL stages applied to the results (source testResults: name status durationMs message stackTrace), e.g. where status == "Failed" | select name message; the answer is then a summary line plus compact RQL text.includePassingTests (default false) — include details for passing tests; otherwise only failing test details are returned.includeMessages (default true) — include per-test result messages.includeStacktrace (default false) — include stack traces for failing tests.includeLogs (default false) — include console logs captured during the run.logType (default Warning) — minimum log severity to include.includeLogsStacktrace (default false) — include log stack traces (large payload; use sparingly).If the AssetDatabase refresh triggers compilation, the tool persists the run parameters to SessionState, returns Processing, and resumes the run automatically after the reload completes. Pre-existing compilation errors short-circuit the run and return the error details so the caller can fix the project first.
unity-mcp-cli run-tool tests-run --input '{
"testMode": "string_value",
"testAssembly": "string_value",
"testNamespace": "string_value",
"testClass": "string_value",
"testMethod": "string_value",
"query": "string_value",
"result": "string_value",
"includePassingTests": false,
"includeMessages": false,
"includeStacktrace": false,
"includeLogs": false,
"logType": "string_value",
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.