Search Unity

Resolved Unity Editor Test runner results not written in 2017.1?

Discussion in 'Testing & Automation' started by eppz, Jul 12, 2017.

  1. eppz

    eppz

    Joined:
    Aug 2, 2014
    Posts:
    172
    In 5.5.0f3 this just worked fine!

    I'm basically using Unity Test Runner / Running from the command line commands per documentation.
    I made a shell script (test.command) that wraps up this into VS Code task.json.

    Then I upgraded to 2017.1.0f3, and the now no test result file generated.
    (the tests run fine in Unity Editor, but not in command line).

    Please shed me a light.
    For reference I put the entire project to GitHub.
     
    Last edited: Jul 12, 2017
  2. eppz

    eppz

    Joined:
    Aug 2, 2014
    Posts:
    172
    I found it in Editor.log:
    Code (CSharp):
    1. ...
    2. Warning: Running tests in batch mode will not work when "quit" is specified.
    3. ...
    Should update documentation though at https://docs.unity3d.com/Manual/CommandLineArguments.html. It says "quit is not required, because the Editor automatically closes down after the run is finished.". Should say the truth instead above.

    Anyway, Unity should hire a ~200 sized staff to fix up then maintain documentation / examples.
     
    Last edited: Jul 12, 2017
  3. ikriz

    ikriz

    Joined:
    Dec 3, 2009
    Posts:
    88
    It does say the truth... quit is not required when using batchmode. so remove the quit from the commandline and your warning is gone ;)
     
unityunity