summaryrefslogtreecommitdiffstats
path: root/chrome/test/ui/ui_test.cc
Commit message (Collapse)AuthorAgeFilesLines
* Move platform_thread to base/threading and put in the base namespace. I left abrettw@chromium.org2010-12-311-4/+4
| | | | | | | | | | | stub and "using" declarations in the old location to avoid having to change the entire project at once. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/6001010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70342 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up Automation and Chrome Frame IPC code.-only use routed messages when ↵jam@chromium.org2010-12-231-2/+2
| | | | | | | | needed-use routing IDs to avoid manually unpacking messages-remove data structures from IPC namespace (that should only be used for IPC code, and param traits)Note that I temporarily commented out part of a test in external_tab_test.cc because I couldn't figure out how to get the updated gmock macros to compile. Review URL: http://codereview.chromium.org/5998006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70105 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 68944 - Revert "Add named testing interface."nirnimesh@chromium.org2010-12-231-21/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reverting the revert of named interface CL. Followup CL which addresses Pawel's comments is up at http://codereview.chromium.org/5967003/ http://src.chromium.org/viewvc/chrome?view=rev&revision=67300 The change has been approved conditionally, i.e. if the outstanding review comments are handled in a follow-up as the top priority. Two weeks have passed, and I have not seen the follow-up. It is risky to keep this change in the tree, as it is already non-trivial to revert. Conflicts: chrome/browser/automation/automation_provider.cc chrome/test/ui/named_interface_uitest.cc ipc/ipc_channel_posix.cc TBR=nirnimesh BUG=chromium-os:8512 TEST=none Review URL: http://codereview.chromium.org/5707006 TBR=phajdan.jr@chromium.org BUG=chromium-os:8512 TEST=ui_tests --gtest_filter=NamedInterfaceTest.FLAKY_BasicNamedInterface Review URL: http://codereview.chromium.org/6012006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70089 0039d316-1c4b-4281-b951-d872f2087c98
* Update file version info/memory details/process utils to use string16.avi@chromium.org2010-12-231-1/+1
| | | | | | | | | BUG=23581 TEST=everything still works Review URL: http://codereview.chromium.org/5968008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70071 0039d316-1c4b-4281-b951-d872f2087c98
* Rename WebKitTools->Tools.tonyg@chromium.org2010-12-181-1/+1
| | | | | | | | | | BUG=None TEST=None TBR=yurys Review URL: http://codereview.chromium.org/6015002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69627 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Add named testing interface."phajdan.jr@chromium.org2010-12-111-39/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | http://src.chromium.org/viewvc/chrome?view=rev&revision=67300 The change has been approved conditionally, i.e. if the outstanding review comments are handled in a follow-up as the top priority. Two weeks have passed, and I have not seen the follow-up. It is risky to keep this change in the tree, as it is already non-trivial to revert. Conflicts: chrome/browser/automation/automation_provider.cc chrome/test/ui/named_interface_uitest.cc ipc/ipc_channel_posix.cc TBR=nirnimesh BUG=chromium-os:8512 TEST=none Review URL: http://codereview.chromium.org/5707006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68944 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-241-21/+39
| | | | | | | | | | | | | | | | | | | | | 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 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67300 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66840 - Add named testing interface. This allows you to connect to a ↵kkania@chromium.org2010-11-201-39/+21
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-191-21/+39
| | | | | | | | | | | | | | | | | | | | | 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 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66840 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 66350 - Add named testing interface. This allows you to connect to a ↵nirnimesh@chromium.org2010-11-171-39/+21
| | | | | | | | | | | | | | | | | | | | | | | | 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/5139001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66368 0039d316-1c4b-4281-b951-d872f2087c98
* Add named testing interface. This allows you to connect to a pre-existing ↵nirnimesh@chromium.org2010-11-171-21/+39
| | | | | | | | | | | | | | | | | | | | | 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 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66350 0039d316-1c4b-4281-b951-d872f2087c98
* Group cmdline settings in UI test and in_process_browser_test.lzheng@chromium.org2010-11-161-34/+39
| | | | | | | | | BUG=none TEST=all UI tests and browser tests stays green. Review URL: http://codereview.chromium.org/4724004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66202 0039d316-1c4b-4281-b951-d872f2087c98
* Restrict file protocol on chromeos to certain whitelisted directories. ↵achuith@chromium.org2010-11-111-0/+3
| | | | | | | | | | | Disable this for tests. BUG=chromium-os:3412 TEST=Access file: directories on chromeos. browser, ui, interactive ui and unit tests should continue to pass. Review URL: http://codereview.chromium.org/4160003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65866 0039d316-1c4b-4281-b951-d872f2087c98
* Part 2 of reapplying r64637.erg@google.com2010-11-101-1/+1
| | | | | | | | | | | | | Move the automation message files from chrome/test/automation to chrome/common/. This requires a temporary override to chrome/common/DEPS until Part 3 lands. BUG=51409 TEST=compiles Review URL: http://codereview.chromium.org/4758001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65695 0039d316-1c4b-4281-b951-d872f2087c98
* Moved --use-gl=osmesa to UITest::SetUp so it is not visible to pyautolib.apatrick@chromium.org2010-11-101-8/+11
| | | | | | | | | | | It derives from UITestBase. TEST=ui_tests BUG=62602 Review URL: http://codereview.chromium.org/4662005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65616 0039d316-1c4b-4281-b951-d872f2087c98
* Moved --use-gl=osmesa switch out of test_launcher_utils.apatrick@chromium.org2010-11-101-0/+10
| | | | | | | | | | | | | It was affecting tests other than ui_tests and browser_tests, which potentially need to use regular GL. For example, plugins expect to be able to use regular GL with core animation. In the future, we should be able to make more tests use osmesa by allowing a regular GL surface to be read back into an OSMesa surface in AcceleratedSurface on Mac. TEST=ui_tests, browser_tests BUG=62602 Review URL: http://codereview.chromium.org/4761001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65604 0039d316-1c4b-4281-b951-d872f2087c98
* BUG=43066ahendrickson@chromium.org2010-11-091-4/+26
| | | | | | | | TEST=Download UI tests are much less flaky on build bots. Review URL: http://codereview.chromium.org/3790010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65542 0039d316-1c4b-4281-b951-d872f2087c98
* Split out command IDs from chrome_dll_resource.h.evan@chromium.org2010-11-081-1/+1
| | | | | | | | | | | | The name of this file is a leftover from Windows. Split the command ids (which are used on all platforms) out, leaving just the Windows-specific resource IDs in the original file. TEST=compiles Review URL: http://codereview.chromium.org/4710001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65453 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Refactor automation messages." due to mysterious problems on mac.erg@google.com2010-11-011-1/+1
| | | | | | | | | | | | | This reverts commit c1c1fed998ee4d839bfe256150e5e59220ebc0ef (r64637). TBR=nirnimesh@ BUG=51409 TEST=none Review URL: http://codereview.chromium.org/4194007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64644 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor automation messages.erg@google.com2010-11-011-1/+1
| | | | | | | | | | | | | | | | | automation_messages used to live in chrome/test/automation, when it's needed by browser and chrome_frame. When I started lifting code out of headers and into implementation files, I was getting link errors and temporarily solved the problem by compiling the cc files manually into libbrowser.a. Now this is part of chrome/common/ which is included by all targets needed. While doing this, discover that automation IPC redefines the ContextMenuParams struct. Rename it to MiniContextMenuParams. BUG=51409 TEST=none Review URL: http://codereview.chromium.org/4200007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64637 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 63388 - ↵stoyan@chromium.org2010-10-211-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://build.chromium.org/buildbot/waterfall/builders/Mac10.6%20Tests%20(dbg)(2)/builds/10949 - Relanding 61718. I disabled the GPU watchdog in three new cases: - If the OSMesa software renderer is in use. This will disable it on bots. - When running on valgrind, whether on a bot or locally. - In debug builds I added a GPU process initialization time to the GPU info. I moved the GPU initialization code outside the watchdog protection because it can take a long time and trigger the watchdog. I increased the timeout. I set up a field trial with different timeouts to see the rate of failure for each period. I made ui_tests always run with OSMesa, for consistent operation on bots and when run locally. Original CL description: I added a watchdog thread that intermitently checks the main thread can respond to tasks posted on its message queue. I fixed some bugs that preventede GGL from failing when the GPU channel was lost. Added a command line swith to disable the watchdog thread for debugging purposes. TEST=try, local testing of all features BUG=none Review URL: http://codereview.chromium.org/3794011 TBR=apatrick@chromium.org Review URL: http://codereview.chromium.org/3979004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63396 0039d316-1c4b-4281-b951-d872f2087c98
* Relanding 61718.apatrick@chromium.org2010-10-211-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I disabled the GPU watchdog in three new cases: - If the OSMesa software renderer is in use. This will disable it on bots. - When running on valgrind, whether on a bot or locally. - In debug builds I added a GPU process initialization time to the GPU info. I moved the GPU initialization code outside the watchdog protection because it can take a long time and trigger the watchdog. I increased the timeout. I set up a field trial with different timeouts to see the rate of failure for each period. I made ui_tests always run with OSMesa, for consistent operation on bots and when run locally. Original CL description: I added a watchdog thread that intermitently checks the main thread can respond to tasks posted on its message queue. I fixed some bugs that preventede GGL from failing when the GPU channel was lost. Added a command line swith to disable the watchdog thread for debugging purposes. TEST=try, local testing of all features BUG=none Review URL: http://codereview.chromium.org/3794011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63388 0039d316-1c4b-4281-b951-d872f2087c98
* Rename CommandLine::ARGUMENTS_ONLY to NO_PROGRAM.mattm@chromium.org2010-10-211-2/+2
| | | | | | | | | | | ARGUMENTS_ONLY was misleading since CommandLine has methods for handling "switches" and "arguments", but that constructor still allows both. BUG=none TEST=still builds Review URL: http://codereview.chromium.org/3935001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63325 0039d316-1c4b-4281-b951-d872f2087c98
* Convert LOG(INFO) to VLOG(1) - chrome/test/.pkasting@chromium.org2010-10-201-4/+3
| | | | | | | | | | Also fix indentation, remove a few unnecessary endls, collapse some append()s into +s, and remove a few extra {}s. BUG=none TEST=none Review URL: http://codereview.chromium.org/3915004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63253 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Move more parts of UITestBase down to UITest.phajdan.jr@chromium.org2010-10-151-50/+49
| | | | | | | | | | | | This is a part of an effor to make UITestBase reusable in more contexts. BUG=56865 TEST=if it compiles it is perfect Review URL: http://codereview.chromium.org/3764008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62751 0039d316-1c4b-4281-b951-d872f2087c98
* Move windows version-related stuff out of base/win_util and into ↵brettw@chromium.org2010-10-151-2/+2
| | | | | | | | | | | | | | base/win/windows_version. Many files now only need to include this instead of all of win_util. Remove a bunch of unused code from base/win_util. There was a surprising amount. Replace the AppUserModel property key with the one from the SDK now that we use the Win7 SDK. Move GetLogonSessionOnlyDACL from win_util to ipc since it's only used in that one place. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/3823002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62694 0039d316-1c4b-4281-b951-d872f2087c98
* base: Move SplitString functions into the base namespace and update the callers.tfarina@chromium.org2010-10-141-1/+1
| | | | | | | | | BUG=None TEST=trybots Review URL: http://codereview.chromium.org/3750001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62483 0039d316-1c4b-4281-b951-d872f2087c98
* Record startup time closer to where the browser really startednirnimesh@chromium.org2010-10-121-3/+2
| | | | | | | | | | | | | | | | | | | | | startup time is used as a timestamp to discover new crashes (determined by entries in crash dir since the recorded startup time) in the ui_test framework. Initialing it in the constructor is problematic for PyAuto since python unittest initialzes testcase objects for all tests together, so all instances will have about the same startup time, and this leads to crashes from one test being mismatched to the error reporting in another. This CL fixes it by moving startup time initialization to SetUp, which is closer to the time the browser actually gets launched. Consciously, Not moving to LaunchBrowserAndServer. BUG=51463 TEST= Review URL: http://codereview.chromium.org/3670004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62314 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Move parts of UITestBase down to UITest.phajdan.jr@chromium.org2010-10-061-267/+268
| | | | | | | | | | | | This is a part of an effort to make UITestBase reusable in more contexts. BUG=56865 TEST=if it compiles it is perfect Review URL: http://codereview.chromium.org/3519010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61645 0039d316-1c4b-4281-b951-d872f2087c98
* Extract common browser command-line flags used by tests.phajdan.jr@chromium.org2010-09-301-8/+2
| | | | | | | | | | | | This will help avoiding adding a required flag to ui_tests but not browser_tests and vice versa. BUG=none TEST=none Review URL: http://codereview.chromium.org/3565003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61037 0039d316-1c4b-4281-b951-d872f2087c98
* Turn off preconnect for UI tests as well.jochen@chromium.org2010-09-291-0/+3
| | | | | | | | | BUG=none TEST=less flakiness on the tree Review URL: http://codereview.chromium.org/3520004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60921 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: clean up http server launching in ui_tests.phajdan.jr@chromium.org2010-09-281-28/+20
| | | | | | | | | | | We can use the utilities from base/process_util. BUG=none TEST=none Review URL: http://codereview.chromium.org/3441033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60786 0039d316-1c4b-4281-b951-d872f2087c98
* ui_tests: check the return value of WaitForAppLaunch.evan@chromium.org2010-09-241-1/+2
| | | | | | | | | | | | | This function has a return value. We should abort the test if it fails. BUG=45115 TEST=EarlyReturnTest.ToastCrasher, which times out, should go red (I preemptively disabled it) Review URL: http://codereview.chromium.org/3470014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60506 0039d316-1c4b-4281-b951-d872f2087c98
* base: Finish moving the SplitString functions from string_util.h to ↵tfarina@chromium.org2010-09-241-0/+1
| | | | | | | | | | | string_split.h BUG=None TEST=trybos Review URL: http://codereview.chromium.org/3447008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60422 0039d316-1c4b-4281-b951-d872f2087c98
* ifdef out tests that don't apply to the Macstuartmorgan@chromium.org2010-09-231-0/+2
| | | | | | | | | | | The reason these tests were failing on the Mac is that they test something that the Mac explicitly doesn't support: opening a new window in the existing browser process by re-running from the command line. This ifdefs out the tests that don't apply to the Mac, and the helper method that they are built on so that new tests using it won't accidentally be run on the Mac. BUG=45108 TEST=N/A Review URL: http://codereview.chromium.org/3394018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60354 0039d316-1c4b-4281-b951-d872f2087c98
* Use a scoped temp dir in browser_tests instead of deleting the default user ↵rohitrao@chromium.org2010-09-231-15/+3
| | | | | | | | | | data dir. BUG=None TEST=Less flake, I hope. Review URL: http://codereview.chromium.org/3443021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60335 0039d316-1c4b-4281-b951-d872f2087c98
* Unify the two places we attempt to find the crash count.evan@chromium.org2010-09-221-10/+15
| | | | | | | | | | | Aside from reducing duplicated logic, I intend to change the behavior of this (newly refactored) function. BUG=46246 Review URL: http://codereview.chromium.org/3475008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60234 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 57897 - GTTF: Retry launching the browser a few times in UITest.phajdan.jr@chromium.org2010-09-141-37/+8
| | | | | | | | | | | | | | | | This should help us with some temporary bad conditions on the bots. The browser shouldn't fail to start three times in a row. TEST=ui_tests BUG=52746, 54453 Review URL: http://codereview.chromium.org/3126034 TBR=phajdan.jr@chromium.org Review URL: http://codereview.chromium.org/3404001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59315 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Move UI test timeouts to a centralized place, chrome/test/test_timeouts.phajdan.jr@chromium.org2010-09-101-93/+17
| | | | | | | | | | | | Next patches will also centralize timeouts for our other test binaries based on that file. BUG=none TEST=none Review URL: http://codereview.chromium.org/3308020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59145 0039d316-1c4b-4281-b951-d872f2087c98
* Fix CheckFalseTest.CheckFails on Linux after my change to ui_test.phajdan.jr@chromium.org2010-09-091-0/+12
| | | | | | | | | | | | | This makes PathService clear its cache after overriding a path. We have many paths depending on each other, so this is necessary to avoid inconsistencies. TEST=ui_tests in Release mode BUG=49838 Review URL: http://codereview.chromium.org/2805100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59021 0039d316-1c4b-4281-b951-d872f2087c98
* Make FastShutdown ui test more reliable on linux.estade@chromium.org2010-09-081-11/+15
| | | | | | | | | | | | | | | See previous patch at http://codereview.chromium.org/2830010/show This patch puts the responsibility of waiting on the test rather than making ui_test.cc robust. The reason for moving the test to interactive tests (instead of straight up ui tests) is that waving the mouse around can break the test. BUG=46614 TEST=test passes many times locally; try bots Review URL: http://codereview.chromium.org/3338013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58863 0039d316-1c4b-4281-b951-d872f2087c98
* Moving file_util::FileInfo to base::PlatformFileInfo, and adding thedumi@chromium.org2010-09-031-2/+1
| | | | | | | | | | | | last_accessed and creation_time fields. BUG=none TEST=none Review URL: http://codereview.chromium.org/3347005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58454 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Retry launching the browser a few times in UITest.phajdan.jr@chromium.org2010-08-301-8/+37
| | | | | | | | | | | | | This should help us with some temporary bad conditions on the bots. The browser shouldn't fail to start three times in a row. TEST=ui_tests BUG=52746 Review URL: http://codereview.chromium.org/3126034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57897 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Extract performance-testing-specific parts of UITestBase to UIPerfTest.phajdan.jr@chromium.org2010-08-261-316/+0
| | | | | | | | | | | In the future this may even be used to tune some settings/behaviors (like timeouts) for performance tests. TEST=ui_tests, page_cycler_*, etc BUG=none Review URL: http://codereview.chromium.org/3137040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57552 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 56738 - Fix CheckFalseTest.CheckFails on Linux after my change to ↵rvargas@google.com2010-08-191-12/+0
| | | | | | | | | | | | | | | | | | ui_test. This makes PathService clear its cache after overriding a path. We have many paths depending on each other, so this is necessary to avoid inconsistencies. TEST=ui_tests in Release mode BUG=49838 Review URL: http://codereview.chromium.org/2805100 TBR=phajdan.jr@chromium.org Review URL: http://codereview.chromium.org/3169031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56778 0039d316-1c4b-4281-b951-d872f2087c98
* Fix CheckFalseTest.CheckFails on Linux after my change to ui_test.phajdan.jr@chromium.org2010-08-191-0/+12
| | | | | | | | | | | | | This makes PathService clear its cache after overriding a path. We have many paths depending on each other, so this is necessary to avoid inconsistencies. TEST=ui_tests in Release mode BUG=49838 Review URL: http://codereview.chromium.org/2805100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56738 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: After timeout, all further automation calls should fail immediately.phajdan.jr@chromium.org2010-08-191-2/+9
| | | | | | | | | | | | | If IPC send fails, further automation calls are extremely likely to fail. Avoid wasting a lot of time on further timeouts by closing the channel immediately on the first error. TEST=ui_tests BUG=51346 Review URL: http://codereview.chromium.org/3131020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56722 0039d316-1c4b-4281-b951-d872f2087c98
* CommandLine: eliminate wstring-accepting AppendLooseValueevan@chromium.org2010-08-131-5/+6
| | | | | | | | Instead use AppendArg variants which accept a FilePath or an ASCII string. Review URL: http://codereview.chromium.org/3134008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56100 0039d316-1c4b-4281-b951-d872f2087c98
* Add new downloads testsnirnimesh@chromium.org2010-08-071-0/+11
| | | | | | | | | | | testBigZip -- test downloads for a 1 GB file, from Sunand This required methods to temporarily increase automation timeout, since it might not be possible to download 1 GB file in the default 25 secs. testDownloadsPersistence -- verify that download history persists browser restart, from Srikanth Review URL: http://codereview.chromium.org/3046030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55341 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Replace DCHECK with EXPECT_TRUE in UITestBase.phajdan.jr@chromium.org2010-08-061-1/+1
| | | | | | | | | | | We should avoid crashing entire ui_tests in case of failure. With EXPECT_TRUE we still see it, but tests continue to run. TBR=huanr Review URL: http://codereview.chromium.org/2868116 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55279 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-09 11:04:37 +0000