|about 1 month ago||2 days ago|
|MIT License||MIT License|
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.
HSpec, Tasty, sydtest, Hunit, ... -> what do you use for writing Haskell tests?
2 projects | /r/haskell | 15 Jan 2023
doctest for testing examples in the documentation. Docs are much clearer when they contain usage examples and doctest helps them keep up to date.
Why is the debugger so bad in Haskell? (or is it just me)
3 projects | /r/haskell | 19 Oct 2021
Try to restrict your types even on sub functions (inside where), use testing, break down your code to the most atomic parts, using ghci to debug each part once at a time, and because Haskell doesn't let you reuse variables, or mutate state, it's a lot easier to rationalize evaluation order (which makes it a lot easier to debug without step debuggers compared to languages like python).
We haven't tracked posts mentioning tasty yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
hspec - A Testing Framework for Haskell
tasty-hspec - Hspec provider for tasty
hedgehog - Release with confidence, state-of-the-art property testing for Haskell.
HUnit - A unit testing framework for Haskell
quickspec - Equational laws for free
smartcheck - A Smarter QuickCheck
genvalidity - Validity and validity-based testing
tasty-th - Automatically generate tasty test groups from functions in a module using TH
http-test - Tests for HTTP APIs
tasty-ant-xml - A tasty ingredient to output test results in XML, using the Ant schema. This XML can be consumed by the Jenkins continuous integration framework.
tasty-expected-failure - Mark test cases as expected-failure