Search Issue Tracker
Active
Under Consideration for 1.4.X
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
Add comment