Search Issue Tracker

Won't Fix



Found in


Issue ID




Runing Editor Test Runner with “-editorTestsVerboseLog teamcity” doesn't print any TeamCity log output

Unity Test Runner


To reproduce:

1. Download attached project ""
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

  1. Response avatar

    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.

Comments (3)

  1. 6bcc719977cc4176e05c812b3cc918b0?d=mm


    Jan 21, 2020 15:19

    Morpheus TV app is a free video streaming service for Android and Firestick, PC devices.

  2. 1fe9923d4b48be2dc8d83ae34f9b5d93?d=mm


    Jul 09, 2017 13:52

    You can convert the generated xml to a teamcity compatible xml with this script:

    This is what I use to be able to get test results in teamcity.

  3. 112370c99d538070c1109b6198d168c2?d=mm


    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

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.