Comments (5)
customParameters
are extra parameters for Unity's test runner which this project doesn't explicitly support (see test runner docs for the arguments that you can use as customParameters
).
This project currently doesn't support target platform tests, as they do not work in Docker. For obvious reasons, Android tests will never be able to work in Docker unless you could somehow hook up an Android emulator. If you are using a self-hosted runner instead of github-hosted runner, you may be able to get Android or any other target platform tests to work, but not with this repo as it currently is.
I made a fork of this repo where I tried to get target platform tests to work, but was unable to simply because they do not work in Docker. If you are using a self-hosted runner, you could try using my fork (on the targetPlatform
branch) to see if it will work for you. Just pass testMode: Android
.
P.S. The default target is not Standalone, it is actually both EditMode and PlayMode (which run in editor).
from unity-test-runner.
Yes, but also keep in mind that our actions use a docker image under the hood.
The images have a package installed for the targetPlatform.
You can specify targetPlatform
in builder, but not in test-runner. Though what you can do is use a specific image using customImage
.
All of these parameters are also documented in builder, and we're open to contributions that would bring builder features to test-runner. Also long term we're looking to consolidate the core of these actions into one repository.
from unity-test-runner.
Super handy info and links. Test runner docs linked as a note to the customParameters info in the gameci documentation would probably have saved me that time 👍
Out of curiosity - I can't run the Android platform tests, but can I set the Editor to Android before running them?
Many thanks!
from unity-test-runner.
Super handy info and links. Test runner docs linked as a note to the customParameters info in the gameci documentation would probably have saved me that time +1
I agree. Perhaps you could make a PR with that change?
Out of curiosity - I can't run the Android platform tests, but can I set the Editor to Android before running them?
game-ci will use whatever configuration your project is already set to. If you need to change the build target during your CI, I think you can pass -buildTarget Android
as a customParameters
(see https://docs.unity3d.com/Manual/EditorCommandLineArguments.html). That's an editor argument, so I'm not 100% if it also works with the test runner, but if it doesn't, you can also manually edit the project settings file before running the tests.
from unity-test-runner.
Ah yeah, I forgot about that part. That's a pretty niche use-case, but I do see the value in it.
Unity is currently working on official Docker support, and I'm really hoping target platform tests will just work once they finally do, then it would be nice to support it fully in game-ci.
Also see for more information: https://forum.unity.com/threads/unity-test-framework-2-0-ready-for-feedback.1230126/#post-7896961
from unity-test-runner.
Related Issues (20)
- Feature: Support Package Testing for Packages with Dependencies Outside of the Unity Registry HOT 1
- Feature: Add Caching for Package Testing
- Feature: Allow `unityVersion` of `auto` for Package Testing
- Code Coverage does not write any output anywhere HOT 2
- Unity no longer supports manual activation of Personal licenses HOT 2
- Create breaking change that updates rolling version number from 1 to 2
- Inconsistent licence activation HOT 7
- Reasource not Available by Integration HOT 5
- 'Unclassified error occured while trying to activate license.' HOT 9
- cannot access '/github/workspace/CodeCoverage': No such file or directory HOT 5
- v4.1.0 causing activation to fail when using manual offline activation HOT 5
- fullProjectPath is not set when using runAsHostUser
- packageMode workflow doesn't run playmode tests HOT 2
- chmod: cannot access '/github/workspace/CodeCoverage' HOT 1
- Licensing fails inconsistently during test step HOT 1
- Feature: Add support for Nuget dependency resolution when testing packages HOT 1
- Fails when organization or repository name have uppercase letters HOT 1
- Unity 6 HOT 1
- Support Private Package Registries in Project testing
- Print to console
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from unity-test-runner.