Search Issue Tracker
Won't Fix
Votes
3
Found in
5.6.0f3
Issue ID
909727
Regression
Yes
Runing Editor Test Runner with “-editorTestsVerboseLog teamcity” doesn't print any TeamCity log output
To reproduce:
1. Download attached project "TeamCity.zip"
2. Open Command Line and write this:
"D:\path to your Unity location\Unity 5.6.0f3\Editor\Unity.exe" -batchmode -logFile - -projectPath D:\path to your project location -runEditorTests -editorTestsResultFile .\test.xml -editorTestsVerboseLog teamcity
3. Press Enter
Expected result: Teamcity formatted log messages about test progress in log
Actual result: No log messages about TeamCity
Reproduced on Unity 5.6.0a1, 5.6.0f3, 5.6.1f1 and 2017.1.0b4
Not Reproduced on Unity 5.3.8f1, 5.4.5p1, 5.5.2p2, 5.5.3p2
Regression on Unity 5.6.0a1
Comments (3)
-
MNNoxMortem
Jul 09, 2017 13:52
You can convert the generated xml to a teamcity compatible xml with this script:
http://answers.unity3d.com/questions/1355795/can-unity-56s-test-runner-optionally-output-nunit.htmlThis is what I use to be able to get test results in teamcity.
-
einWikinger
Jul 07, 2017 14:02
This is very annoying! We've been relying on unit testing in Unity for a long time and ditched our own solution for the builtin nunit test runner. It all worked well but we practically live without a proper working CI since 5.6.0f3! It just puts a big pile of risks on developers which otherwise would be easily catched by the CI, since there is no proper workaround to get test results. Even the nunit report XML is broken and, in our case, can't be read by TeamCity.
I've also been reporting this issue since may, but not a single change has been found in the changelogs since then. This is urgently needed! But I wonder why this issue doesn't impact more people - could anyone find a workaround yet?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2017.2.0f3):
This is not supported anymore. If there is a good use case for it, another bug report should be submitted.