Type and Member filtering for running specs

Add support for -filters for filtering down to specific types to run - similar to what the console runner for the .NET Framework has.

dotnet test --filters My.Spec.In.Namespace.MySpec, My.Spec.In.Namespace.MyOtherSpec

In addition, it would be really nice to have something to specify which member within a specification should be run.

dotnet test --specs My.Spec.In.Namespace.MySpec#Member, My.Spec.In.Namespace.MyOtherSpec#Member

This will be extremely helpful in the Visual Studio Code extension I’m working on. I plan to invoke the dotnet test tool directly.

[einari]

I’ve now implemented something. But please let me know if this is just wrong. I’ve been zipping through the Nunit and Xunit runners and they both implement -test and basically from what I can gather they both rely on unique testnames. The way I write my MSpec Specifications, there is no way to guarantee a unique name without including the entire namespace for the spec, because I don’t prefix or postfix the classname - or include in any way a reference to the unit being specified. So I figured that -test takes a comma separated list of fully qualified Namespace + class and an optional # and then the name of a specific assertion.

Anyways, PR sitting here: https://github.com/machine/dotnet-test-mspec/pull/6

[einari]

This vacation thing has really done my head in - obviously it should have been the ´-test / --test´ option:

this.Add("test=", "Comma-separated list of {NAMES} of tests to run or explore. This option may be repeated.",
                v => ((List<string>)TestList).AddRange(TestNameParser.Parse(RequiredValue(v, "--test"))));

I’ll dig into the format of what is being sent to these so that we match that.