Huge regression compiling and Test Runner performance discovering and running tests

Unity Engine
1

I don’t know if it has to do with assembly definition files but in 2018.1b when I try to discover available tests when I click on “PlayMode” or “EditMode” button in test runner inspector it needs like 30 seconds to recover because Unity editor freezes entirely.

Also, when I run a test, it needs like another 1 minute to start running them.

On 2017.3 it’s much faster it needs some seconds only for each task.

My bug report: 987608
** @Tomek-Paszek **

1 Like
2

Hi @bdovaz ,
How many tests do you have, and how are they structured? This is news to me so I really would like to reproduce this locally so I can profile where this extra time is comming from.
Do you have some project/repro you can supply so Im sure to see the same as you?
Thanks for sharing this, will look into it as soon you give me the information.

3

Is no project/repro attached to the bug-report?

4

Ah yes sorry, thanks will look into it

1 Like
5

Any news @HaraldNielsen ? It’s been a week already.

6

@bdovaz im currently making big performance improvements and tested your project on that locally. It had no issues handling it, trying to get that included or it will be soon after

7

Thanks.

8

@HaraldNielsen Do you know in what version will it land? In beta 5 I still have the same problem.

9

Hi @bdovaz , I’m not sure if I will be able to get it in 2018.1. But I will do everything in my power to do. Otherwise, I can maybe get it in a patch

10

Ok, thanks. Please post here when you have any news.

Also, I have more minor bug reports regarding test runner:

#1001101
#987590
#987587

Can we suggest a Testing subforum? I’m really lost when I want to post something and reach Unity technical QA staff.

I would want a place to discuss Test Runner and testing features, suggestions, etc.

11

@HaraldNielsen are you going to make it? It’s been two months since my original report.

12

So is it just my project that has no reference to nunit in my solution?
If I use the [Test] attribute and us VS to reconcile the missing reference it gives me an option to “add” the nunit dll reference, and it’s the correct one according to the path, but when returning to Unity and back to VS it’s been stripped out again.
I thought this must have been an issue with 2018 beta, but this post leads me to believe otherwise.

13

@bdovaz I dont think it will make it to 2018.1, but will be in one of the next patches. Will let you know.

@AdamSingle for 2018.1 we use asmdefs as default for tests, look in there, there are a checkbox for making it as a test assembly.
If you are upgrading from an older project, the “enable playmode” are saved in the project settings, so it will still work. If you want to enable it, there are a “Enable for all assemblies” in the Test Runner window options context menu (the top left icon in the window)