Search Issue Tracker
Fixed
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.5.1):
The "Rerun Failed" button now reruns only tests, that have failed.