Feature request: valueExclude attribute on automatic theory generation

[bazarniy]

Hello!

Please look this example and you'll understand:

[Theory, CombinatorialData]
public async Task Should_Filter_By_Status([CombinatorialValuesExclusion(Status.Draft)] Status status)
{
...
}

So sometimes it is useful to use automatic theory generation and exclude some values, Something like this is pretty good to

[AArnott]

There are a few ways you can achieve this already:

• Within the test, skip the bad cases with Assert.SkipWhen(status == Status.Draft)
• List the CombinatorialValuesAttribute to list the ones you do want.
• Use a generating member that enumerates the ones you want, and skips the ones you don't.

[bazarniy]

Yes I can archieve this in this ways. But I'm asking about convinience.
The first way will generate test with status in the test list.
The second way - when you have 20 statuses in the enum it will be too long.
The last way - yes, no problem to do that, but generation code will be in the separate place and when somebody read test code he have to go into values generation code and understand that all this rows are about excluding one or to parameters.

So looks like it is more redable when I can see single exclusion in test heading

[AArnott]

I'm not convinced it's worth the extra cost not only to add the feature but to maintain it. But I'll keep this issue active to see if it gathers up-votes.

[AArnott]

#3 may help you here.