Update code coverage documentation on chromium.org |
|||
Issue descriptionThanks Hans for pointing that out: https://www.chromium.org/developers/code-coverage Assuming that current content on that page is obsolete, we may put something like: "Please follow the instructions from https://cs.chromium.org/chromium/src/tools/code_coverage/coverage.py" to that page in the mean time? How does it sound? Later, we can add more details.
,
Mar 14 2018
I think it's better to remove that page completely and add a docs/clang_code_coverage.md
,
Mar 14 2018
I created a CL weeks ago, but forgot to send it out for review, WDYT? https://chromium-review.googlesource.com/c/chromium/src/+/952296/2/docs/clang_code_coverage.md
,
Mar 14 2018
That's great, I'll review it in a bit! Let's then replace that page with a link to docs/clang_code_coverage.md. I don't want to remove the page completely, as it appears to be the first Google Search result :)
,
Mar 14 2018
that's a good point! I'll also talk to Dirk to ask what's our general strategy regarding obsolete pages.
,
Mar 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d3b46273e30e56f055b20cec785974e7aa150000 commit d3b46273e30e56f055b20cec785974e7aa150000 Author: Yuke Liao <liaoyuke@chromium.org> Date: Wed Mar 14 18:25:14 2018 [Coverage] Add documentation for Clang source based code coverage. Change-Id: I6c3920ca92cf05b41fe69c74936cc0578841847f Bug: chromium:821851 Change-Id: I6c3920ca92cf05b41fe69c74936cc0578841847f Reviewed-on: https://chromium-review.googlesource.com/952296 Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Reviewed-by: Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#543125} [add] https://crrev.com/d3b46273e30e56f055b20cec785974e7aa150000/docs/code_coverage.md [modify] https://crrev.com/d3b46273e30e56f055b20cec785974e7aa150000/tools/code_coverage/coverage.py
,
Mar 14 2018
Updated chromium.org: https://sites.google.com/a/chromium.org/dev/developers/code-coverage
,
Mar 14 2018
Woohoo! Thanks Yuke! |
|||
►
Sign in to add a comment |
|||
Comment 1 by mmoroz@chromium.org
, Mar 14 2018