You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Thom!
I'm having the following test that uses MethodDataSource which points to a method that returns a tuple of the values I'm expecting as arguments.
Why is there suddenly a ValueTuple<string?> assumed by TUnit? Is there a hard limit for how many types TUnit supports?
By the way if I add further arguments to my test method and the data source they get then added to the ValueTuple.
Of course I could create an own type for the test data but still it would be great if this edge case could be either documented or a fix for it discovered.
Thank you so much Thom in case you get once again to a solution!
The text was updated successfully, but these errors were encountered:
Hi Thom!
I'm having the following test that uses
MethodDataSource
which points to a method that returns a tuple of the values I'm expecting as arguments.This leads to the following error (plus 3 additional ones for the generated test code from TUnit that basically tell the same thing):
Why is there suddenly a
ValueTuple<string?>
assumed by TUnit? Is there a hard limit for how many types TUnit supports?By the way if I add further arguments to my test method and the data source they get then added to the
ValueTuple
.Of course I could create an own type for the test data but still it would be great if this edge case could be either documented or a fix for it discovered.
Thank you so much Thom in case you get once again to a solution!
The text was updated successfully, but these errors were encountered: