Search Issue Tracker
Active
Under Consideration for 1.4.X
Fixed in 1.5.1
Votes
0
Found in [Package]
1.4.5
1.5.1
2.0.1-pre.18
Issue ID
DSTR-1087
Regression
No
Test Runner reruns all tests of a class, which has at least a single failed test when the "Rerun Failed" button is pressed
Reproduction steps:
1. Open the attached “ReproProject.zip“ project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the “RandomFailing“ Category
4. Press “Run All tests”
5. Press “Rerun Failed“
6. Observer
Expected result: The Test Runner reruns only the failed tests
Actual result: The Test Runner reruns all of the class’s tests, which has at least a single test that’s failed (in this case all 9 are reran)
Reproducible with: 1.4.5 (2022.3.54f1, 6000.0.31f1), 2.0.1-pre.18 (6000.0.31f1)
Reproducible on: M1 Max MacOS 15.1.1
Not reproducible on: No other environment tested
Note: Using 2.0.1-pre.18 only the successful tests are rerun instead of failed ones
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 1.5.1):
The "Rerun Failed" button now reruns only tests, that have failed.