Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.1-pre.18
Issue ID
DSTR-639
Regression
Yes
Test results get erased when restarting the Editor
To reproduce:
1. Open the project “IN-7084”
2. Open the Test Runner window (Window → General → Test Runner)
3. Click the button “Run All” to run all tests
4. Exit the editor
5. Start the editor again
6. Open the Test Runner window
Expected result: Test results are not erased
Actual results: Test results are erased
Reproducible with: 2.0.1-exp.1, 2.0.1-pre.18 (2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4)
Not reproducible with: 1.1.33 (2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6)
Could not test: 2.0.1-exp.1, 2.0.1-pre.18 (2023.1.0a6) (No Test Runner window)
Reproduced on: macOS Monterey 12.5.1 (Intel)
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note:
Since this issue is only affecting 2.0.1-exp.2 and we won't release 2.0.1 in the future, we are going to reject this issue. Feel free to re-open it if you see this behaviour in any of our not exp or preview releases