You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when you run lein modules test, the result summaries are printed after each modules' tests, which means you have to scroll through the output to find them. This gets tedious to do in large projects with lots of submodules. It would be great to have all of the test result summaries printed again at the very end of the test run, so you can tell at a glance what failed and in which modules. So, I imagine the end of the test output would look something like:
... many lines of test output ...
Module mod.foo: Ran 4 tests containing 10 assertions.
0 failures, 0 errors.
Module mod.bar: Ran 9 tests containing 34 assertions.
4 failures, 0 errors.
Module mod.baz: Ran 5 tests containing 28 assertions.
0 failures, 0 errors.
I would be happy to make a PR for this, just let me know if you have any pointers about how it should be done!
The text was updated successfully, but these errors were encountered:
Hi Morgan! I would be equally happy to accept a PR for this. :)
I haven't inhabited that code in a while, and IIRC it's fairly complex and brittle due to Leiningen itself. Do you have an approach in mind already?
I don't have an approach in mind yet, I would need to study the test runner code first. I'll post an update here when I have an idea of what needs to be done
Currently, when you run
lein modules test
, the result summaries are printed after each modules' tests, which means you have to scroll through the output to find them. This gets tedious to do in large projects with lots of submodules. It would be great to have all of the test result summaries printed again at the very end of the test run, so you can tell at a glance what failed and in which modules. So, I imagine the end of the test output would look something like:I would be happy to make a PR for this, just let me know if you have any pointers about how it should be done!
The text was updated successfully, but these errors were encountered: