-
Notifications
You must be signed in to change notification settings - Fork 91
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
MUnit only reporting a handful of test results #138
Comments
Some additional information: I get different results when running my suites in SBT and Bloop. In Bloop, it reports from at least one test in each suite, but skips many of the others, and in SBT it only reports the last several.
|
Thank you for reporting! Do you get different output if you enable/disable forking? Do the tests have conflicting names? Have you tried to minimize the issue into something you can share publicly? |
What is the output if you run the tests with |
If I enable
It almost looks like it might have something to do with the names of the tests. In the |
Ok, new update: I prefixed all my tests with the # they are in the current file (first test is prefixed with Full output:
To reproduce the issue it seems that if you have tests with names similar to mine (minus the number prefixes) it would happen again. Seems like it cuts out the test name after |
Thanks for the details! I'm able to reproduce, opened #140 which fixes the issue. |
Triggered a v0.7.8 release with the fix |
good one :-) |
I have converted my test suites from ScalaTest to MUnit, and for some reason MUnit only appears to be reporting a subset of my expected test results. At first I only had a single test suite, in a large file of several hundred lines, and it was reporting only 3 results. I have since moved my tests into several, smaller suites, and now it only reports results from the very last suite.
Here is some sample output, from SBT:
As you can see, the first 4 suites look almost as if they are being skipped over, but the final suite is the only one that appears to get ran at all.
The tests for all of the above suites have the following in common:
ScalaCheckSuite
with some custom configuration and common functions (some scalacheck generators, HTTP4S DSLs and implicits, mainly)property
functionThe code in question is on a private repository. If it helps to resolve the issue, I can grant temporary access to the repository to a project maintainer for MUnit (it's a personal project anyway). I can also share more specific code samples as needed, but the tests are pretty deeply tied into my domain logic so I can only share so much at a time.
EDIT: Some additional details:
The text was updated successfully, but these errors were encountered: