Search Issue Tracker
Won't Fix
Won't Fix in 1.1.X
Votes
0
Found in [Package]
1.1.33
Issue ID
DSTR-653
Regression
No
Tests do not load when TestFixtureSource returns multiple items
How to reproduce:
1. Open the attached “UnitTestFailure” project
2. Select “Window“ → “General” → “Test Runner” in the main menu bar
3. Select “TestsSuite” (expand “UnitTestFailure” and “Tests.dll” in case they are collapsed)
Expected result: Tests load successfully with no errors
Actual result: Trying to load the tests raises a System.ArgumentNullException exception
Reproducible with: 1.1.33 (2020.3.39f1, 2021.3.10f1, 2022.1.16f1, 2022.2.0b9, 2023.1.0a12)
Reproducible on: Windows 10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (1.1.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.