Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a test suite entry #396

Open
ndmitchell opened this issue Oct 22, 2017 · 1 comment · May be fixed by #1614
Open

Add a test suite entry #396

ndmitchell opened this issue Oct 22, 2017 · 1 comment · May be fixed by #1614

Comments

@ndmitchell
Copy link
Owner

As noted by @contivero, stack test should do a test. Probably just add an extra Test.hs which calls the existing test suite.

@hseg hseg mentioned this issue Sep 4, 2024
@hseg
Copy link
Contributor

hseg commented Sep 4, 2024

Started working on this, am puzzled by some of the code structure.
For example, judging by its imports, the module Language.Haskell.HLint seems to mainly serve to reexport HLint.hlint, as well as serving as a kitchensink export for interactive use?

@hseg hseg linked a pull request Sep 4, 2024 that will close this issue
hseg added a commit to hseg/hlint that referenced this issue Sep 4, 2024
We probably want to be more clever and replace the `--test` invocation
with a `detailed-0.9` testsuite. We probably also should integrate the
QuickCheck tests into the testsuite.
That would take a deeper reorganization than I'm willing to commit to
now, though, so I'll leave it for another day.

Closes: ndmitchell#396
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants