Closed leorodriguesrj closed 2 years ago
Never mind! I was using :meck
to mock lets say "ModuleA" on "ModuleBTest". It turns our that "ModuleBTest" was not calling :meck.unload
at the end. Then in some executions "ModuleATest", which should run against the actual "ModuleA", whould be executed right after "ModuleBTest", that left the mock behind. So in those circumstances, "ModuleATest" was running againt the mock of "ModuleA", leaving the actual module effectively without coverage.
For some reason, coveralls is leaving some of my source files out of scope. I mean, they don't show up on the final coverage listing. I can't fathom what I could be doing wrong.
PS: I use
:meck
to mock modules around.