Uw Unity Test Runner

Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit

47 stars 6 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add devdavv/unity-ai-workflow --skill uw-unity-test-runner
Manual install
git clone --depth 1 https://github.com/devdavv/unity-ai-workflow.git /tmp/unity-ai-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/unity-ai-workflow/.claude/skills/uw-unity-test-runner ~/.claude/skills/uw-unity-test-runner

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Unity Test Runner

Generate NUnit tests mapped from GDD Gherkin scenarios.

## Before You Start

1. Read `docs/GDD.md` for Gherkin scenarios (Given/When/Then) to convert into tests.
2. Ensure a `Tests.asmdef` exists for the feature — create with `uw-unity-feature-scaffold` if needed.
3. Read `docs/CODING_STANDARDS.md` for async patterns (`Awaitable` + `CancellationToken`) used in PlayMode tests.
4. Read `docs/NAMING_CONVENTIONS.md` for test class and file naming.
5. Check `docs/ProjectConfig.yaml -> mcp.unity_mcp` — if `true`, use `run_tests` / `get_test_job` to execute tests. Otherwise, instruct the user to run via Unity Editor (Window -> General -> Test Runner).

## Test Types

| Type | Location | When to Use | Runner |
|------|----------|-------------|--------|
| **EditMode** | `Tests/EditMode/` | Pure logic — no MonoBehaviour lifecycle, no scene required | `[Test]` with NUnit |
| **PlayMode** | `Tests/PlayMode/` | Needs `Awake`/`Start`/`Update`, scene loading, physics, or coroutines | `[UnityTest]` + `IEnumerator` |

**Default to EditMode** whenever possible — they're faster, more reliable, and easier to debug. Only use PlayMode when the code under test depends on Unity's runtime lifecycle.

## Gherkin to Test Mapping

Each Gherkin scenario from the GDD becomes one test method. The Given/When/Then structure maps directly to Arrange/Act/Assert:
Read the full skill on GitHub

Details

Skill name
uw-unity-test-runner
Path
.claude/skills/uw-unity-test-runner/SKILL.md
License
MIT
Repo updated
1 April 2026

FAQ

What does the Uw Unity Test Runner skill do?

Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit

How do I install the Uw Unity Test Runner skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add devdavv/unity-ai-workflow --skill uw-unity-test-runner. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Uw Unity Test Runner popular?

It lives in devdavv/unity-ai-workflow, which has 47 GitHub stars and 6 forks.

Related skills

Uw Code Review

47

devdavv/unity-ai-workflow

Pre-commit code quality review for Unity C# code. Checks against Rules, CODING_STANDARDS.md, NAMING_CONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code", "check my implementation", "pre-commit review", "code review", "check before commit", "is this ready to commit", "review my changes", or any request to validate code quality before committing.

Software Development

Uw Dependency Injection

47

devdavv/unity-ai-workflow

Opt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, an

Software Development

Uw Game Feel Integrator

47

devdavv/unity-ai-workflow

Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Mat

Images, Video & Audio

Testing and Quality

49

dynamics365ninja/d365fo-cli

Write and run D365FO tests — SysTestCase unit tests, the ATL acceptance library, and the offline gates (`validate xpp`, `validate references`, `lint`) that catch defects before a build. Invoke when the user asks how to test X++, add a unit test, assert on behaviour, or check code quality without a VM.

Testing & QA26

Uw Unity Feature Scaffold

47

devdavv/unity-ai-workflow

Create a complete feature module with folder structure, Assembly Definition (.asmdef), test assembly, and namespace. Use when adding a new feature, system, or module to a Unity project. Triggers on requests like "create a new feature", "scaffold a module", "add a combat system", "I need a health system", "set up inventory", "create a new module for X", "add a new system", "new feature folder", or any task requiring new folders, assemblies, or namespaces for a gameplay feature — even when the user just names a system they want to build from scratch. Reads ProjectConfig.yaml for folder_strategy

Testing & QA

Condition Based Waiting

43

obra/clank

Replace arbitrary timeouts with condition polling for reliable async tests

Testing & QA26

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.