+1 That would be extremely useful to the Mac port as well.
WebKit calls a bunch of OS X APIs that are not specced in regards to their
interaction with the Sandbox (i.e. they may try to open arbitrary files,
talk to the network, etc and fail in the process). We have no good source
of test coverage for this at the moment.
In addition, if memory serves, we've run into a few sitatuions in the Mac
port where things have worked fine in test shell while failing in Chrome
(I'm sure similar situations exist on other platforms).
Running Layout Tests in Chrome would address both of these issues.
Best regards,
Jeremy
On Wed, Apr 29, 2009 at 2:05 PM, Mike Belshe <mbel...@google.com> wrote:
> We're still using the test-shell to run the LayoutTests. I just fixed a
> bug, wrote a layout test, and then realized how dumb I was because the code
> I was testing was only in Chrome, and not in the test_shell.
>
> I think we're accumulating a lot of code that is chrome specific, but which
> could effect rendering and layout. In my case, I'm working on v8 extensions
> that have been put into the browser, but there is tons of code which differs
> between chrome and test shell. Not having layout tests for chrome itself is
> making me a bit nervous.
>
> 2 Questions:
>
> 1) Any plans already underway to run chrome rather than test_shell through
> the Layout Tests?
>
> 2) Should we create those plans :-)
>
> Cheers,
> Mike
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
