We can do this. The priority is hooking up windows coverage; Randall finished his end (weeks ago) and I've mostly finished mine but I haven't hooked things up yet. Next is tracking down the "add more unit tests and coverage goes down" problem reported by the media guys.
Once we're hooked up and correct we can spend some time on UI. jrg On Fri, Jul 17, 2009 at 10:20 AM, Scott Violet <[email protected]> wrote: > > Thanks! > > Personally I think the overall numbers are the most important, rather > than what they are for a build. Any reason we don't drop you into the > subdirectory view from the get go? > > -Scott > > On Fri, Jul 17, 2009 at 9:37 AM, Nicolas Sylvain<[email protected]> > wrote: > > > > > > On Fri, Jul 17, 2009 at 8:39 AM, Scott Violet <[email protected]> wrote: > >> > >> I'm interested in seeing code coverage. We have a code coverage page > >> (http://build.chromium.org/buildbot/perf/dashboard/coverage.html), but > >> I can't make heads or tails of this. Is there a page that shows > >> coverage per file, so that we know what areas to add tests for? > > > > I agree that this is not easy to find. Click on the "view coverage" link > > on the coverage bot on the experimental (FYI) waterfall. > > It brings you to the detailed result for a given build. > > > http://build.chromium.org/buildbot/coverage/linux-debug/20957/CHROMIUM/index.html > > Nicolas > > > >> > >> Thanks, > >> > >> -Scott > >> > >> >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
