Set up hspec for unit testing #54
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robinheghan
approved these changes
May 1, 2022
Comment on lines
+4
to
+6
| - build: `cabal build -f dev` | ||
| - run tests: `cabal test -f dev` | ||
| - format files: `find -name '*.hs' | xargs -t ormolu -m inplace` |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Run tests with
cabal test -f dev.This approach uses the "common" stanzas feature of cabal to add the source files of the exe to the test-suite module. This means that if you build and then test, the changed files will get compiled twice (once for exe, and one for tests), but imo this way is better than the alternative, which requires that you put all your hs files into a lib module where all files are publicly exposed, and have exe and tests both depend on lib.