leancheck VS smallcheck

Compare leancheck vs smallcheck and see what are their differences.

Our great sponsors
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • Scout APM - Less time debugging, more time building
  • JetBrains - Developer Ecosystem Survey 2022
leancheck smallcheck
0 1
39 125
- -
3.9 2.9
7 months ago about 1 month ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

leancheck

Posts with mentions or reviews of leancheck. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning leancheck yet.
Tracking mentions began in Dec 2020.

smallcheck

Posts with mentions or reviews of smallcheck. We have used some of these posts to build our list of alternatives and similar projects.
  • Property-based testing #1: What is it anyway?
    1 project | dev.to | 9 Jun 2022
    Another strategy is exhaustive generation. There, all possible values for some type are generated in some well-defined order - typically from "small" to "large" values, and with some upper bound, as once you go past booleans the number of values for most types are (countably) infinite. For example, trying all the integers between -20 and 20 in "zig zag" order 0,1,-1,2,-2,.... SmallCheck for Haskell and SciFe for Scala do this, but this approach is not so well-known. It's a shame as random and exhaustive generation are complementary - if you think of generating values as exploring some large space to find failing tests, random generation is a serendipitous type of exploration, while exhaustive generation is diligently mapping out all the paths in some area.

What are some alternatives?

When comparing leancheck and smallcheck you can also consider the following projects:

hedgehog - Release with confidence, state-of-the-art property testing for Haskell.

genvalidity - Validity and validity-based testing

smallcheck-series - Orphan Series/CoSeries instances for common types

titan - Testing Infrastructure for Temporal AbstractioNs

smallcheck-laws - Property testing for common type classes

silvi - Haskell library for generating fake data.

test-fixture - Testing with monadic side-effects

tasty-groundhog-converters - Testing Harness for groundhog and groundhog converters.

chuchu

ghc-prof-flamegraph

HTF - Haskell Test Framework

HUnit-Plus - A test framework expanding on the HUnit Haskell testing package