Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
987203
Regression
No
[asmdef] Test runner does not find unit tests in assemblies defined with .asmdef
Steps to reproduce:
1. Open user attached project
2. Open Test Runner window
3. Notice how NewEditModeTest1 and NewEditModeTest2 tests do not show
Expected result: test runner should find unit tests in assemblies defined with .asmdef feature
Reproduced in: 2018.2.0a1, 2018.1.0b3, 2017.3.0p2, 2017.3.0b1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
mikael_kalms
Jan 24, 2018 07:17
Response from Unity QA:
"Issue has been resolved as by design.
A new option has been added in 2018.1 version of Unity allowing you to use assembly only for test, please update if possible.
EditMode tests should have Test assemblies and only editor included under platforms."
So, it sounds there is a different workflow - create special Test assemblies, and mark them as such - from 2018.1 onward. I have not tested this myself.