Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.10f1
2019.2.0a1
2019.3.0a1
Issue ID
1171050
Regression
No
[TestRunner] NUnit tests doesn't time out when [Timeout()] attribute is set
How to reproduce:
1. Open the attached project "Nunit_case"
2. Go to Window -> General -> Test Runner
3. Run any of the given tests
Expected result: the test will time out after one second
Actual result: the test doesn't time out
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a10
Comments (2)
-
zabenok
May 06, 2020 14:36
почему у вас все через жопу?
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
It is not possible to timeout or cancel tests, as they are running in the main thread in Unity. A recommended workaround is to use [UnityTest] and then yield back null at each look, allowing the framework to timeout if needed.