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

Improve the way test output is handled #216

Open
erikd opened this issue Apr 11, 2018 · 2 comments
Open

Improve the way test output is handled #216

erikd opened this issue Apr 11, 2018 · 2 comments
Assignees
Labels

Comments

@erikd
Copy link
Contributor

erikd commented Apr 11, 2018

Been using stack a little for work and comparing how it does things in comparison to mafia.

One of the nice things stack test is show the fully colourized and on-the-fly Hedgehog test output whereas mafia just prints it out the whole test output chunk once the test is complete.

The stack way is simply nicer and couldn't be too hard to do.

@erikd erikd added the wishlist label Apr 11, 2018
@erikd erikd self-assigned this Apr 11, 2018
@jacobstanley
Copy link
Contributor

The main issue here is that mafia test just calls cabal test which disconnects the tty, so hedgehog thinks that it's being piped to a file on disk.

To fix this without fixing it in cabal, we'd just have to read the test suites from the .cabal file and execute them manually. I believe mafia already depends on the Cabal library so parsing the .cabal file shouldn't be a big deal.

@erikd
Copy link
Contributor Author

erikd commented Apr 11, 2018

My first step was going to be to trawl through the stack code to figure out how it does it, but your suggestion sounds plausible.

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

No branches or pull requests

2 participants