Search Issue Tracker

Fixed in Unity 2017.2

Votes

8

Found in

5.6.1p3

Issue ID

926540

Regression

Yes

[Unity Test Runner] Unity Test Runner no longer shows tests contained inside custom assemblies

Scene Management

-

-

Priority: 7Not yet prioritized for a release

-

Severity: 3Workaround is possible

Since Unity 5.6 and the new runner, NUnit tests contained within custom assemblies are no longer able to be used by the runner.

To repro:
1) Open attached project
2) See in Test Runner Window that only the tests in the two CS scripts are shown. It should instead also show the tests contained within the DLLs.

More info:

- MorePlayModeTests.dll contains more play mode tests: MorePlayModeTests.Tests.PlayModeTestsSimplePasses and MorePlayModeTests.Tests.PlayModeTestsWithEnumeratorPasses

- MoreEditModeTests.dll contains MoreEditModeTests.Tests.AnotherEditModeTestsSimplePasses and MoreEditModeTests.Tests.AnotherEditModeTestsWithEnumeratorPasses

- NoPlayModeTests.dll contains no tests. Contains Clicker MonoBehaviour class and a Frog class (not MonoBehaviour).

- NoEditModeTests.dll contains no tests. Contains DatabaseChecker class with CheckDatabase method, MenuItem ("Example/Check Database").

There are also two scripts containing tests. PlayModeTests.cs and EditModeTests.cs.

Only the tests from the two cs scripts show in the Test Runner.

.mdb files are included for each DLL.

Comments (1)

  1. C997357bd71ecfb58efa6d3474d7180e?d=mm

    pahe

    Oct 30, 2017 14:19

    Question is, how to get the fix for 5.6 if you can't update to 2017.2?

All about bugs

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