diff options
author | kkania@chromium.org <kkania@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-20 00:59:38 +0000 |
---|---|---|
committer | kkania@chromium.org <kkania@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-20 00:59:38 +0000 |
commit | 060e9ddba52b3ac3704bbdcfc1c755e53b695e1b (patch) | |
tree | 24e5c75523302405922d7c7a99652c713fbc55c7 /chrome/common/automation_constants.h | |
parent | 09a9da72051e7543bd800167c88e5d56c523b5fe (diff) | |
download | chromium_src-060e9ddba52b3ac3704bbdcfc1c755e53b695e1b.zip chromium_src-060e9ddba52b3ac3704bbdcfc1c755e53b695e1b.tar.gz chromium_src-060e9ddba52b3ac3704bbdcfc1c755e53b695e1b.tar.bz2 |
Revert 66840 - Add named testing interface. This allows you to connect to a pre-existing Chrome process and run tests on it. This is an addition to the low level interface underlying testing frameworks like PyAuto and WebDriver.
Normally, test frameworks communicate with Chrome over an unnamed socket pair on POSIX. The test creates the socket pair and then launches the browser as a child process, passing an open file descriptor for one end of the socket to the browser. This change adds a command line switch that, when passed to the browser, causes it to listen on a named socket instead, eliminating this parent/child process requirement. Therefore, you can potentially connect any number of tests to a preexisting browser process.
For ChromeOS, this allows you to run tests on the instance of Chrome that is launched on startup, which controls things like the login and lock screens, the battery meter, the wireless UI, etc. Currently there is no way to run tests on a pre-existing Chrome instance. Eventually this will also allow you to connect both PyAuto and WebDriver to the same Chrome instance and run both in the same test.
If you pass the browser the following command line switch:
./chrome --testing-channel=NamedTestingInterface:/path/to/file
This causes the browser to listen for incoming connections. An AutomationProxy can connect to the browser by connecting a Unix domain socket to the specified path and control the browser over the socket.
This is currently only for POSIX. Windows support will come in a future change. Also, this initial change only allows one connection; multiple connection support will come in a future change.
BUG=chromium-os:8512
TEST=Run Chrome with --testing-interface=/var/tmp/NamedTestingInterface, then run NamedInterfaceTest.BasicNamedInterface under ui_tests.
Review URL: http://codereview.chromium.org/4202004
TBR=nirnimesh@chromium.org
Review URL: http://codereview.chromium.org/5177007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66856 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/automation_constants.h')
-rw-r--r-- | chrome/common/automation_constants.h | 10 |
1 files changed, 1 insertions, 9 deletions
diff --git a/chrome/common/automation_constants.h b/chrome/common/automation_constants.h index 6579776..13b120e 100644 --- a/chrome/common/automation_constants.h +++ b/chrome/common/automation_constants.h @@ -7,7 +7,6 @@ #pragma once namespace automation { - // JSON value labels for proxy settings that are passed in via // AutomationMsg_SetProxyConfig. These are here since they are used by both // AutomationProvider and AutomationProxy. @@ -17,16 +16,9 @@ extern const char kJSONProxyPacUrl[]; extern const char kJSONProxyBypassList[]; extern const char kJSONProxyServer[]; -// When passing the kTestingChannelID switch to the browser, prepend -// this prefix to the channel id to enable the named testing interface. -// Named testing interface is used when you want to connect an -// AutomationProxy to an already-running browser instance. -extern const char kNamedInterfacePrefix[]; - // Amount of time to wait before querying the browser. static const int kSleepTime = 250; - -} // namespace automation +} // Used by AutomationProxy, declared here so that other headers don't need // to include automation_proxy.h. |