skills.rest
hatayama
hatayamaCOMMUNITY
Explore all skills by this author →
GitHub

uloop-run-tests

Run Unity EditMode and PlayMode tests and save NUnit XML results.

500|44|Updated Jun 15, 2025
Search Tags:#automation#testing#nunit#unity#ci#test-runner#test-results
One-click install
npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-run-tests-hatayama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uloop-run-tests
Source: https://github.com/hatayama/unity-cli-loop/tree/main/.agents/skills/uloop-run-tests
Command: npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-run-tests-hatayama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables developers and CI systems to run Unity EditMode and PlayMode unit tests and quickly identify failing tests with actionable diagnostics and saved NUnit results, removing guesswork from test failures and speeding up debugging.

Core Features & Use Cases

  • Run EditMode and PlayMode tests: Execute full test suites or targeted tests using filters for exact names, regex, or assemblies.
  • Structured summary output: Returns a JSON summary including Success, Message, TestCount, PassedCount, FailedCount, and XmlPath for programmatic consumption.
  • Failure artifacts for diagnosis: Automatically saves NUnit XML result files on failures containing error messages and stack traces for each failed test.
  • Use Case: Integrate into local developer workflows or CI pipelines to validate code changes, reproduce intermittent failures, and collect machine-readable test reports.

Quick Start

Run the Unity test suite for the current project in EditMode and return the JSON summary while saving the NUnit XML results if any tests fail.

Frequently Asked Questions about uloop-run-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Unity EditMode and PlayMode tests and get NUnit XML results?▼

You can run Unity EditMode and PlayMode tests using the Unity Test Runner. It executes your test suites and automatically saves NUnit XML result files containing error messages and stack traces for any failing tests.

Can I filter Unity tests by name or assembly when running them in CI?▼

Yes, you can filter Unity tests using exact names, regex patterns, or assembly names. This allows you to execute targeted tests rather than the full suite, which is useful for validating specific code changes in local or CI workflows.

How do I get a structured summary of Unity test results for programmatic consumption?▼

Executing Unity tests returns a structured JSON summary including Success, TestCount, PassedCount, FailedCount, SkippedCount, Message, and XmlPath. This machine-readable output is designed for programmatic consumption in CI pipelines.

Where are Unity test failure artifacts and NUnit XML files saved for diagnosis?▼

NUnit XML result files are saved to the .uloop/outputs/TestResults/<timestamp>.xml directory. These failure artifacts contain detailed error messages and stack traces to help diagnose and debug failing tests quickly.

What is the best way to automate Unity test execution and capture detailed failures?▼

Automating Unity test execution through the Test Runner captures detailed failures by saving NUnit XML outputs and returning a JSON summary. This removes guesswork from test failures and speeds up debugging in development and CI environments.

Related Skills

Explore More Software Engineering Skills→
RayzerrekRayzerrek

unity-test

Run and manage Unity Test Runner jobs with async polling.

Community
Advanced
cffrankcffrank

test-analyzer

Parse Vitest JSON output to generate test quality metrics and reports.

Community
Advanced
DmitriyYukhanovDmitriyYukhanov
6

unity-tests-run

Run Unity Test Framework tests via CLI batchmode with platform and filter options.

Community
Intermediate
Dev-GOMDev-GOM
95

unity-test-runner

Run Unity Test Framework tests and generate failure reports.

Community
Advanced