Guide Unity package test workflows with TDD and NUnit patterns.
npx skills add https://github.com/punkfuncgames/tetris-clone --skill testing-punkfuncgames
Please help me install this Agent Skill. Skill: testing Source: https://github.com/punkfuncgames/tetris-clone/tree/main/.claude/skills/testing Command: npx skills add https://github.com/punkfuncgames/tetris-clone --skill testing-punkfuncgames
This reference codifies a test-driven development workflow and testing standards for a modular Unity project to prevent regressions, false-green tests, and inconsistent test patterns across packages.
Add an EditMode test following the Test File Template, run the package Tests, and confirm the new test passes while avoiding forbidden workaround patterns.
High-intent search queries and answers about installing and using this skill.
To eliminate false-green tests in Unity package tests, enforce a test-first TDD workflow using NUnit and NSubstitute templates for EditMode and PlayMode suites, ensuring root-cause fixes and per-class coverage validation in CI.
Forbidden testing patterns in Unity UPM packages include swallowing exceptions, changing test expectations to force passes, and other false-green workarounds. The testing infrastructure enforces guardrails and a decision flow to drive root-cause fixes instead of masking failures.
Yes, Unity testing infrastructure supports NSubstitute mocking with UniTask compatibility. It provides MockFactory and TestFixtures utilities to create test doubles and ScriptableObject data while maintaining MessagePipe and VContainer framework pattern guidance.
Write EditMode and PlayMode test suites for Unity UPM packages by following the provided Test File Template, utilizing NUnit and NSubstitute frameworks, and validating behavior through CI pipelines to ensure 100% coverage for code changes.
Unity unit tests may pass but miss regressions due to false-green patterns like swallowing exceptions or altering expectations. Enforcing strict TDD workflows, forbidden-pattern checks, and per-class coverage requirements eliminates these misleading test results.
The best way to achieve 100% test coverage for changes in modular Unity projects is mandating test-first TDD practices, using NUnit and NSubstitute templates for EditMode and PlayMode tests, and validating all modifications through CI guardrails.
ZzulinAdvises Unity refactors to extract pure C# logic and plan Edit/PlayMode tests.
Dev-GOMRun Unity Test Framework tests and generate failure reports.
creator-hianConfigure VContainer dependency injection for Unity projects.
gil00pitaAutomate JavaScript and TypeScript testing with Jest, including mocking and coverage reporting.
