HUnit-Plus
A test framework expanding on the HUnit Haskell testing package (by emc2)
DocTest
An implementation of Python's doctest for Haskell (by sol)
Our great sponsors
| HUnit-Plus | DocTest | |
|---|---|---|
| - | 3 | |
| 1 | 369 | |
| - | - | |
| 0.0 | 5.4 | |
| 5 months ago | 6 months ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | MIT 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.
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.
HUnit-Plus
Posts with mentions or reviews of HUnit-Plus.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning HUnit-Plus yet.
Tracking mentions began in Dec 2020.
DocTest
Posts with mentions or reviews of DocTest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-15.
-
HSpec, Tasty, sydtest, Hunit, ... -> what do you use for writing Haskell tests?
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)
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).
What are some alternatives?
When comparing HUnit-Plus and DocTest you can also consider the following projects:
hspec - A Testing Framework for Haskell
tasty - Modern and extensible testing framework for Haskell
hspec-expectations - Catchy combinators for HUnit
quicktest
http-test - Tests for HTTP APIs
fitspec - refine properties for testing Haskell programs
bdd - A domain-specific language for testing programs using Behavior-Driven Development (BDD) process in Haskell
test-fixture - Testing with monadic side-effects
testing-feat - FEAT
http-mock - HTTP mocking and expectations library for Haskell
smartcheck - A Smarter QuickCheck
hspec-wai - Helpers to test WAI applications with Hspec