unity-test

Run Unity tests asynchronously by initiating a test run that returns a jobId for polling. You then poll the test result endpoint using this jobId to fetch summaries and determine pass or fail rates upon job completion.

Yes, you can enumerate available tests by mode and apply a name filter to identify specific tests. This allows you to run targeted Unity test suites by name or filter criteria instead of executing the entire project test suite.

Integrate Unity tests into CI by running EditMode tests after code changes and polling the asynchronous job results. Start a test run to get a jobId, poll for completion, and fetch summaries to validate code and catch regressions quickly.

Yes, it supports generating EditMode and PlayMode test script templates to bootstrap unit tests. This integrates with debugging flows to perform compilation checks and helps structure new test creation within Unity projects.

A Unity test run returns a jobId because the execution is handled as an asynchronous job. You must poll this jobId to check the job status and retrieve the final test summaries once the background execution completes.

You can cancel running Unity test jobs during the asynchronous polling phase. Since test runs execute as background jobs, use the job management features to terminate the active process before it naturally completes.