summaryrefslogtreecommitdiffstats
path: root/chrome/test/ui
Commit message (Collapse)AuthorAgeFilesLines
* 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
* Remove some obsolete FLAKY_ markers, and add some missing bug referencesstuartmorgan@chromium.org2010-11-091-2/+1
| | | | | | | | | BUG=29020,35221,62143,62595 TEST=N/A Review URL: http://codereview.chromium.org/4759001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65589 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-082-2/+2
| | | | | | | | | | | | 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
* * Add follow_redirects_ field to pepper::URLRequestInfo, follow_redirects() ↵brettw@chromium.org2010-11-081-2/+1
| | | | | | | | | | | | | accessor, modified SetProperty to support this * Add status_text_, redirect_url_ fields to pepper::URLResponseInfo, modified GetProperty to return these * Add URL redirect auditing to pepper::URLLoader. BUG=49790 BUG=51345 TEST=ui_tests --gtest_filter=PPAPI* Review=http://codereview.chromium.org/4394003/show git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65443 0039d316-1c4b-4281-b951-d872f2087c98
* Added GPUBrowserTest.BrowserTestLaunchedWithOSMesa.apatrick@chromium.org2010-11-041-38/+0
| | | | | | | | | | | | | | | | | This just verifies that the OpenGL backend is OSMesa and does a simple smoke test that it is functional. It is the browser test equivalent of GPUUITest.UITestLaunchedWithOSMesa. OSMesa should be required for both kinds of tests. I moved both tests into the new chrome/test/gpu directory. There are ongoing stability issues with OSMesa (and GL in general) on bots. TEST=passes locally, try BUG=none Review URL: http://codereview.chromium.org/4424001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65126 0039d316-1c4b-4281-b951-d872f2087c98
* Fix up test directory to use the new file location for the PPAPI tests.brettw@chromium.org2010-11-041-1/+1
| | | | | | | | TEST=this is a test BUG=none Review URL: http://codereview.chromium.org/4406003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65099 0039d316-1c4b-4281-b951-d872f2087c98
* Remove FileRef, FileIO and DirectoryReader PPAPI tests from ui_testsdumi@chromium.org2010-11-041-12/+0
| | | | | | | | | | | | | for now. It looks like run_testserver is crashing. BUG=none TEST=none TBR=darin Review URL: http://codereview.chromium.org/4411002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65008 0039d316-1c4b-4281-b951-d872f2087c98
* Pepper's directory reader implementation + test.dumi@chromium.org2010-11-041-0/+12
| | | | | | | | | BUG=none TEST=test_directory_reader.cc Review URL: http://codereview.chromium.org/4107004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65002 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps. This is a re-land ↵brettw@chromium.org2010-11-021-1/+0
| | | | | | from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64757 0039d316-1c4b-4281-b951-d872f2087c98
* Revert PPAPI change due to Linux compile failures.brettw@chromium.org2010-11-021-0/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64751 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps.brettw@chromium.org2010-11-021-1/+0
| | | | | | | | | This is a re-land from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64750 0039d316-1c4b-4281-b951-d872f2087c98
* Revert PPAPI change.brettw@chromium.org2010-11-021-0/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64719 0039d316-1c4b-4281-b951-d872f2087c98
* Use PPAPI from chrome trunk rather than pulling via deps.brettw@chromium.org2010-11-021-1/+0
| | | | | | | | | This is a re-land from r64716. This is identical with an an include directory changed in the ppapi repo which I'm hoping was what was confusing everything. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64718 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 64716 - Switch to the new PPAPI repository. This removes the DEPS ↵brettw@chromium.org2010-11-021-0/+1
| | | | | | | | | | | | | | entry that refers to the PPAPI repo, and fixes the includes to use the new location. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/4164015 TBR=brettw@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64717 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to the new PPAPI repository. This removes the DEPS entry that refers tobrettw@chromium.org2010-11-021-1/+0
| | | | | | | | | | the PPAPI repo, and fixes the includes to use the new location. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/4164015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64716 0039d316-1c4b-4281-b951-d872f2087c98
* Marked GPUUITest.UITestLaunchedWithOSMesa disabled on Windows.apatrick@chromium.org2010-11-021-5/+4
| | | | | | | | | | | http://build.chromium.org/p/chromium/builders/Vista%20Tests/builds/672/steps/ui_tests/logs/UITestLaunchedWithOSMesa TEST=none BUG=none Review URL: http://codereview.chromium.org/4242002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64705 0039d316-1c4b-4281-b951-d872f2087c98
* Reenabled GPUTest.UITestLaunchedWithOSMesa on linux and windows.apatrick@chromium.org2010-11-011-3/+3
| | | | | | | | | | | I think r64288 will make it work. TEST=try BUG=none Review URL: http://codereview.chromium.org/4201005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64674 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
* Flagged GPUTest.UITestLaunchedWithOSMesa as DISABLED.apatrick@chromium.org2010-10-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | [10101:10101:550978034308:WARNING:app/gfx/gl/gl_context_linux.cc(194)] GLX 1.3 or later is recommended. [10101:10101:550978122044:ERROR:app/gfx/gl/gl_context_linux.cc(539)] glXChooseFBConfig failed. failed to create pixmap [10101:10101:550978127562:ERROR:chrome/gpu/gpu_main.cc(33)] X Error detected: serial 128, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 55 minor_code 0 (X_CreateGC) [10101:10101:550978127622:ERROR:chrome/gpu/gpu_main.cc(33)] X Error detected: serial 129, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 55 minor_code 0 (X_CreateGC) [10101:10101:550978127643:ERROR:chrome/gpu/gpu_main.cc(33)] X Error detected: serial 130, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 14 minor_code 0 (X_GetGeometry) [10101:10101:550978127738:ERROR:chrome/gpu/gpu_main.cc(33)] X Error detected: serial 131, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 14 minor_code 0 (X_GetGeometry) [10101:10101:550978127824:ERROR:chrome/gpu/gpu_main.cc(33)] X Error detected: serial 132, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 14 minor_code 0 (X_GetGeometry) ... http://build.chromium.org/p/chromium/builders/Linux%20Builder%20%28ChromiumOS%20dbg%29/builds/545/steps/ui_tests/logs/stdio It appears that the bot does not support GLX 1.3. I am working on making the bots use OSMesa by default. TEST=none BUG=none TBR=vangelis@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64280 0039d316-1c4b-4281-b951-d872f2087c98
* Update a bunch of FLAKY_ tests to match current realitystuartmorgan@chromium.org2010-10-281-5/+2
| | | | | | | | | | | Mostly this is removing FLAKY_ where the bug was fixed but the label never removed, but also switches some FLAKY_ to platform-specific FAILS_. BUG=28372,32048,32070,35341,45561,48544,48562,52858 TEST=N/A Review URL: http://codereview.chromium.org/4087009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64264 0039d316-1c4b-4281-b951-d872f2087c98
* Marking GPUTest.UITestLaunchedWithOSMesa FLAKY.apatrick@chromium.org2010-10-281-1/+1
| | | | | | | | | | | http://build.chromium.org/p/chromium/builders/Vista%20Tests/builds/524 TEST=none BUG=none TBR=vangelis@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64190 0039d316-1c4b-4281-b951-d872f2087c98
* Add a bunch of missing bug references to FLAKY testsstuartmorgan@chromium.org2010-10-271-0/+1
| | | | | | | | | BUG=None TEST=N/A Review URL: http://codereview.chromium.org/4135007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64150 0039d316-1c4b-4281-b951-d872f2087c98
* Temporarily disabling test GPUTest.UITestLaunchedWithOSMesa on linux.apatrick@chromium.org2010-10-271-1/+1
| | | | | | | | | | | | | Test was new in r64122 and failed. http://build.chromium.org/p/chromium/builders/Linux%20Tests%20x64/builds/761/steps/ui_tests/logs/stdio TEST=none BUG=none TBR=kbr@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64138 0039d316-1c4b-4281-b951-d872f2087c98
* ui_tests run with --use-gl=osmesa so they use the OSMesa software renderer ↵apatrick@chromium.org2010-10-271-0/+39
| | | | | | | | | | | | | for GL. This to ensure that ui_tests run consistently regardless of the GPU capabilities, or absense, of the box they run on. TEST=try BUG=none Review URL: http://codereview.chromium.org/4138003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64122 0039d316-1c4b-4281-b951-d872f2087c98
* Add UI test for click-to-play.bauerb@chromium.org2010-10-251-0/+19
| | | | | | | | | BUG=57277 TEST=NPAPIVisiblePluginTester.ClickToPlay:ClickToPlayPluginTest.* Review URL: http://codereview.chromium.org/3539002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63722 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
* Revert 63271 - Add the FileRef and FileIO tests to ppapi_uitest.ccdumi@chromium.org2010-10-201-9/+1
| | | | | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/3883003 TBR=dumi@chromium.org Review URL: http://codereview.chromium.org/4019001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63282 0039d316-1c4b-4281-b951-d872f2087c98
* Add the FileRef and FileIO tests to ppapi_uitest.ccdumi@chromium.org2010-10-201-1/+9
| | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/3883003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63271 0039d316-1c4b-4281-b951-d872f2087c98
* Convert LOG(INFO) to VLOG(1) - chrome/test/.pkasting@chromium.org2010-10-202-6/+5
| | | | | | | | | | 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
* Add a switch to grant unlimited file storage when running Pepper tests.dumi@chromium.org2010-10-201-0/+5
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/3853001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63152 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Move more parts of UITestBase down to UITest.phajdan.jr@chromium.org2010-10-152-73/+69
| | | | | | | | | | | | 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-142-2/+2
| | | | | | | | | 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
* ui_tests: log timings of individual AppCache UI tests.evan@chromium.org2010-10-111-0/+4
| | | | | | | | | | This will help break down why it is slow. BUG=54717 Review URL: http://codereview.chromium.org/3667003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62166 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Move parts of UITestBase down to UITest.phajdan.jr@chromium.org2010-10-062-346/+348
| | | | | | | | | | | | 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
* Move TestTimeouts from chrome/test to base/test.sergeyu@chromium.org2010-10-051-1/+1
| | | | | | | | | BUG=None TEST=unittests Review URL: http://codereview.chromium.org/3544008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61540 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPITest: disable a test that always times out.evan@chromium.org2010-10-041-1/+2
| | | | | | | | BUG=51345 Review URL: http://codereview.chromium.org/3617003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61398 0039d316-1c4b-4281-b951-d872f2087c98
* Run PPAPI's Var testspiman@chromium.org2010-09-301-0/+4
| | | | | | | | | BUG=none TEST=ran ui_tests Review URL: http://codereview.chromium.org/3608002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61099 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
* GTTF: remove flaky mark from following tests:phajdan.jr@chromium.org2010-09-291-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | - FilePathWatcherTest.DeleteAndRecreate (bug 54822) - FilePathWatcherTest.DirectoryChain (bug 54822) - FilePathWatcherTest.MoveChild (bug 54822) - FilePathWatcherTest.MoveParent (bug 54822) - FilePathWatcherTest.NonExistentDirectory (bug 54822) - AccountScreenTest.TestSchemeInspector (bug 46274) - SavePageBrowserTest.SaveCompleteHTML (bug 52292) - DownloadRequestLimiterTest.Allow (bug 39753) - PPAPITest.Graphics2D (bug 54150) - ExtensionApiTest.Storage (bug 42943) - BrowserEncodingTest.TestEncodingAliasMapping (bug 51716) - BrowserCrApplicationAppleScriptTest.InsertWindow (bug 53584) - ExtensionInstallUIBrowserTest.TestThemeInstallUndoResetsToDefault (bug 43441) TBR=mal BUG=54822, 46274, 52292, 39753, 54150, 42943, 51716, 53584, 43441 TEST=none Review URL: http://codereview.chromium.org/3545003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60923 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
* dom_checker_uitest: fix three related bugsevan@chromium.org2010-09-291-8/+13
| | | | | | | | | | | | | | | | 1) was using the wrong path for its http expectations file, so it was never successfully loading the file 2) was not properly aborting when it could load a file, so it'd run the full http test despite not having an expectations file 3) even with that, the http test always fails. At least it fails quickly now. BUG=21321 TEST=DomCheckerTest should get faster by failing fast Review URL: http://codereview.chromium.org/3549002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60905 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-25 00:41:29 +0000