As a developer, when using a module loader failed tests are not being reported correctly.
IngwiePhoenix opened this issue · 4 comments
Basically, I want them.
Since I use karma-webpack in order to roll my tests through my WebPack config, I urgently need to be able to see backtraces. Because of some preprocessors, lines have an offset, or I get to see the wrong file entirely! But the backtrace itself would solve many, many problems.
That files arent displayed correctly is a karma-webpack thing, fo' sho'. But having no idea where an error is coming from is problematic.
How can I get them?
Are you not getting any type of reporting at all? Can you post your karma.config.js please?
Unfortunately, I've never used a webpack before. karma-spec-reporter is a reporter, not a preprocessor. Maybe the preprocessor is altering the stacktrace somehow before it makes it to the reporter?
Any type of information, examples, console output, or further explanations would help a lot! We might need to collaborate to help get this working, I completely understand the need for a solid stacktrace!
@IngwiePhoenix have you tried bumping the version that is used in karma-webpack to the latest release? It looks like they are a few versions behind. Let me know if that works!!
@IngwiePhoenix please verify that with the latest karma that you are still not seeing reporting, this was actually a recent defect that was just fixed: karma-runner/karma#1894
Closing since no one else has verified that this is still an issue. I'll re-open if that's not the case.