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
I'm not sure how to do this, but in Cats right now when a property fails you see the generated input (good) but then just a gigantic stack trace.
When we set this up in Algebra, the ?== operator was designed to use ScalaCheck's labels so that you could "see" the values being compared when there was a failure. I'm not sure why that isn't working here.
Anyway, this isn't critically-important, but since many folks will be discovering law-checking through Cats, it would be good to have a better experience here.
The text was updated successfully, but these errors were encountered:
I made an override to our List instance's map method to always return Nil, and I see a helpful label of the two values being compared just after the generated input:
I think that this was improved by #2052. I'm going to go ahead and close this out. @non feel free to reopen if you think that there are still improvements that could be made here.
I'm not sure how to do this, but in Cats right now when a property fails you see the generated input (good) but then just a gigantic stack trace.
When we set this up in Algebra, the
?==
operator was designed to use ScalaCheck's labels so that you could "see" the values being compared when there was a failure. I'm not sure why that isn't working here.Anyway, this isn't critically-important, but since many folks will be discovering law-checking through Cats, it would be good to have a better experience here.
The text was updated successfully, but these errors were encountered: