Hey,
We’re running a several tests with a lot of permutations (Around 15000 in total). The duration that these tests make Unity hang is around 10 minutes however the time actually spent executing reported by the Test Runner is around 1 minute.
I’ve been checking where the extra time comes from and it looks like it is due it being in a fairly deep namespace.
Note: there are a few more levels above EditModeTests.
Removing the namespace all together drastically reduces the time the tests take to run (around 50%).
What could be the cause of this and how can we solve this?
Hey. Thanks for reporting this. We are aware of the issue, which is a performance regression introduced in 2018.2. We have a fix and it is currently being tested internally. We hope to have the new package version with the fix available this week.
1 Like
Hey,
Thanks for the quick response. Glad to see it fixed soon
Hey. The performance regression fix is available now with version 1.1.2
https://docs.unity3d.com/Packages/com.unity.test-framework@1.1/changelog/CHANGELOG.html
Please let me know if it fixes your issue.
Hey,
We’re still on 2019.1 unfortunately, we’re trying to upgrade to 2019.2 however we’re still waiting on another bug to be fixed.
1 Like