Disable/Prevent XUnit Warnings on build in .NET Core Test Project

Question

I have a project with several large test cases in it and the project takes about 2-3 minutes to build. I am suspicious that it has to do with this new warnings feature... for example:

warning xUnit2003: Do not use Assert.Equal()
warning xUnit2004: Do not use Assert.Equal() to check for boolean conditions.

It is doing this for thousands of lines...

It would be great if there was a way to disable this feature. Not sure if it has to do with the visual studio runner or xunit itself.

How about fixing your unit tests and using `Assert.IsTrue` and `Assert.IsFalse` instead? — Tseng, Jun 14 '17 at 14:26
Technical debt has a way of calling in the loan. You need to fix the tests. The warnings are there for a reason. — Nkosi, Jun 14 '17 at 15:05

score 6 · Accepted Answer · answered Sep 19 '17 at 20:50

6

You could disable the warnings as follows:

for a file

#pragma warning disable xUnit2003, xUnit2004

optionally restore them:

#pragma warning restore xUnit2003, xUnit2004

Or in your project properties:

answered Sep 19 '17 at 20:50

Julian

33,915
22
119
174

no way to do this on the command line? :/ – john k Mar 12 '23 at 01:44
@johnk see: https://stackoverflow.com/questions/1023858/how-to-suppress-specific-msbuild-warning – Julian Mar 12 '23 at 04:09

Disable/Prevent XUnit Warnings on build in .NET Core Test Project

1 Answers1