Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run All Tests not working in VS #1259

Closed
mateoatr opened this issue Jun 9, 2020 · 5 comments · Fixed by #1628
Closed

Run All Tests not working in VS #1259

mateoatr opened this issue Jun 9, 2020 · 5 comments · Fixed by #1628
Assignees

Comments

@mateoatr
Copy link
Contributor

mateoatr commented Jun 9, 2020

Running all tests from Visual Studio isn't working. NUnit stops with the following message:
An exception occurred while invoking executor 'executor://nunit3testexecutor/': Incorrect format for TestCaseFilter Error: Missing '('. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed. It seems that this is an issue within the communication between NUnit and VS (see https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue691/Issue691). Started failing after 0e38c61.

@marek-safar
Copy link
Contributor

@sbomer thoughts on this?

@sbomer
Copy link
Member

sbomer commented Jun 9, 2020

I don't think we can do much here other than work around it, either by using dotnet test or by disabling the problematic tests. I can look into which ones would need to be disabled.

@sbomer sbomer self-assigned this Jun 9, 2020
@sbomer
Copy link
Member

sbomer commented Jun 9, 2020

It seems like most of the signatures (any that include '(' or '#' for example) trigger the bug, so I don't think we want to work around it by disabling tests. For now I suggest using dotnet test to run all. It looks like test groups under a project (or individual tests) can still be run from VS.

If nunit/nunit3-vs-adapter#691 isn't fixed soon, I can spend some more time looking for other workarounds, but it would take some understanding of how nunit communicates with VS. It's possible that the testcase data is being filtered using its ToString(), in which case there might be a workaround like defining a different ToString on the test data types.

@marek-safar
Copy link
Contributor

Can this be closed?

@sbomer
Copy link
Member

sbomer commented Nov 13, 2020

It might be worth trying the workaround suggested in nunit/nunit3-vs-adapter#691 (comment). I'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants