Search Issue Tracker
Fixed
Fixed in 1.4.5
Votes
1
Found in [Package]
1.4.3
2.0.1-pre.18
Issue ID
DSTR-1041
Regression
No
Test Runner test is inactive when Player test is run
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the "Player" tab
4. Press the “Run All” button
5. Observe the test results
Expected result: The "RunningOnlyOnPlayer" test succeeds
Actual result: The "RunningOnlyOnPlayer" test is inactive
Reproducible with: 1.4.4, 2.0.1-pre.18 (2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b16)
Couldn’t test with: 1.3.9, 1.1.33 (Console errors)
Reproducible on: macOS Sonoma 14.4.1 (M1 Max)
Not reproducible on: No other environment tested
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
- Incorrect opacity blending occurs when parent opacity is applied
- "W" and "S" keys navigate ListView when in Player or Play Mode
- “Error in Shader Graph Assets/Samples/Shader Graph/17.1.0/Production Ready Shaders/Lit/URPLit.shadergraph: Graph is generating too many variants…” error is thrown after importing Shader Graph Samples
- ComputeShader cannot access the depth element of RenderTexture targeted by an HDR camera
- Search in the Console window highlights wrong text when text contains HTML attributes
Resolution Note (fix version 1.4.5):
Ensured that the results of tests that is ignored in the editor, but runs on a player, is not being overwritten with ignore when showed in the ui,