-
During test runs I'd also like to have code coverage run, so that results of addons like Coverage Gutters are up-to-date. Is that possible somehow or would it be a feature request? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Karma test explorer primarily integrates with Karma as a reporter, while disabling the reporters that are setup in the project's But basically, that behavior means that any code coverage tool that functions as a Karma reporter will not currently work with Karma Test Explorer. Also, Karma Test Explorer did not always take the approach of making itself the sole reporter enabled in the modified Karma setup, but there were cases where other reporters interfered with its functioning, one example being the BrowserStack reporter. This line is where the reporters confgured in const reporters = Array.isArray(config.reporters) ? config.reporters : [];
- reporters.splice(0, reporters.length, reporterName);
+ reporters.push(reporterName);
config.reporters = reporters; |
Beta Was this translation helpful? Give feedback.
Karma test explorer primarily integrates with Karma as a reporter, while disabling the reporters that are setup in the project's
karma.conf
file. The rationale is that Karma Test Explorer's visual reporting of the tests is the only reporting that's relevant in the VS Code context, and disabling the other reporters in the project's karma config avoids the performance cost of running them, especially given that they are usually redundant in the VS Code context. The code coverage case here is perhaps one example where the other reporter is not redundant.But basically, that behavior means that any code coverage tool that functions as a Karma reporter will not currently work with Karma Test E…