Add end-to-end tests in standalone .inferno files #80
Conversation
This file contains 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
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.
This PR uses https://hackage.haskell.org/package/HTF-0.15.0.0 to implement end-to-end tests for inferno. This way we can have
.infernofiles containing inferno programs withassertstatements to test things, and will hopefully help new users and documentation/learning material generation. (@smurphy8 hope this is what you were thinking of?)@ngua I've made it look for the path to the
infernoexe in the env varINFERNO_EXE. Could you help modify the nix build magic to set the var accordingly? Thanks