Add support for generating test-suite. #5761
Merged
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.
Overview
Support generating a
test-suite
for libraries fromcabal init
.Partially addresses #5705.
Changes
Two new flags:
--tests :: Bool
--test-dir :: [String]
(same behaviour assrcDirs
)Interactive Prompt Behaviour
You will only get asked about generating a test suite if it is a Library or LibraryAndExecutable. The rationale for this is because testing modules that are only part of an executable is more complicated to set up then just depending on the library.
If you select "no" for generating a test suite, you won't be asked for the test directory.
Example Invocation
initsample.cabal
TODO
MyLib.hs
oncecabal init
improvements: application-dir and creating library hs file #5740 is mergedPlease include the following checklist in your PR:
[ci skip]
is used to avoid triggering the build bots.Please also shortly describe how you tested your change. Bonus points for added tests!