Search Issue Tracker
Active
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-120718
Regression
No
Parameterized Tests with ValueSource fail when supplied parameter is an System.Object
Steps to reproduce:
1. Open the attached project “ParameterizedTestBug.zip“
2. Open the Test Runner window (Window -> General -> Test Runner)
3. Select the button “PlayMode”
4. Scroll down to display the individual parameterized tests (Tests.dll -> BrokenTest -> Test -> Test(Brokentest+TestData)
5. Double click the first generated test
6. Observe the Console
7. Double click the second generated test
8. Observe the Console
9. Find the "Good" tests and run the second generated test
10. Observe the Console
Expected result: Double clicking a test runs the test that was clicked
Actual result: Double clicking the first faulty test runs all of the tests, while double clicking the second or third tests doesn’t run anything
Reproducible with: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment