summaryrefslogtreecommitdiffstats
path: root/chrome/test
Commit message (Collapse)AuthorAgeFilesLines
* Linux: enable ChromeMainTest.AppLaunch.agl@chromium.org2010-03-241-2/+0
| | | | | | I can't fault it locally so I want to see if it works on the builders. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42537 0039d316-1c4b-4281-b951-d872f2087c98
* Add instructions to chrome://extensions page for inspecting popups.rafaelw@chromium.org2010-03-243-3/+6
| | | | | | | | | | | Under "Inspect Active Views", any extension that has a browser or page action will show grayed text directing the developer to right click on the icon and select 'Inspect Popup' BUG=24477 TEST=Install an extension with a page or browser action. Go to chrome://extensions, turn on developer mode. Verify that under "inspect active views", the new instructions appear. Review URL: http://codereview.chromium.org/1198002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42529 0039d316-1c4b-4281-b951-d872f2087c98
* Mark keyboard access tests as flaky until I figure out why they'redmazzoni@chromium.org2010-03-241-2/+2
| | | | | | | | | | | | not running on the Interactive Tests buildbot. BUG=http://crbug.com/39213 TEST=none TBR=maruel Review URL: http://codereview.chromium.org/1233005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42526 0039d316-1c4b-4281-b951-d872f2087c98
* Reapply 42467 by reverting 42499 and added suppression.maruel@chromium.org2010-03-242-3/+31
| | | | | | | | | | | "Clear cookies, local storage and databases when an extension gets uninstalled." BUG=39177 BUG=38398 Review URL: http://codereview.chromium.org/1210004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42520 0039d316-1c4b-4281-b951-d872f2087c98
* Remove an old reliability crash suppression. The code moved to the renderer ↵estade@chromium.org2010-03-241-4/+0
| | | | | | | | | | so I expect the crash is gone. If not we can add the suppression back in. BUG=23140 Review URL: http://codereview.chromium.org/1272004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42514 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r42467: "Clear cookies, local storage and databases when an extension ↵maruel@chromium.org2010-03-242-31/+3
| | | | | | | | | | | | gets uninstalled." It introduced a memory leak, causing a regression on valgrind test: unit. TBR=jochen Review URL: http://codereview.chromium.org/1295001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42499 0039d316-1c4b-4281-b951-d872f2087c98
* Keyboard accessibility for the page and app menus.dmazzoni@chromium.org2010-03-248-1/+169
| | | | | | | | | | | | | | | | | | | | | | | | | | Works on Windows, and on Linux with toolkit_views. The goal is to make Chrome behave more like a standard Windows application, for users who rely on the keyboard and expect standard keyboard accelerators to work. Pressing F10, or pressing and releasing Alt, will set focus to the Page menu, as if it was the first item in a menu bar. Pressing enter, space, up arrow, or down arrow will open the focused menu. Once a menu is opened, pressing left and right arrows will switch between the two menus. Pressing escape will return focus to the title of the previously open menu. A new UI test attempts to select something from the menus using only the keyboard. It works on Linux (with toolkit_views) and on Windows. BUG=none TEST=New keyboard accessibility interactive ui test. Review URL: http://codereview.chromium.org/660323 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42498 0039d316-1c4b-4281-b951-d872f2087c98
* Tentative fix for geolocation test with iframes: loads frame one by one.bulach@chromium.org2010-03-241-15/+13
| | | | | | | | | | | | Mark as "flaky" to analyze how it behaves, will fully enable it once it's proven stable. Restructure the tests a bit in order to simplify the usage of mocks. TEST=geolocation_browsertest.cc Review URL: http://codereview.chromium.org/1081012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42495 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Fix browser side handling of moveTo by resizing the content area; ↵erg@chromium.org2010-03-241-1/+1
| | | | | | | | | | | | | | | | | not the window." This reverts commit 2ce3ea80b627f58acb97802b0cc182b3a2bdf809 (r40386). This seems to tickle some weird race condition where the renderer and the browser process disagree about the size of the window. I'm reverting this change as 38685 is scarier then 27365. TEST=none BUG=38785,27365 Review URL: http://codereview.chromium.org/1259004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42494 0039d316-1c4b-4281-b951-d872f2087c98
* History APIs that parse a time as a number of milliseconds need to allow ↵skerner@chromium.org2010-03-241-0/+13
| | | | | | | | | | | integer numbers. BUG=38994 TEST=ExtensionApiTest.FLAKY_History Review URL: http://codereview.chromium.org/1221001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42486 0039d316-1c4b-4281-b951-d872f2087c98
* Change chrome.experimental.history.search's first param to use 'text' for ↵skerner@chromium.org2010-03-243-16/+16
| | | | | | | | | | | text search. BUG=38995 TEST=ExtensionApiTest.FLAKY_History' Review URL: http://codereview.chromium.org/1102007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42482 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 42473 - Add a delegate to CookieMonster and broadcast notifications ↵dhollowa@chromium.org2010-03-241-1/+1
| | | | | | | | | | | | | | | | about changes to cookies. This change will allow implementing the experimental cookie extension API, specifically the cookies.onChanged event BUG=38398 TEST=net_unittests Review URL: http://codereview.chromium.org/1023004 TBR=jochen@chromium.org Review URL: http://codereview.chromium.org/1256003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42478 0039d316-1c4b-4281-b951-d872f2087c98
* Add a delegate to CookieMonster and broadcast notifications about changes to ↵jochen@chromium.org2010-03-241-1/+1
| | | | | | | | | | | | | cookies. This change will allow implementing the experimental cookie extension API, specifically the cookies.onChanged event BUG=38398 TEST=net_unittests Review URL: http://codereview.chromium.org/1023004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42473 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 42465 - Keyboard accessibility for the page and app menus.dmazzoni@chromium.org2010-03-247-168/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reverting because newly added Test*MenuKeyboardAccess tests fail on some of the Windows buildbots, and possibly a XP Perf regression. Works on Windows, and on Linux with toolkit_views. The goal is to make Chrome behave more like a standard Windows application, for users who rely on the keyboard and expect standard keyboard accelerators to work. Pressing F10, or pressing and releasing Alt, will set focus to the Page menu, as if it was the first item in a menu bar. Pressing enter, space, up arrow, or down arrow will open the focused menu. Once a menu is opened, pressing left and right arrows will switch between the two menus. Pressing escape will return focus to the title of the previously open menu. A new UI test attempts to select something from the menus using only the keyboard. It works on Linux (with toolkit_views) and on Windows. BUG=none TEST=New keyboard accessibility ui test. Review URL: http://codereview.chromium.org/660323 TBR=dmazzoni@chromium.org Review URL: http://codereview.chromium.org/1257003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42468 0039d316-1c4b-4281-b951-d872f2087c98
* Clear cookies, local storage and databases when an extension gets uninstalled.jochen@chromium.org2010-03-242-3/+31
| | | | | | | | | | BUG=27938 TEST=Unittest in extension_service_unitttest.cc Review URL: http://codereview.chromium.org/1095003 Patch from Mattias Nissler. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42467 0039d316-1c4b-4281-b951-d872f2087c98
* Keyboard accessibility for the page and app menus.dmazzoni@chromium.org2010-03-247-1/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | Works on Windows, and on Linux with toolkit_views. The goal is to make Chrome behave more like a standard Windows application, for users who rely on the keyboard and expect standard keyboard accelerators to work. Pressing F10, or pressing and releasing Alt, will set focus to the Page menu, as if it was the first item in a menu bar. Pressing enter, space, up arrow, or down arrow will open the focused menu. Once a menu is opened, pressing left and right arrows will switch between the two menus. Pressing escape will return focus to the title of the previously open menu. A new UI test attempts to select something from the menus using only the keyboard. It works on Linux (with toolkit_views) and on Windows. BUG=none TEST=New keyboard accessibility ui test. Review URL: http://codereview.chromium.org/660323 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42465 0039d316-1c4b-4281-b951-d872f2087c98
* basic browser tests for compact navigation bar.oshima@chromium.org2010-03-242-0/+9
| | | | | | | | | | | | | * Tests if Browser::ToggleCompactNavigationBar() turns on/off compact navigation bar and tool bar. * Tests if the accelerator works. BUG=http://crosbug.com/2028 TEST=new tests CompactNativationBarTest.TestBasic/TestAccelerator should pass. Review URL: http://codereview.chromium.org/1200001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42430 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r42426 - tests are failing because the WebKit LayoutTests directoriesdpranke@google.com2010-03-241-9/+7
| | | | | | | | | | | | | aren't checked out on the bots. We need to figure out how to deal with this since we don't want to keep expectations downstream if we can avoid it. BUG=none R=none TEST=bots stay green Review URL: http://codereview.chromium.org/1253002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42427 0039d316-1c4b-4281-b951-d872f2087c98
* Use upstream layout_test baselines since the downstream ones are going away.dpranke@google.com2010-03-241-7/+9
| | | | | | | | | | BUG=none TEST=bots stay green R=eroman@chromium.org Review URL: http://codereview.chromium.org/1214001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42426 0039d316-1c4b-4281-b951-d872f2087c98
* Add a few PyAuto tests for bookmarks.nirnimesh@chromium.org2010-03-244-0/+207
| | | | | | | | | | | | | | | The first two tests are from rohitbm and the rest from krisrs. testUnicodeStrings -- test bookmarks with unicode strings testSizes -- test bookmarks with different sized strings testAddingBookmarksToBarAndOther - add bookmarks to diff locations testAddingFoldersToBarAndOther -- add bookmark groups to diff locations testAddingFoldersWithChildrenToBarAndOther -- add bookmarks and groups to different locations Review URL: http://codereview.chromium.org/1191002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42417 0039d316-1c4b-4281-b951-d872f2087c98
* Mark all selenium tests as passing.tony@chromium.org2010-03-241-1/+0
| | | | | | | | | TBR=dglazkov BUG=38610 Review URL: http://codereview.chromium.org/1247001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42414 0039d316-1c4b-4281-b951-d872f2087c98
* Make it clear what last_sync_timestamp actually tracks. Updatenick@chromium.org2010-03-241-4/+4
| | | | | | | | | | | | | | | | last_sync_timestamp from the new_timestamp only, never from per-entry timestamps. Use what the server sends us to know whether or not there are more updates to fetch. Eliminate some unnecessarily complicated logic having to do with the # of updates returned -- that's always a red herring; with server-side filtering, it is indeed possible for 0 updates to be returned along with a new timestamp. BUG=37373 TEST=manual testing of 2 browser sync; unit tests. Review URL: http://codereview.chromium.org/1161006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42413 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 42366 - Allow TabContentsDelegate classes to specify whether InfoBars ↵joi@chromium.org2010-03-231-1/+0
| | | | | | | | | | | | | | | | are enabled. Allow ChromeFrame to pass infobar enabled parameter to ExternalTabContainer. BUG=2444936 Patch contributed by ericdingle@google.com Original review at http://codereview.chromium.org/890005 TBR=joi@chromium.org Review URL: http://codereview.chromium.org/1205001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42378 0039d316-1c4b-4281-b951-d872f2087c98
* Allow TabContentsDelegate classes to specify whether InfoBars are enabled.joi@chromium.org2010-03-231-0/+1
| | | | | | | | | | | Allow ChromeFrame to pass infobar enabled parameter to ExternalTabContainer. BUG=2444936 Patch contributed by ericdingle@google.com Original review at http://codereview.chromium.org/890005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42366 0039d316-1c4b-4281-b951-d872f2087c98
* Fix PyAuto crash when a script has multiple tests.nirnimesh@chromium.org2010-03-2314-103/+417
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL better maps C++ UITestSuite to python suite and C++ UITestBase to python testcase. All one-time initializations go in the suite while testcases are re-entrant now -- this is what fixes the crash. Also: - Cmdline flags to pyauto script (verbose, wait for attaching to debugger) - Establish the setup of sys.path, so that it's setup correctly and tests don't have to worry about it - Create facitlites for PYAUTO_TESTS files inside script dirs (say chrome/test/functional) which defines the tests to run. - Restructure such that pyauto scripts can be run standalone as well as using the pyauto.py script (like unittest.py). For example, a test could be fired in any of the below ways: # Run tests in a module ('bookmarks') python pyauto_functional.py bookmarks # Run tests in a test case ('bookmarks.BookmarksTest') python pyauto_functional.py bookmarks.BookmarksTest # Run a test ('bookmarks.BookmarksTest.testBasics') python pyauto_functional.py bookmarks.BookmarksTest.testBasics # Run directly from the test script python bookmarks.py python bookmarks.py bookmarks python bookmarks.py bookmarks.BookmarksTest python bookmarks.py bookmarks.BookmarksTest.testBasics BUG=32292 TEST=python chrome/test/functional/bookmarks.py Review URL: http://codereview.chromium.org/1126003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42350 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed the gtest filter for unit_tests on Mac under ThreadSanitizerglider@chromium.org2010-03-231-1/+1
| | | | | | | | | BUG=38889 TBR=timurrrr Review URL: http://codereview.chromium.org/1148008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42329 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enable the DB perf tests and lower the number of iterations perdumi@chromium.org2010-03-221-9/+25
| | | | | | | | | | | | test from 10 to 5, to make sure all tests finish in less than 10 minutes (seems to be a problem only on the Vista perf bot). TEST=none BUG=none Review URL: http://codereview.chromium.org/1089006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42284 0039d316-1c4b-4281-b951-d872f2087c98
* We had a problem where if chrome crashed on cros and was relauncheddavemoore@chromium.org2010-03-222-4/+14
| | | | | | | | | | | | | | | | | | | it would always run with the Default profile. This meant that two different users could see the same data...a big problem. We patched in the OS by deleting the profile directory each time but this is the right fix. When the session_manager reruns Chrome on a crash it will now pass a new flag (--login-user). Chrome uses this and ensures that the profile dir (specified by --login-profile) is mounted as an encrypted drive. If this flag isn't specified then Chrome uses the Default profile, but in incognito mode so no data is written. BUG=chromiumos:1967 TEST=Login to chromeos as user1, in a terminal kill the browser process, chrome relaunches, log into gmail, sign out (using menu or power button). Login as user2, kill browser process, chrome relaunches, go to gmail. Ensure that user1 isn't logged in. Review URL: http://codereview.chromium.org/1094009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42279 0039d316-1c4b-4281-b951-d872f2087c98
* Enable DOM paste for extensions with clipboard access.dcheng@chromium.org2010-03-221-0/+4
| | | | | | | | | BUG=none TEST=browser_tests.exe --gtest_filter=ExtensionApiTest.Clipboard Review URL: http://codereview.chromium.org/1121004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42264 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Keyboard accessibility for the page and app menus.", rev 42234 and ↵maruel@chromium.org2010-03-225-153/+0
| | | | | | | | | | 42236. TBR=dmazzoni Review URL: http://codereview.chromium.org/1158004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42239 0039d316-1c4b-4281-b951-d872f2087c98
* Keyboard accessibility for the page and app menus.dmazzoni@chromium.org2010-03-225-0/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | Works on Windows, and on Linux with toolkit_views. The goal is to make Chrome behave more like a standard Windows application, for users who rely on the keyboard and expect standard keyboard accelerators to work. Pressing F10, or pressing and releasing Alt, will set focus to the Page menu, as if it was the first item in a menu bar. Pressing enter, space, up arrow, or down arrow will open the focused menu. Once a menu is opened, pressing left and right arrows will switch between the two menus. Pressing escape will return focus to the title of the previously open menu. A new UI test attempts to select something from the menus using only the keyboard. It works on Linux (with toolkit_views) and on Windows. BUG=none TEST=New keyboard accessibility ui test. Review URL: http://codereview.chromium.org/660323 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42234 0039d316-1c4b-4281-b951-d872f2087c98
* Filtered out ExtensionTest.InitFromValueInvalid from being executed underglider@chromium.org2010-03-221-0/+3
| | | | | | | | | | | ThreadSanitizer on Mac BUG=38889 TBR=timurrrr Review URL: http://codereview.chromium.org/1111009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42219 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Keyboard accessibility for the page and app menus."maruel@chromium.org2010-03-225-157/+0
| | | | | | | | | | This reverts commit 42217. TBR=dmzazzoni Review URL: http://codereview.chromium.org/1154003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42218 0039d316-1c4b-4281-b951-d872f2087c98
* Keyboard accessibility for the page and app menus.dmazzoni@chromium.org2010-03-225-0/+157
| | | | | | | | | | | | | | | | | | | | | | | | | | Works on Windows, and on Linux with toolkit_views. The goal is to make Chrome behave more like a standard Windows application, for users who rely on the keyboard and expect standard keyboard accelerators to work. Pressing F10, or pressing and releasing Alt, will set focus to the Page menu, as if it was the first item in a menu bar. Pressing enter, space, up arrow, or down arrow will open the focused menu. Once a menu is opened, pressing left and right arrows will switch between the two menus. Pressing escape will return focus to the title of the previously open menu. A new UI test attempts to select something from the menus using only the keyboard. It works on Linux (with toolkit_views) and on Windows. BUG=none TEST=New keyboard accessibility ui test. Review URL: http://codereview.chromium.org/660323 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42217 0039d316-1c4b-4281-b951-d872f2087c98
* [GTTF] Reduce number of automation methods ending with WithTimeout.phajdan.jr@chromium.org2010-03-2217-451/+141
| | | | | | | | | | | | | | | | | | | | | They are just too easy to misuse. People started inventing their own hardcoded timeouts all over the place. Also, the is_timeout return parameter was not checked consistently. Additionally, some calls actually had no timeout at all, making hangs possible. This change also removes useless DLOG statements. We should get the required info from the ASSERT/EXPECT macros in test code, which is quite well checked by WARN_UNUSED_RESULT. TEST=all ui-based BUG=none Review URL: http://codereview.chromium.org/1076005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42213 0039d316-1c4b-4281-b951-d872f2087c98
* Adds browser tests exercising multiple iframes for geolocation.bulach@chromium.org2010-03-222-2/+24
| | | | | | | | | | Adds a disabled test waiting for rolling https://bugs.webkit.org/show_bug.cgi?id=36315 TEST=geolocation_browsertest.cc Review URL: http://codereview.chromium.org/1134001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42212 0039d316-1c4b-4281-b951-d872f2087c98
* When testing, we don't want to know about 'component' or 'external'joi@chromium.org2010-03-201-1/+8
| | | | | | | | | | | | extensions, and if there are loaded extensions we probably loaded them explicitly (and got a notification thereof) so don't list them either. BUG=none TEST=none Review URL: http://codereview.chromium.org/1081008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42189 0039d316-1c4b-4281-b951-d872f2087c98
* Move RTL related functions from app/l10n_util to base/i18n/rtlben@chromium.org2010-03-201-2/+3
| | | | | | | | | | TBR=darin BUG=none TEST=none Review URL: http://codereview.chromium.org/1073005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42182 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r42156, r42157, r42160. Allow dynamic switching in and out of ↵thestig@chromium.org2010-03-201-1/+0
| | | | | | | | | | | | sidetabs mode. Reliability bot and Linux CrOS browser_tests all had crashes in ~TabStrip. BUG=none TEST=none Review URL: http://codereview.chromium.org/1141005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42176 0039d316-1c4b-4281-b951-d872f2087c98
* Disable new WorkerTest.SharedWorkerInIframe test. It's failing in Valgrind.thestig@chromium.org2010-03-191-0/+1
| | | | | | | | BUG=38575 TEST=Valgrind Linux goes green. Review URL: http://codereview.chromium.org/1096007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42169 0039d316-1c4b-4281-b951-d872f2087c98
* Allow dynamic switching in and out of sidetabs mode.ben@chromium.org2010-03-191-0/+1
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/1001003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42156 0039d316-1c4b-4281-b951-d872f2087c98
* Resubmit 1025006: Refactor app-related manifest propertiesaa@chromium.org2010-03-1927-7/+213
| | | | | | | | so that they don't include the name 'app'. TBR=erikkay@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42146 0039d316-1c4b-4281-b951-d872f2087c98
* Improve the integration test harness by using the max_local_timestamptim@chromium.org2010-03-193-93/+66
| | | | | | | | | | | from the sync engine rather than waiting for "a couple syncs" to happen before declaring sync "done". BUG=37351 Review URL: http://codereview.chromium.org/1042008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42134 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 42115 - Disable BrowserEncodingTest.TestEncodingAliasMapping as it's ↵jhawkins@chromium.org2010-03-191-3/+0
| | | | | | | | | | | | | | failing under Valgrind. TBR=thestig BUG=38657 TEST=none Review URL: http://codereview.chromium.org/1105005 TBR=jhawkins@chromium.org Review URL: http://codereview.chromium.org/1124004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42132 0039d316-1c4b-4281-b951-d872f2087c98
* Disable BrowserEncodingTest.TestEncodingAliasMapping as it's failing under ↵jhawkins@chromium.org2010-03-191-0/+3
| | | | | | | | | | | Valgrind. TBR=thestig BUG=38657 TEST=none Review URL: http://codereview.chromium.org/1105005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42115 0039d316-1c4b-4281-b951-d872f2087c98
* Disable BookmarkAllTabsControllerTest.BookmarkAllTabs under Valgrind, as it ↵jhawkins@chromium.org2010-03-191-0/+2
| | | | | | | | | | | is consistently failing. TBR=thestig BUG=38655 TEST=none Review URL: http://codereview.chromium.org/1147002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42114 0039d316-1c4b-4281-b951-d872f2087c98
* [GTTF] Make automation timeouts more sane.phajdan.jr@chromium.org2010-03-193-12/+8
| | | | | | | | | | | | | | | | | | Do not expose command execution timeout outside ui_test.cc. This way people have less timeouts to choose from, which leaves less space for confusion. The option to manipulate the command execution timeout is still available, because it's still used and makes sense. Also updated misleading comments and names in ui_test.cc. TEST=ui_tests BUG=none Review URL: http://codereview.chromium.org/1078003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42112 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 42091 - Refactor apprelated manifest properties so that they don'tandybons@chromium.org2010-03-1926-211/+0
| | | | | | | | | | | | | | | include the name 'app'. I think these will be useful for normal extensions, too. Also extract an ExtensionExtent class out of Extension. I think this will be useful for passing by value to the IO thread. Review URL: http://codereview.chromium.org/1025006 TBR=aa@chromium.org Review URL: http://codereview.chromium.org/1120005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42104 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor app-related manifest properties so that they don'taa@chromium.org2010-03-1926-0/+211
| | | | | | | | | | | | include the name 'app'. I think these will be useful for normal extensions, too. Also extract an ExtensionExtent class out of Extension. I think this will be useful for passing by value to the IO thread. Review URL: http://codereview.chromium.org/1025006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42091 0039d316-1c4b-4281-b951-d872f2087c98
* Mark selenium test as failing to get the bot green.tony@chromium.org2010-03-191-0/+1
| | | | | | | | | | BUG=38610 TBR=thestig Review URL: http://codereview.chromium.org/1151002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42086 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-17 15:15:29 +0000