Add "!~" operator to test filter

[livarcocc]

From @mano-cz on October 10, 2018 8:12

Steps to reproduce

run "dotnet test Some.csproj --filter FullyQualifiedName!~Some.Namespace"

Expected behavior

Not contain operator will work.

Actual behavior

Not contain operator is not implemented yet.

Use case

Parallelization of test execution according to namespaces e.g.:
#1 thread - filter on few namespaces
#2 thread - filter on other few namespaces
#3 thread - filter on remaining (dynamic) namespaces (with usage of !~ operator on namespaces from previewous threads)

Copied from original issue: dotnet/cli#10149

[mayankbansal018]

@mano-cz, we don't support similar to(~) operator, with not(!), however we support similar(~). For more queries related to filters please go through https://github.com/Microsoft/vstest-docs/blob/master/docs/filter.md

However if you exact ask is !~, that would be an enhancement on our part

[hgran]

I’d like to have a go at this if that’s ok?

[hgran]

Issue #1385 describes the same functionality.

[baruchiro]

How can I know if my dotnet vstest supports this?

$: dotnet vstest

--TestCaseFilter|/TestCaseFilter:<Expression>
      Run tests that match the given expression.
      <Expression> is of the format <property>Operator<value>[|&<Expression>]
         where Operator is one of =, != or ~  (Operator ~ has 'contains'
         semantics and is applicable for string properties like DisplayName).
         Parenthesis () can be used to group sub-expressions.
      Examples: /TestCaseFilter:"Priority=1"
                /TestCaseFilter:"(FullyQualifiedName~Nightly
                                  |Name=MyTestMethod)"

And how can I get this change?

[baruchiro]

Sorry, my problem was unupgraded Microsoft.sdk.Test nuget.