Question 1

How do I set up Unity Test Runner in GitHub Actions?

Accepted Answer

Refer to the GameCI documentation website for step-by-step guides on configuring the action in your workflow YAML file, including parameters for test modes and Unity versions.

Question 2

Unity Test Runner vs manual testing in Unity Editor?

Accepted Answer

Unity Test Runner automates test execution in CI/CD pipelines for consistency and regression prevention, while manual testing is error-prone and not scalable for continuous integration.

Question 3

Does Unity Test Runner support all Unity test types, like edit mode and play mode?

Accepted Answer

Yes, it typically supports common Unity test types, but check the GameCI docs for specifics on configuration and any limitations based on Unity version or project setup.

Question 4

How to handle slow test runs for large Unity projects?

Accepted Answer

Optimize by using GitHub Actions caching for dependencies, splitting tests into parallel jobs, or adjusting timeout settings, though performance may be limited by GitHub runner resources.

Question 5

Can I integrate Unity Test Runner with other GameCI actions for building?

Accepted Answer

Yes, it's designed to work with the GameCI ecosystem, allowing seamless integration with actions like Unity Builder for a complete CI/CD pipeline in game development.

Question 6

What happens if my Unity package isn't supported by Unity Test Runner?

Accepted Answer

You may need to use alternative testing methods, such as custom scripts or other CI tools, as the action only works with 'some' packages, per the README's admission.

Run Unity tests

What is Run Unity tests?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions