How do I install the Uloop Run Tests skill?

Run npx skillmds@latest add hatayama/uloop-run-tests-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Uloop Run Tests safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Uloop Run Tests?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Uloop Run Tests free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Uloop Run Tests?

hatayama (@hatayama) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Uloop Run Tests by hatayama — Agent Skill

Name: Uloop Run Tests
Rating: 4.2 (5 reviews)
Author: hatayama

Uloop Run Tests

Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Auto-saves NUnit XML results on failure.

hatayama Updated Sep 22, 2026

File contents

uloop run-tests

Execute Unity Test Runner. When tests fail, NUnit XML results with error messages and stack traces are automatically saved. Read the XML file at XmlPath for detailed failure diagnosis.

Usage

uloop run-tests [options]

Parameters

Parameter	Type	Default	Description
`--test-mode`	string	`EditMode`	Test mode: `EditMode`, `PlayMode`
`--filter-type`	string	`all`	Filter type: `all`, `exact`, `regex`, `assembly`
`--filter-value`	string	-	Filter value (test name, pattern, or assembly)

Global Options

Option	Description
`--project-path <path>`	Target a specific Unity project (mutually exclusive with `--port`)
`-p, --port <port>`	Specify Unity TCP port directly (mutually exclusive with `--project-path`)

Examples

# Run all EditMode tests
uloop run-tests

# Run PlayMode tests
uloop run-tests --test-mode PlayMode

# Run specific test
uloop run-tests --filter-type exact --filter-value "MyTest.TestMethod"

# Run tests matching pattern
uloop run-tests --filter-type regex --filter-value ".*Integration.*"

Output

Returns JSON with:

Success (boolean): Whether all tests passed
Message (string): Summary message
TestCount (number): Total tests executed
PassedCount (number): Passed tests
FailedCount (number): Failed tests
SkippedCount (number): Skipped tests
XmlPath (string): Path to NUnit XML result file (auto-saved when tests fail)

XML Result File

When tests fail, NUnit XML results are automatically saved to {project_root}/.uloop/outputs/TestResults/<timestamp>.xml. The XML contains per-test-case results including:

Test name and full name
Pass/fail/skip status and duration
For failed tests: <message> (assertion error) and <stack-trace>

---name: uloop-run-tests-4description: Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Auto-saves NUnit XML results on failure.---# uloop run-testsExecute Unity Test Runner. When tests fail, NUnit XML results with error messages and stack traces are automatically saved. Read the XML file at `XmlPath` for detailed failure diagnosis.## Usage```bashuloop run-tests [options]```## Parameters| Parameter | Type | Default | Description ||-----------|------|---------|-------------|| `--test-mode` | string | `EditMode` | Test mode: `EditMode`, `PlayMode` || `--filter-type` | string | `all` | Filter type: `all`, `exact`, `regex`, `assembly` || `--filter-value` | string | - | Filter value (test name, pattern, or assembly) |## Global Options| Option | Description ||--------|-------------|| `--project-path <path>` | Target a specific Unity project (mutually exclusive with `--port`) || `-p, --port <port>` | Specify Unity TCP port directly (mutually exclusive with `--project-path`) |## Examples```bash# Run all EditMode testsuloop run-tests# Run PlayMode testsuloop run-tests --test-mode PlayMode# Run specific testuloop run-tests --filter-type exact --filter-value "MyTest.TestMethod"# Run tests matching patternuloop run-tests --filter-type regex --filter-value ".*Integration.*"```## OutputReturns JSON with:- `Success` (boolean): Whether all tests passed- `Message` (string): Summary message- `TestCount` (number): Total tests executed- `PassedCount` (number): Passed tests- `FailedCount` (number): Failed tests- `SkippedCount` (number): Skipped tests- `XmlPath` (string): Path to NUnit XML result file (auto-saved when tests fail)### XML Result FileWhen tests fail, NUnit XML results are automatically saved to `{project_root}/.uloop/outputs/TestResults/<timestamp>.xml`. The XML contains per-test-case results including:- Test name and full name- Pass/fail/skip status and duration- For failed tests: `<message>` (assertion error) and `<stack-trace>`

Frequently asked questions