Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.9
Issue ID
1206476
Regression
No
[Test Runner] Incorrect listing of test order of execution
Steps to reproduce:
1. Open supplied project
2. Run the tests in the Test Runner
3. Inspect the Console window
Expected: the Console logs and the test runner order of tests are identical
Actual: the "Test0" is running after "Test1"
Reproduced in: 2017.4.35f1, 2018.4.15f1, 2019.2.17f1, 2019.3.0f3, 2020.1.0a17
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This is on the edge of won't fix or by design - the test list overview is sorted alphabetic and not by execution order, those in most cases will match but not when doing a specific test ordering through Order-attribute.