Are these numbers generated by running all tests, eg unit, ui, browser, interactive .. ?
-Scott On Thu, Dec 31, 2009 at 9:07 PM, John Grabowski <j...@chromium.org> wrote: > I had an OKR to get code coverage working on 3 platforms for Chromium unit > test bundles in Q409. > If you're in PST, I made it! > Dashboard (overview): > http://build.chromium.org/buildbot/perf/dashboard/coverage.html > Sample output for > Windows: > http://build.chromium.org/buildbot/coverage/xp-debug/35420/CHROMIUM/index.html > Mac: http://build.chromium.org/buildbot/coverage/mac-debug/35422/CHROMIUM/index.html > Linux: http://build.chromium.org/buildbot/coverage/linux-debug/35422/CHROMIUM/index.html > Coverage is not perfect. For example, Mac coverage number generation is > smart enough to exclude *_win.cc and *_linux.cc but can't > tell base/file_version_info.cc and base/wmi_util.cc should be Windows-only. > This is a trade-off to prevent a complete exclusion of files without unit > tests at all. > Lots of thanks to Randall and Bradley. > jrg > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
