Search Issue Tracker
In Progress
Under Consideration for 1.4.X
Fix In Review for 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
- Lights on Renderer Features break when rendering at lower resolution with "Forward+" Rendering Path
- [Android] High GPU usage is reported when the device is rotated into landscape orientation and the application is Vsync bound
- Aspect ratio toolbar doesn’t have tooltip to display contextual help or information when hovering over it
- Particle System isn't playing in Play Mode when it's out of view in Scene view, Simulation Space is set to "World", and Culling mode is set to "Pause and Catch-up"
- [Android] GameObject not rendered when rendering is performed with the help of "BatchRendererGroup"
Resolution Note (fix version 1.5.1):
The "Rerun Failed" button now reruns only tests, that have failed.