Tooling for Haskells
Haskell tooling is the set of programs used to build, test and manage projects. GHC compiles code, Cabal and Stack resolve dependencies from Hackage or Stackage, GHCup installs toolchains, and test libraries such as HUnit, Hspec and QuickCheck check behaviour. Good tooling habits make a project reproducible.
Stage: Ecosystem · Part of the Haskell roadmap · Last reviewed 19 November 2026
What to learn in Tooling
- Install a toolchain with GHCup and create a project with Cabal
- Add a dependency in the .cabal file and build the project
- Write unit tests with Hspec and run them from the build tool
- Write a QuickCheck property and read a shrunk counterexample
- Run the Haskell Language Server in an editor for feedback
Tooling interview questions
What is the difference between Cabal and Stack?
Cabal is the standard build tool and package manager that solves dependency versions from Hackage. Stack uses curated Stackage snapshots so that a set of package versions is known to build together. Both use .cabal files and both work with GHC.
What is property-based testing with QuickCheck?
Instead of fixed examples, you state a property that should hold for all inputs, such as reversing a list twice returns the original. QuickCheck generates many random inputs, and when one fails it shrinks it to a small counterexample.
Where Tooling fits in the Haskell roadmap
Tooling belongs to the Ecosystem stage (advanced level). Real projects.
Other units in this stage
Back to the full Haskell roadmap