-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Storage] Fixing code coverage for the browser tests #6666
[Storage] Fixing code coverage for the browser tests #6666
Conversation
…to FixCodeCoverageBrowser
It would be nice to add into the description summary of the issue and fix |
I was just adding some :P |
It would've been filled if you have some words in the first commit! |
If the approach and the report look good, I'll extend this to the rest of the SDKs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
Code Coverage for Browser Tests
Problem
Code coverage for browser tests is broken.
Investigation
karma plugins
karma-coverage
is supposed to generate a report showing the code covered while testing(for the file
dist-test/index.browser.js
). This works properly.karma-remap-coverage
is supposed to remap the above coverage and show the code covered in the src files using the sourceMappings. This is broken, the report shown is blank.Looks like the package(karma-remap-coverage) has not been responding to the issues in github and is deprecated too - karma-remap-coverage
After failed many attempts at fixing it, finally gave up and started looking for alternatives to karma-remap-coverage.. came across karma-remap-istanbul
Tried that instead of karma-remap-coverage(updated karma.conf appropriately), I could generate a report like following.
Fixes #2937