On Fri, Jan 30, 2009 at 9:31 AM, Scott Violet <[email protected]> wrote: > The second test class is InProcessBrowserTest. This test class invokes > BrowserMain (but not BrowserInit) to startup Chrome, then runs your > test method. Your test method is then running as if you were inside > Chrome. You can create and destroy Browsers, navigate to pages; > whatever. InProcessBrowserTest can be used as a replacement for > existing UI tests. See InProcessBrowserTest documentation for details > as well as find_bar_win_unittest for an example.
Thanks! I was just looking at writing a UI test for extensions, and it was a bit painful because the extensions service loads asynchronously. Even though it sends out a notification when complete, and external process can't easily see that. This will things easier. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
