unity-test

To run Unity tests and analyze Test Runner results, you execute EditMode or PlayMode tests and parse the generated TestResults XML reports to extract pass, fail, skip, and timing data for failure analysis.

The best way to automate Unity PlayMode and EditMode test discovery is using a workflow that starts specific test runs by name and retrieves structured outcomes directly from Unity Test Runner reports.

Yes, you can run specific Unity tests by name. The test execution workflow supports targeting individual test cases directly, then reading the TestResults XML to verify their specific pass or fail outcomes.

Yes, you need Unity MCP test commands. They are required to execute automated test workflows and trigger the TestResults XML parsing needed to evaluate test outcomes reliably.

AI agents fail to interpret Unity test outcomes correctly when relying on unavailable job tracking or incorrect testing assumptions. Using structured TestResults XML parsing ensures accurate pass, fail, and skip data retrieval.

You need to parse TestResults XML reports in Unity development workflows when validating a project after changes. Parsing provides structured pass, fail, skip, and timing information required for identifying failed test cases.