Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.30
Issue ID
DSTR-402
Regression
No
[Test Runner] Consecutive tests results in play mode do not have fresh context
Reproduction steps:
1. Open Attached project "Tests"
2. Open PlayMode in Test Runner (Window -> General -> Test Runner -> PlayMode)
3. Run TestA
4. Run TestB
5. Run All
Expected result: Tests passed when run separately and when run together
Actual result: when passed together "TestB" failed.
Reproducible with: 1.1.29, 1.1.30 (2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.1.2f1, 2022.1.0a14)
Comments (1)
-
Whatever560
Oct 28, 2021 14:24
Thanks for investigating on this. You can find additional infos on how we are working around it with a fork on Zenject test cleaner, although its not optimal because highly subject to each test details, loaded plugins, etc ...
https://github.com/modesttree/Zenject/pull/249
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note:
The Enter and ExitPlayMode commands are intended for EditMode tests. When run in PlayMode, it can give unintended effects. If we move the test into an EditMode test assembly, then it works as intended and both tests can be run after each other.
We are considering a more general solution, which will allow for automatically reload the scene after each test.