-
Notifications
You must be signed in to change notification settings - Fork 79
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
No output for successful test runs #533
Comments
Perhaps for your use case using one of the machine readable output formats might be the best? They do indeed output all the tests run. |
@gampleman I should've elaborated a lot more and mentioned that I've tried the For my case it would have been very convenient if the frontend simply hears about |
@techmindful I'm answering a little bit late but I think you might be interested in the setup that was done for the exercism platform: https://github.com/exercism/elm-test-runner This repo holds a docker containing a program composed of two pieces, (1) a setup for the elm-test-rs test runner to output a report in the exercism json format, and (2) a code snippet extractor, aimed at extracting the expectations from the test code. Both outputs are merged together to generate the final json in the exercism format with both the tests results and associated code snippets for test expectations. Of course the repo has limitations and some of the building blocks for the test extractor take advantages of the constraints imposed by the exercism setup, but nonetheless, I thought this might interest you. |
FYI I believe elm-test-rs 2.0.1 prints even successful tests when you pass the verbose |
elm-test
seems to only output test cases that failed, and omits the ones that succeeded. Sometimes the information on successful test cases is useful. For example, I'm implementing interactive coding on my webpage, and usingelm-test
on the backend to run the code. I would like to tell the user which test cases their code got right, on top of which ones they got wrong.The text was updated successfully, but these errors were encountered: