FsCheck icon indicating copy to clipboard operation
FsCheck copied to clipboard

Random Testing for .NET

Results 36 FsCheck issues
Sort by recently updated
recently updated
newest added

Try this: ``` csharp [FsCheck.NUnit.Property] public void TestSuccess(int x) { Assert.Pass(); } ``` The test should have passed but instead fails. I am using version 3.0.0-beta2.

bug
help wanted
good first issue

[`Seq.pick`](https://fsharp.github.io/fsharp-core-docs/reference/fsharp-collections-seqmodule.html#pick) is a very useful function that applies a given "chooser" function to successive elements, returning the first `x` where the function returns `Some x`. By analogy, I think FsCheck...

If you create a new .NET 4.8 test project and reference - FsCheck.3.0.0-rc3 - FsCheck.Xunit.3.0.0-rc3 - xunit.2.7.0 - Other xUnit dependencies in 2.7.0 version then the FsCheck `[]` test fails...

![image](https://github.com/fscheck/FsCheck/assets/8892111/a21eef82-88bc-42fa-9bd3-8111e618ab59) ![image](https://github.com/fscheck/FsCheck/assets/8892111/00d13523-dc48-4ea1-ae82-8b533117c08d) ![image](https://github.com/fscheck/FsCheck/assets/8892111/81fae29b-2936-4889-bb60-952418d5f891) ![image](https://github.com/fscheck/FsCheck/assets/8892111/fdac2b74-d3c2-4c70-a3f9-3a5016dc46e2) ![image](https://github.com/fscheck/FsCheck/assets/8892111/9695e376-7103-49aa-a174-e5a078011d8a) ![image](https://github.com/fscheck/FsCheck/assets/8892111/437f3f5c-bf00-4679-b196-0e580f5301ce) ![image](https://github.com/fscheck/FsCheck/assets/8892111/b7efe2c5-9c43-4d15-a7a1-02ea6fd5795e) These have been flagged by synk, not sure if they are fixable, but they are problematic and serious issues.

The behavior added in #634 to address #633 feels confusing to me when contrasted with the behavior of tests that return `Task`, especially for xUnit/NUnit tests annotated with `PropertyAttribute`. That...

Methods which uses `FsCheck.Xunit.PropertyAttribute`, throws `MissingMethodException` in xUnit version 2.9 when having `ITestOutputHelper` as a ctor dependency. Removing the ctor seems to solve the problem. This error is not present...