You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a related note, these would be useful because auto formatting with fantomas can make the test labels less readable in some case by breaking the label onto a new line (and that is less likely when using an indentation based list):
test1 |@ "label 1"
.&. test2
|@ "label 2"
Last, would it make sense to expose ITestable for custom implementations?
Thanks for your help!
The text was updated successfully, but these errors were encountered:
rynoV
changed the title
No instances of class FsCheck.Testable+ITestable1[T] for type Microsoft.FSharp.Collections.FSharpList1[FsCheck.Property]
No instances of class FsCheck.Testable+ITestable\1[T] for type Microsoft.FSharp.Collections.FSharpList\1[FsCheck.Property]
Feb 23, 2024
rynoV
changed the title
No instances of class FsCheck.Testable+ITestable\1[T] for type Microsoft.FSharp.Collections.FSharpList\1[FsCheck.Property]
No instances of class FsCheck.Testable+ITestable1[T] for type Microsoft.FSharp.Collections.FSharpList1[FsCheck.Property]
Feb 23, 2024
F# constrains 'a to be a Property, when ideally it would be anything implementing ITestable, but I don't think there's any way to prevent this with the current API
I also generally wanted to move away from having to maintain API for combining properties in this way. Using a test runner/assertion library like xunit or nunit is the suggested way forward here.
At the time, I felt like maintaining the additional, and bespoke API surface in FsCheck was not really worth it. People seem to like being able to return bools as assertions and combining them. I've found in practice that assertions while a bit more verbose often give better error indications.
I was expecting lists and tuples to be testable based on these docs, but it seems they're not implemented yet:
FsCheck/src/FsCheck/Testable.fs
Line 190 in f1bd17a
On a related note, these would be useful because auto formatting with fantomas can make the test labels less readable in some case by breaking the label onto a new line (and that is less likely when using an indentation based list):
Last, would it make sense to expose
ITestable
for custom implementations?Thanks for your help!
The text was updated successfully, but these errors were encountered: