Workaround for ReSharper regarding `ShouldNotBeNull()`

Please take a look at this code:

var car = new Car();
Assert.IsNotNull(car);
Assert.IsTrue(car.HasEngine);

When using ReSharper, it works perfectly fine without any complaints. Now I “translate” the code into…

var car = new Car();
car.ShouldNotBeNull();
car.HasEngine.Should().BeTrue();

… which makes ReSharper complaining about the last line saying that car can be null.

There is a ReSharper issue regarding this topic as well: Extend support for FluentAssert

Do you see any lightweight workaround that can be included in FluentAssertions without polluting the code base with a dependency to a third-party tool?

[dennisdoomen]

That’s isn’t really helping either. But I’ve just reached out to Jetbrains to ask them if there is a better way.

[Evangelink]

I don’t think null pointer warnings in unit tests are such a big deal because it is still caught before any prod.

At the same time, and I might be wrong with it, but I would favor having some False Negatives instead of False Positives here. Most people are probably using the simple scenario and would prefer not to have a FP message from ReSharper. For more advanced users, who will wrap assertions in the AssertionScope they would end up with a False Negative (no message from ReSharper).

just my 2 cents