Uh oh!
There was an error while loading. Please reload this page.
coverage: translate info into WIP scripts - #46
Conversation
Some things still don't work though... I couldn't get gcov to work, and grep -o doesn't work with +/* in the regex for me
addaleax
commented
Dec 5, 2016
Just for reference, the original scripts are still available at https://github.com/addaleax/node-core-coverage |
mhdawson
commented
Dec 5, 2016
I can't quite decode your title "translate info into WIP scripts". You are trying to create scripts that can be run outside the build environment ? |
Fishrock123
commented
Dec 5, 2016
@mhdawson Yes but ideally both? Coverage is... a lot less useful unless you can also run it locally... |
Agreed, my goal is to get us to "make coverage" as the way to build/run coverage and @CurryKitten is working to pull more of the pieces needed for that into the core. I'll try to catch up with him to see how far away we are on that front. |
CurryKitten
commented
Dec 15, 2016
As @mhdawson mentioned, I'm working on some additional changes which will effectively give you a coverage result from running make so a developer will be able to see what impact a code change/fix/new test has on the overall coverage result. Next action is to add Javascript coverage into the build. |
Fishrock123
commented
Dec 23, 2016
@CurryKitten Is your work on a public repo somewhere? |
CurryKitten
commented
Jan 6, 2017
@Fishrock123 I'll push my code into my fork (https://github.com/CurryKitten/node) before I make a PR. Should have something ready next week, but I'll let you know |
Trott
commented
Sep 28, 2017
Now that we have |
gibfahn
commented
Sep 30, 2017
Seems like it, if not it can be reopened. |
Some things still don't work though...
I couldn't get gcov to work, and grep -o doesn't work with +/* in the
regex for me
cc @addaleax & @mhdawson