Search Issue Tracker

Won't Fix

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

  1. Resolution Note:

    Due to limited resources this issue was deemed to be low priority and will be closed as won’t fix. If you do not agree with this priority assessment, please reopen the bug and we will reevaluate it.

    As a workaround, you can wrap System.Object into a class. This will also allow you to override ToString() method to give the test parameter a sensible name.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.