Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only.

    Please, do not make any changes to your username or email addresses at id.unity.com during this transition time.

    It's still possible to reply to existing private message conversations during the migration, but any new replies you post will be missing after the main migration is complete. We'll do our best to migrate these messages in a follow-up step.

    On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live.


    Read our full announcement for more information and let us know if you have any questions.

Resolved New Test Runner doesn't run the tests in pre-compiled dlls

Discussion in 'Testing & Automation' started by Xtro, Dec 26, 2017.

  1. Xtro

    Xtro

    Joined:
    Apr 17, 2013
    Posts:
    616
    In Unity 2017.3, the built-in test runner displays the tests in dlls but doesn't run them.
    Are you aware of this problem? Working on it already? Is there an ETA for fixing it?

    Please see screenshots. When I click "run all" button. Unity enters playmode. The project name shows a green check icon but individual tests don't show green or red test result icons.

    Before Unity 2017.3, it wasn't event displaying the tests which are implemented in dlls. For reference: https://forum.unity.com/threads/new...sts-in-pre-compiled-dlls.489107/#post-3254334
     

    Attached Files:

  2. HaraldNielsen

    HaraldNielsen

    Unity Technologies

    Joined:
    Jun 8, 2016
    Posts:
    142
    Hi @Xtro,
    I recently fixed an issue with precompiled assembly file names containing `.`'s. I was sure it got included in the release but just tested the released version and seem like it was not. Will make sure we get this fixed in an upcoming patch, and will write here what patch it will be part of.
     
  3. HaraldNielsen

    HaraldNielsen

    Unity Technologies

    Joined:
    Jun 8, 2016
    Posts:
    142
    This fix will be in patch 2017.3.0p2 and its estimated to be released around the 10th.