You are correct; I am not running layout tests on the coverage bots.
 Definitely something else to work on.

jrg

On Mon, Jan 4, 2010 at 3:46 PM, Erik Kay <[email protected]> wrote:

> Good to see this.
>
> I don't see a reference to layout tests.  Given that webkit is listed at 9%
> coverage, I'd guess that these aren't running either.
>
> Erik
>
> On Mon, Jan 4, 2010 at 10:00 AM, John Grabowski <[email protected]> wrote:
>
>> At this time, just the tests which run successfully on all 3 platforms.
>>  The list from chrome_tests.gypi:
>>
>>             'automated_ui_tests',
>>             '../app/app.gyp:app_unittests',
>>             '../base/base.gyp:base_unittests',
>>             '../ipc/ipc.gyp:ipc_tests',
>>             '../media/media.gyp:media_unittests',
>>             '../net/net.gyp:net_unittests',
>>             '../printing/printing.gyp:printing_unittests',
>>             'unit_tests',
>>
>> I did not yet add unit test bundles which don't run on 3 platforms
>> (interactive_ui_tests, browser_tests, courgette_tests).
>>
>> ui_tests runs on 3 platforms but chokes on OSX when run instrumented; I
>> need to track down why.
>>
>> jrg
>>
>>
>> On Mon, Jan 4, 2010 at 8:53 AM, Scott Violet <[email protected]> wrote:
>>
>>> 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 <[email protected]>
>>> 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: [email protected]
>>> > View archives, change email options, or unsubscribe:
>>> > http://groups.google.com/group/chromium-dev
>>>
>>
>>  --
>> Chromium Developers mailing list: [email protected]
>> View archives, change email options, or unsubscribe:
>> http://groups.google.com/group/chromium-dev
>>
>
>

-- 
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev

Reply via email to