Search Issue Tracker

Fixed in 2017.3.0f3



Found in


Issue ID




Running Unity in batchmode gives a result file with the wrong test type

Deployment Management


Repro Steps:

1. Open command prompt
2. Write this command: "{UNITY_PATH}\Editor\Unity.exe" -batchmode -runEditorTests -projectPath "{PROJECT_PATH}" -editorTestsResultFile "{PROJECT_PATH}\results.xml"
3. Open the "results.xml" file
4. See that the "type" is equal to "TestSuite" and not to "TestRun"

Expected: The "results.xml" file to show that the "type" is equal to "TestRun"
Actual: The "results.xml" file to show that the "type" is equal to "TestSuite"

Fixed in: 2017.3.0a4

Reproduced on: 5.6.0f1,
Can't reproduce on: 5.5.2f1: just doesn't create the "results.xml" file, 5.4.0f3: Aborts batch-mode due to failure. "An exception was thrown when running unit tests"

The user also attached the "results.xml' file.

Comments (8)

  1. amitpandeyblogs

    Jun 05, 2020 19:49

  2. ELihaib

    Nov 03, 2017 17:07

    Also on 2017.2

  3. fltech

    Sep 08, 2017 07:30

  4. fltech

    Sep 08, 2017 07:28

    I reproduce this issue in version 2017.1.0f3.

  5. jkrumow

    Jul 11, 2017 12:46

    I can still reproduce this error in version 5.6.2f1.

    As mentioned above, it is currently not possible to properly publish the xml-reports on a Continuous Integration System.

  6. c9iner

    Jun 10, 2017 19:04

    We also have this issue and cannot parse the xml automatically, which makes Unit test reporting impossible.

  7. at-at

    May 10, 2017 11:21

    Specifically, the issue is that any reports produced now are malformed XML that doesn't follow either the NUnit3 or NUnit2 format specifications. This means that we cannot parse them automatically to actually *use* the results for anything meaningful.

  8. at-at

    May 10, 2017 11:18

    We have this issue too, running unity on Mac OS X 10.11.6 and triggering batchmode tests through Jenkins over SSH.
    Coupled with issue 892798 (inexplicably closed as by design?), these prevent any automated testing, which unfortunately means 5.6.0 is off limits for a lot of studios doing anything beyond indie/hobbyist projects, including us.

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.