Search Issue Tracker
By Design
Votes
0
Found in
2019.3.5f1
2019.4
2019.4.32f1
2020.3
2021.1
2021.2
2022.1
2022.2
Issue ID
1399029
Regression
No
Subsequent Tests fail when MonoBehavior stops the Editor
How to reproduce:
1. Open the attached project "InvokeTestingBug.zip"
2. Open Test Runner (Window > General > Test Runner)
3. Press the "Run All" button
Expected result: Subsequent "ZzzFurtherTests" test succeeds
Actual result: Subsequent "ZzzFurtherTests" test fails
Reproducible with: 2019.3.5f1, 2019.3.16f1, 2019.4.35f1, 2020.3.27f1, 2021.1.28f1, 2021.2.10f1, 2022.1.0b6, 2022.2.0a3
Not reproducible with: 2019.3.4f1
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
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Hub Window is closed when closing Unity AI Window via the OS Window Close Button on Windows
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Resolution Note:
Exiting the player or PlayMode from a PlayMode-test is not supported and can give unforeseen results.