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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.