uloop-run-tests

Execute Unity Test Runner tests and save NUnit XML results to XmlPath.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/sakastudio/cef-test --skill uloop-run-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uloop-run-tests
Source: https://github.com/sakastudio/cef-test/tree/main/.claude/skills/uloop-run-tests
Command: npx skills add https://github.com/sakastudio/cef-test --skill uloop-run-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running Unity tests and obtaining detailed results can be manual and error-prone; this Skill automates test execution and collects results to streamline diagnosis.

Core Features & Use Cases

  • Execute the Unity Test Runner for both EditMode and PlayMode tests.
  • Auto-save NUnit XML results when tests fail, including error messages and stack traces.
  • Provide a path (XmlPath) to inspect failures and generate reports for CI or reviews.

Quick Start

Run the test suite with uloop run-tests and then review the generated NUnit XML at the XmlPath for failures.

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 unit tests and automatically save the results?

You can run Unity unit tests automatically by executing the Unity Test Runner for EditMode and PlayMode, which auto-saves detailed NUnit XML results to a specified XmlPath for review.

What is the best way to diagnose failing Unity PlayMode tests?

Diagnosing failing PlayMode tests is handled by running the test suite and inspecting the auto-saved NUnit XML output, which captures error messages and stack traces for diagnosis.

Does this automated testing approach capture both EditMode and PlayMode results?

Yes, the automated test execution covers both EditMode and PlayMode tests, collecting detailed results and saving them as NUnit XML output for failure analysis or CI reporting.

How do I generate NUnit XML reports for Unity tests in a CI pipeline?

Generating NUnit XML reports for CI pipelines is done by running the Unity Test Runner and automatically saving the results, including stack traces, to the XmlPath for integration.

Why does my Unity test runner not save error messages and stack traces?

If error messages and stack traces are not saved, you need an automated test runner that explicitly captures NUnit XML output to a configured XmlPath upon test failure.