Open th3coop opened 7 years ago
Please share an stdout of a test you ran that showed this problem. The shorter the stdout the better.
I did. It's in the original report.
I need the complete stdout, not part of it. When I say shorter the better I mean ideally from a reproduction case with as little output as possible, do not truncate the output.
Do you not see this when you run the code intel unit tests in Komodo? I don't think setting up a new test suite of custom tests is a good use of time right now to be frank. I can paste the stdout from Komodo after running the test suite if that would help.
@Naatan, I updated the output to show what Komodo outputs in stdout. I ran the tests by class to get a little output as possible. Unfortunately this doesn't reproduce the issue. It looks like only running the entire test suite causes this issue.
Running the test suite again to confirm.
Short Summary
While reporting https://github.com/Komodo/KomodoEdit/issues/2642 I realized that a LOT of the tests aren't being reported as passed where the summary numbers are displayed beside the test class that was run.
For example, running
TestJavaScriptLegacyCompletions
alone in the Komodo UI looks like this:But Komodo says none passed. See the screenshot below.
Some times tests DO show that things passed though: