question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect format for TestCaseFilter Error: Invalid Condition - Using = in SetName

See original GitHub issue

NUnit

  • 3.12.0

NUnit3TestAdapter

  • 3.16.1

Visual Studio

  • Professional 2019
  • Version 16.4.3

Project under test

  • Console Application
  • .NET Core 3.1

Project performing tests

  • .NET Core 3.1

Application to repo

When using TestCaseData and SetName. Putting an = in the test causes error in Test Output. This also causes all other tests to not be run using Test Explorer in Visual Studio.

Example: yield return new TestCaseData("Input B").SetName("Unit To Test Input B = itself");

Full Error Message

An exception occurred while invoking executor ‘executor://nunit3testexecutor/’: Incorrect format for TestCaseFilter Error: Invalid Condition ‘FullyQualifiedName=UnitTests.Tests.Unit To Test Input B = itself’. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.

This occurs in other framework setups as well but the repo project attached is using the versions listed above.

This looks like it could be similar to #549

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
maks-bondarenkocommented, May 20, 2020

same issue, any updates?

1reaction
smildenbergercommented, Jun 3, 2021

I just noticed the same issue with == or != being in SetName(). I could run the individual tests but if they were included in a set of tests to run then no tests were run. Test Adapter 3.17.0 in VS 2019 16.9.5

Read more comments on GitHub >

github_iconTop Results From Across the Web

Not Contains TestCase filter not working in VSTest 16.6.1
I got error, Incorrect format for TestCaseFilter Error: Invalid Condition 'FullyQualifiedName!~Integration'. on my build server.
Read more >
Incorrect format for TestCaseFilter Error: Invalid Condition
An exception occurred while invoking executor 'executor://nunit3testexecutor/': Incorrect format for TestCaseFilter Error: Invalid Condition ' ...
Read more >
Unable to run tests: Incorrect format for TestCaseFilter Error
Creating an xunit theory test with the following format appears to break Visual Studio test hierarchy such that tests cannot be executed.
Read more >
.NET NUnit Parallel Tests: Incorrect format for TestCaseFilter ...
I'm using the . NET runner with the test command pointed at the csproj of one of our test projects, no coverage.
Read more >
Adapter V3 Release Notes
640 Allow use of FullName as the DisplayName for Converted Tests ... Incorrect format for TestCaseFilter Error: Missing ')'; 549 Invalid ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found