Support mapping JS coverage to source file via source maps |
|
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Run coverage over code with source-maps enabled 2. View coverage details over the file What is the expected behavior? Would love to see some view over the source file mapped from the coverage info + source map What went wrong? Just saw JS coverage info Did this work before? No Chrome version: 64.0.3282.186 Channel: stable OS Version: OS X 10.13.3 Flash Version: I realize it may be unrealistic to do this reliably – but wanted to make sure.
,
Dec 15
I agree I would also like an option for coverage to be mapped back to the original source everywhere if the sourcemap exists. My requested features: 1) Displaying coverage in the gutter on the original source files in the source view (I think this already happens in Chrome 71) 2) The coverage panel should show the original files, not the JS files (or CSS) if they were compiled from another language. 3) The coverage export should be mapped to the original filenames and ranges. 4) Ability to get sourcemapped coverage from the chrome remote debugging protocol for integration with puppeteer or other tools |
|
►
Sign in to add a comment |
|
Comment 1 by caseq@chromium.org
, Mar 5 2018Status: Assigned (was: Unconfirmed)