Thank you. My goal is to "remote control" (e.g. load an url) a running instance of browser.
That is why I am trying to run this AutomationProxyTest NavigateToURL to an running instance of browser. That is why I ask how can I run the 'TEST_F(AutomationProxyTest, NavigateToURL) ' Test case in automation_proxy_uitest.cc using the browser I start in XCode? On Thu, Sep 3, 2009 at 8:29 AM, Paweł Hajdan Jr.<[email protected]> wrote: > You need AutomationProxy for that. See the line > server_.reset(CreateAutomationProxy(command_execution_timeout_ms_)); > Please keep the discussion on the list. And I'll repeat my question: what is > your goal? I might guess that you are trying to re-use the browser between > test runs. It may be a bad example, but in that case there is a much better > (and easier!) way to do that. > > On Wed, Sep 2, 2009 at 19:18, hap 497 <[email protected]> wrote: >> >> Thank you. >> >> I am doing this in XCode on MacOSX. >> >> I have commented out >> * LaunchBrowserAndServer() in UITest::Setup(); >> * CloseBrowserAndServer() in UITest::TearDown(); >> >> And then I start 'chrome' executable in my chrome xcode project. >> >> But how can I run the 'TEST_F(AutomationProxyTest, NavigateToURL) ' >> Test case in automation_proxy_uitest.cc using the browser I start in >> XCode? >> >> Thank you for your help again. >> >> >> On Wed, Sep 2, 2009 at 12:48 PM, Paweł Hajdan >> Jr.<[email protected]> wrote: >> > I think you're on a good track then. Just see how the UI test launches >> > the >> > browser, and to the same manually. Then rip out the launching and >> > shutdown >> > of the browser out of ui_test.cc, and rewire that with the test case you >> > want to run. I can explain in more detail if needed. >> > But... what are you ultimately trying to accomplish? The automation is a >> > tricky thing, and maybe I'll be able to recommend a better way when I >> > see >> > your goal. >> > >> > On Wed, Sep 2, 2009 at 12:45, hap 497 <[email protected]> wrote: >> >> >> >> Currently, I run the 'ui_tests --gtest_filter=Automation*'. This way, >> >> the test creates and tears >> >> down chromium for each test case. >> >> >> >> What I would like is >> >> 1. Launch an instance of chromium (with automation enable) >> >> 2. disable 'creates/tears down of chromium in chromium ui test >> >> 3. Execute 1 test case against that instance of chromium >> >> >> >> Thank you. >> >> >> >> On Wed, Sep 2, 2009 at 10:06 AM, Paweł Hajdan >> >> Jr.<[email protected]> wrote: >> >> > Could you provide some more details? You can find some examples in >> >> > chrome/test/ui/ui_test.cc (LaunchBrowserHelper). >> >> > >> >> > On Wed, Sep 2, 2009 at 09:40, hap 497 <[email protected]> wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> Can you please tell me how can I run chromium with 'automation' >> >> >> enabled? >> >> >> >> >> >> Thank you. >> >> >> >> >> >> >> >> >> >> >> > >> >> > >> > >> > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
