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.

xUnit analyzer emits errors on Property tests

See original GitHub issue

https://github.com/xunit/xunit/issues/2748

so every method which returns Property causes analyzer to emit error.

Issue Analytics

State:
Created 2 months ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

ploehcommented, Jul 10, 2023

OK, comment added: https://github.com/xunit/xunit/issues/2748#issuecomment-1629408107

Please consider joining the discussion.

0reactions

voroninpcommented, Jul 10, 2023

I am not very familiar with xUnit architecture, but currently it looks like FsCheck can do nothing.

IMO, the set of allowed types should be defined by TestCaseDiscovererAttribute.

Maybe it’s indeed worth that you commen in the original issue.

Top Results From Across the Web

Change of supported return types when upgrading from 2.4 ...

We now receive this build error: error xUnit1028: Test methods must ... xUnit analyzer emits errors on Property tests fscheck/FsCheck#636.

Properties throw off xUnit and the Test Explorer

It appears that test discovery fails silently if binding redirects are not set properly. This just cost me about 3 hours, so I...

Testing Source Generators, Analyzers & Code Fixes - Part 3

The other kind of test verifies the emitted errors and warnings, and the generated code, not just the one produced by the Source...

dotnet test command - .NET CLI

The dotnet test command is used to execute unit tests in a given project. ... the CLI will emit a warning (an error...

Rules

ID Title Severity Category xUnit1000 Test classes must be public Error Usage xUnit1001 Fact methods cannot have parameters Error Usage xUnit1003 Theory methods must have test...