unity-testing

Structure Unity tests by separating them into Assets/Tests/Editor for EditMode and Assets/Tests/Runtime for PlayMode scenarios. This organization ensures clear test locations, reliable isolation, and faster feedback loops across different NUnit and Unity TestTools patterns.

EditMode tests run without the Unity engine fully active, allowing fast validation of pure logic, while PlayMode tests execute within the runtime environment to validate behaviors. Using both modes ensures robust test coverage for your Unity project's components and patterns.

Set up and teardown patterns in NUnit tests for Unity by using standard attributes like SetUp and TearDown within your test classes. Applying these patterns ensures proper test isolation and maintains reliable state initialization across your EditMode and PlayMode test suites.

Yes, this approach supports running tests via Unity Editor and MCP. You can author, validate, and execute your test structures directly within the Unity Test Runner, ensuring your NUnit assertions and test patterns function correctly across both environments.

Best practices for Unity test naming conventions and categorization involve using clear, descriptive names and NUnit attributes to group tests. Following these conventions improves test maintainability and helps quickly identify failures within your EditMode and PlayMode test structures.