How is this different from ChromeBot? How you control things depends on what level of "realism" you want. If you're just verifying the sites work correctly, you might just use the code the UI tests use. If you want to actually simulate button clicks and such, then you'll need something more like selenium. If you just care about testing the rendering engine, then you could just hook straight into the WebKit API (note that it's not _quite_ done yet...so you'd need to use Glue some as well).
I think maybe you should explore what's there a bit more and/or figure out exactly what you want to test so you can ask more specific questions. J On Mon, Oct 5, 2009 at 7:12 PM, TJ Shah <[email protected]> wrote: > > Hi, > > I have recently started working on Chrome Release process automation > where I want to automate Visiting various sites (e.g. Top 200 sites) > using Chrome and other browsers and look for possible App-compat > issues. I am fairly new to this kind of automation in Chrome, so > looking for possible ways to automate that. > > I found some references to using Automation Proxy, Web Driver and > Selenium, but not sure on where to get more information on those > tools. Can someone throw some light here? Which is better and more > supported? Any previous work done in this kind of area? Looking for > more longer term cross-plat tool which we can reply on. > > Remember, I want to drive the chrome automation from outside browser > process so test doesn't die when browser crashes. So I think, In-proc > browser will be of little help here. > > Any help will be appreciated !!! > > Thanks, > TJ > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
