summaryrefslogtreecommitdiffstats
path: root/chrome/test/ui
Commit message (Collapse)AuthorAgeFilesLines
* GTK Theme: Add startup tests for gtk themes.erg@google.com2009-08-182-1/+5
| | | | | | | | http://crbug.com/19376 Review URL: http://codereview.chromium.org/173010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23646 0039d316-1c4b-4281-b951-d872f2087c98
* Fix startup tests with complex theme.mirandac@chromium.org2009-08-152-1/+44
| | | | | | | | | | BUG= http://crbug.com/18767 TEST= none Review URL: http://codereview.chromium.org/165478 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23524 0039d316-1c4b-4281-b951-d872f2087c98
* linux: More automation porting.estade@chromium.org2009-08-131-6/+5
| | | | | | | | | | I have verified that this is working on Linux, but still have yet to enable any new automated tests. Baby steps. BUG=19076 Review URL: http://codereview.chromium.org/164446 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23386 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting 23313.mirandac@chromium.org2009-08-132-42/+1
| | | | | | Review URL: http://codereview.chromium.org/165463 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23314 0039d316-1c4b-4281-b951-d872f2087c98
* Enable StartupTest.PerfColdComplexTheme, and add rewriting of Preference ↵mirandac@chromium.org2009-08-132-1/+42
| | | | | | | | | | | file to ensure that the images are picked up for the complex theme tests. BUG= http://crbug.com/18767 TEST= none Review URL: http://codereview.chromium.org/164402 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23313 0039d316-1c4b-4281-b951-d872f2087c98
* Test startup of new tab page with a complex theme.mirandac@chromium.org2009-08-102-0/+29
| | | | | | | | | BUG= http://crbug.com/18767 TEST= none Review URL: http://codereview.chromium.org/165168 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22925 0039d316-1c4b-4281-b951-d872f2087c98
* Run the DOM Storage layout tests in the UI test framework since the test ↵jorlow@chromium.org2009-08-052-0/+275
| | | | | | | | | | | | | | | shell doesn't hit very much of the new code. I still plan to write unit tests and we're still goign to enable the layout tests in test shell, but this is still a good way for us to test the full stack ASAP. Workers has used this technique for a while now. This CL factors out the layout test running code from the workers ui test and moves arounds directories a bit so not everything is in the "workers" directory. Doing this via a v8 extension is the right way to go long term, but I ran into a couple snags, so I think this is a good first step. TEST=none BUG=none Review URL: http://codereview.chromium.org/159720 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22466 0039d316-1c4b-4281-b951-d872f2087c98
* Remove duplication of DieFileDie, and move it to proper location.phajdan.jr@chromium.org2009-07-302-22/+1
| | | | | | | | | TEST=none http://crbug.com/18085 Review URL: http://codereview.chromium.org/159658 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22103 0039d316-1c4b-4281-b951-d872f2087c98
* Increase timeouts in DieFileDie in hope to further reduce the flakiness.phajdan.jr@chromium.org2009-07-291-2/+2
| | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/159548 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21958 0039d316-1c4b-4281-b951-d872f2087c98
* Disable the tips service by default.arv@google.com2009-07-251-1/+2
| | | | | | | | | | | | | Update the UI to not say tips or recommendations. BUG=None TEST=Starting chrome should not show any tips byt default Review URL: http://codereview.chromium.org/160138 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21615 0039d316-1c4b-4281-b951-d872f2087c98
* Disable NPAPIVisiblePluginTester.OpenPopupWindowWithPlugin, which is flaky.yuzo@chromium.org2009-07-241-1/+2
| | | | | | | | | | BUG=17645 TEST=none Review URL: http://codereview.chromium.org/159333 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21514 0039d316-1c4b-4281-b951-d872f2087c98
* Turn backend tip service on by default.mirandac@chromium.org2009-07-121-0/+2
| | | | | | | | | | BUG= none. TEST= New NTP should come up with a default title in Tips and Suggestions box, then be loaded with actual data from popgadget. Review URL: http://codereview.chromium.org/149255 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20466 0039d316-1c4b-4281-b951-d872f2087c98
* Adding command line switch to run UI test in parallel.huanr@chromium.org2009-07-102-0/+38
| | | | | | | | | BUG=16006 TEST=none Review URL: http://codereview.chromium.org/149445 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20435 0039d316-1c4b-4281-b951-d872f2087c98
* Fix NPAPIIncognitoTester.PrivateEnabledjam@chromium.org2009-07-071-1/+1
| | | | | | | BUG=16149 Review URL: http://codereview.chromium.org/155182 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20099 0039d316-1c4b-4281-b951-d872f2087c98
* Sprinkle some defensiveness into the UI tests so that they don't explode if ↵stuartmorgan@chromium.org2009-07-073-8/+15
| | | | | | | | | | the proxy doesn't respond (e.g., due to a timeout). BUG=none TEST=Hopefully the Mac valgrind bots will more reliably run all their tests (although there are likely more issues like this lurking). Review URL: http://codereview.chromium.org/149281 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20096 0039d316-1c4b-4281-b951-d872f2087c98
* Linux build fixdimich@google.com2009-06-241-1/+1
| | | | | | | TBR=thakis Review URL: http://codereview.chromium.org/146061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19085 0039d316-1c4b-4281-b951-d872f2087c98
* Add ability to start/stop http server to ui_tests. This will be used to run ↵dimich@google.com2009-06-232-0/+79
| | | | | | | | | | Workers+XHR layout tests which is impossible to run in test_shell. BUG=none TEST=none Review URL: http://codereview.chromium.org/125283 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19082 0039d316-1c4b-4281-b951-d872f2087c98
* Add a switch to allow longer shutdown timeouts, since quitting under ↵stuartmorgan@chromium.org2009-06-192-2/+15
| | | | | | | | | | valgrind is very slow on the Mac. BUG=none TEST=Most/all of the UI tests should pass on the Mac when run under valgrind. Review URL: http://codereview.chromium.org/140008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18849 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 18512 - Revert 18373 Consider a redirect following user gesture as ↵laforge@chromium.org2009-06-161-2/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | userinitiated in maintaining navigation entries. Also, ignore redirect or machineinitiated new subframe navigations. The current code treats all redirects as machineinitiated in processing navigation to a new page (to fix Bugs 9663 and 10531). This is not always appropriate, because some sites, e.g., www.google.com/ig, use redirect to implement userinitiated navigation (Bug 11896). This change assumes that a machineinitiated redirect happens within 300ms since the last document load was completed, while a userinitiated one happens later. This assumption is not always correct, e.g., a user may cause transition within 300ms. But I cannot think of any better ways to tell if a redirect is machine initiated or userinitiated. I believe this change works good enough, at least better than the status quo. Review URL: http://codereview.chromium.org/115919 TEST=Open http://www.hp.com and observe it redirects to http://www.hp.com/#Product . Hit Back button and observe the former URL is not visited. Open http://www.google.com/ig and click tabs inside the page, and try hitting Back and Forward to see if the navigation is right. Open http://www.google.com/codesearch, search for something, click on a result item, and try hitting Back. BUG=11896,12820 TBR=yuzo@chromium.org Review URL: http://codereview.chromium.org/125202 TBR=laforge@chromium.org Review URL: http://codereview.chromium.org/126221 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18522 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 18373 - Consider a redirect following user gesture as userinitiated ↵laforge@chromium.org2009-06-161-61/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in maintaining navigation entries. Also, ignore redirect or machineinitiated new subframe navigations. The current code treats all redirects as machineinitiated in processing navigation to a new page (to fix Bugs 9663 and 10531). This is not always appropriate, because some sites, e.g., www.google.com/ig, use redirect to implement userinitiated navigation (Bug 11896). This change assumes that a machineinitiated redirect happens within 300ms since the last document load was completed, while a userinitiated one happens later. This assumption is not always correct, e.g., a user may cause transition within 300ms. But I cannot think of any better ways to tell if a redirect is machine initiated or userinitiated. I believe this change works good enough, at least better than the status quo. Review URL: http://codereview.chromium.org/115919 TEST=Open http://www.hp.com and observe it redirects to http://www.hp.com/#Product . Hit Back button and observe the former URL is not visited. Open http://www.google.com/ig and click tabs inside the page, and try hitting Back and Forward to see if the navigation is right. Open http://www.google.com/codesearch, search for something, click on a result item, and try hitting Back. BUG=11896,12820 TBR=yuzo@chromium.org Review URL: http://codereview.chromium.org/125202 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18512 0039d316-1c4b-4281-b951-d872f2087c98
* Consider a redirect following user gesture as user-initiated in maintainingyuzo@chromium.org2009-06-151-2/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | navigation entries. Also, ignore redirect- or machine-initiated- new subframe navigations. The current code treats all redirects as machine-initiated in processing navigation to a new page (to fix Bugs 9663 and 10531). This is not always appropriate, because some sites, e.g., www.google.com/ig, use redirect to implement user-initiated navigation (Bug 11896). This change assumes that a machine-initiated redirect happens within 300ms since the last document load was completed, while a user-initiated one happens later. This assumption is not always correct, e.g., a user may cause transition within 300ms. But I cannot think of any better ways to tell if a redirect is machine- initiated or user-initiated. I believe this change works good enough, at least better than the status quo. Review URL: http://codereview.chromium.org/115919 TEST=Open http://www.hp.com and observe it redirects to http://www.hp.com/#Product . Hit Back button and observe the former URL is not visited. Open http://www.google.com/ig and click tabs inside the page, and try hitting Back and Forward to see if the navigation is right. Open http://www.google.com/codesearch, search for something, click on a result item, and try hitting Back. BUG=11896,12820 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18373 0039d316-1c4b-4281-b951-d872f2087c98
* Compile sunspider on mac and linux.thomasvl@chromium.org2009-06-111-2/+8
| | | | | | Review URL: http://codereview.chromium.org/126003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18201 0039d316-1c4b-4281-b951-d872f2087c98
* Enabled the v8 benchmark tests on mac/linux.thomasvl@chromium.org2009-06-111-2/+8
| | | | | | Review URL: http://codereview.chromium.org/122045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18191 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: Remove legacy InspectorController UI tests.pfeldman@chromium.org2009-06-101-50/+0
| | | | | | | | BUG=4655 Review URL: http://codereview.chromium.org/119415 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18048 0039d316-1c4b-4281-b951-d872f2087c98
* Remove checked-in .vcproj files that have been converted to gyp.sgk@google.com2009-06-101-620/+0
| | | | | | | | BUG=none TEST=successful build Review URL: http://codereview.chromium.org/119411 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18044 0039d316-1c4b-4281-b951-d872f2087c98
* <!doctype html public '-//w3c//dtd html 4.0 ↵willchan@chromium.org2009-06-101-4/+0
| | | | | | | | transitional//en'><html><head><META HTTP-EQUIV='Refresh' CONTENT='0;URL=http://www.orkut.com'></head><body>You are being redirected <a href='http://www.orkut.com'>http://www.orkut.com</a>.</body></html> Review URL: http://codereview.chromium.org/118418 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18010 0039d316-1c4b-4281-b951-d872f2087c98
* ipc: use strings, not wstrings for channel ids.evan@chromium.org2009-06-041-2/+2
| | | | | | | | | | They're ASCII anyway. TEST=covered by existing tests Review URL: http://codereview.chromium.org/119131 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17682 0039d316-1c4b-4281-b951-d872f2087c98
* Move download shelf from per-tab to per-window. Also disable auto-hiding ofthakis@chromium.org2009-06-042-8/+29
| | | | | | | | | | | | | | the shelf. BUG=9025 TEST=Download file in one tab, open new tab, and check that download shelf is still open. Also try the shelf's close button and the "show all downloads" link. When saving a file, the download animation should not show up. Review URL: http://codereview.chromium.org/115740 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17595 0039d316-1c4b-4281-b951-d872f2087c98
* Fix browser hang due to plugin deadlockamit@chromium.org2009-06-031-0/+13
| | | | | | | | | | | | | | | | | | | | | This involves two plugin instances with second instance making sync calls to the renderer while the first one is still servicing an incoming sync request. Our logic to unblock the renderer during the sync call fails since the 'in_dispatch_' counter is maintained per plugin channel (each plugin instance uses its own separate channel). Making 'in_dispatch_' counter static member of PluginChannelBase fixes this deadlock. Added a new NPAPI UI test for this scenario. BUG=12624 TEST=MultipleInstancesSyncCalls Review URL: http://codereview.chromium.org/119052 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17492 0039d316-1c4b-4281-b951-d872f2087c98
* Some UI tests would fail on some boxes as these tests have specific ↵jcampan@chromium.org2009-06-011-0/+4
| | | | | | | | | | | | | expectations in term of how many and what kind of info-bars are showing, and the default browser check would add an extra info-bar. This CL adds a switch that disables the default browser check on start-up and makes the UI tests specify that switch. BUG=13064 TEST=Run the UI tests. Review URL: http://codereview.chromium.org/112081 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17336 0039d316-1c4b-4281-b951-d872f2087c98
* Make automation proxy objects to ref_counted. That allows to process async ↵stoyan@chromium.org2009-05-289-28/+32
| | | | | | | | | | | notifications directly in channel background thread. Add support for listener-less ChannelProxy. BUG=none TEST=none Review URL: http://codereview.chromium.org/113722 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17093 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r16903 that causes reliability crash spike.huanr@chromium.org2009-05-262-26/+6
| | | | | | Review URL: http://codereview.chromium.org/113865 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16925 0039d316-1c4b-4281-b951-d872f2087c98
* Run ui_tests (and other tests based on UITest) with --no-first-run to avoidmark@chromium.org2009-05-261-0/+3
| | | | | | | first-run dialogs. Review URL: http://codereview.chromium.org/113858 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16922 0039d316-1c4b-4281-b951-d872f2087c98
* Retry r15294. The previous two tries causedhuanr@chromium.org2009-05-262-6/+26
| | | | | | | | | | | | | | | | | | | | | | | | a crash spike in ChromeBot. The crash spike is caused by some observers don't remove themselves from notification list after being deleted. The clean up done by pkasting may fix this so I am give this change another try. TEST=None BUG=None Original change description: Close browser window synchronously during UI test tear down. This is an effor to reduce random failure due to browser crash with multiple window open during shutdown. Review URL: http://codereview.chromium.org/113856 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16903 0039d316-1c4b-4281-b951-d872f2087c98
* We need to add UI tests to test workers after we switch to ↵jianli@chromium.org2009-05-261-0/+8
| | | | | | | | | | | process-per-worker model and remove uses of V8 lockers. Due to this, we can not run any worker layout test that starts multiple workers because we load V8 instance in DLL in test shell. To cover this deficiency, we need to add UI tests to test multiple workers. BUG=12554 TEST=none Review URL: http://codereview.chromium.org/115731 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16890 0039d316-1c4b-4281-b951-d872f2087c98
* Committing issue 113734 for Joi.tommi@chromium.org2009-05-231-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | Description: Make sure extension_uitest.cc is actually built (my bad - got confused about the whole .gyp vs. .sln thing). Also, to get things building now that extension_uitest.cc is built, shuffle the extension automation constants around so they end up in the browser library (I didn't realize the UI tests are already linking with that, and the linker was bringing in the automation_extension_function.obj file ended up causing lots of unresolved linker problems). Note that this did build the other day when I submitted the file originally, but it must have been essentially a fluke that the linker chose the other .obj file to get the constants. BUG=none TEST=none Original issue: http://codereview.chromium.org/113734 Review URL: http://codereview.chromium.org/113788 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16835 0039d316-1c4b-4281-b951-d872f2087c98
* Fix some incorrect timeout settings in ui test.huanr@chromium.org2009-05-221-7/+7
| | | | | | Review URL: http://codereview.chromium.org/113673 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16766 0039d316-1c4b-4281-b951-d872f2087c98
* Enable IDC_CLOSE_WINDOW on linux.estade@chromium.org2009-05-201-0/+4
| | | | | | | | I filed http://crbug.com/12334 to fix the ifdefed-out block in ui_test.cc. Review URL: http://codereview.chromium.org/113655 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16526 0039d316-1c4b-4281-b951-d872f2087c98
* Displaying consecutive alerts from plugins should not hang the browser. The ↵ananta@chromium.org2009-05-151-0/+9
| | | | | | | | | | | | | | | | | | plugins display alerts via the NPN_Evaluate API. The browser signals an event handle to ensure that the plugin starts peeking for messages while waiting for the NPN_Evaluate call to return. When the dialog is dismissed by the user, windows does send some messages to the plugin window underneath, like activation messages, etc. These don't get dispatched as the event is reset when the dialog is dismissed, i.e. much before the window is actually destroyed. The fix is to reset the event handle after the window is actually destroyed. To achieve this I added an OnClose virtual function to the DialogDelegate interface, which is overridden by the JavascriptMessageBoxDialog class which eventually ensures that the event is reset. This fixes http://code.google.com/p/chromium/issues/detail?id=10799 I updated the AlertInWindowMessage npapi test to display two alerts instead of one. Bug=10799 Review URL: http://codereview.chromium.org/113464 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16172 0039d316-1c4b-4281-b951-d872f2087c98
* Make WidgetWin redraw child windows that are in a different process ↵jam@chromium.org2009-05-141-0/+22
| | | | | | | | | | | asynchronously. This helps with jank (i.e. bug 11701 which I couldn't repro with this) and also with deadlocks (fixes 11421 for painting). BUG=11421,11701 Review URL: http://codereview.chromium.org/115216 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16027 0039d316-1c4b-4281-b951-d872f2087c98
* This is the successor to http://codereview.chromium.org/67150maruel@chromium.org2009-05-131-4/+31
| | | | | | | | | | | | | | | | | | | | | Make forward/backward navigation work even when redirection is involved. Currently, Chrome tries to go back to the page immediately before the current one. This doesn't work if the current page was visited by redirection; redirection just occurs again. With this change, Chrome first tries to find the redirection source of the current page and then to go back to the page before the source. BUG=9663,10531 Tested: unit_tests, ui_tests, manually. Patch contributed by Yuzo Fujishima <yuzo@google.com> Review: http://codereview.chromium.org/100245 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15950 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r15693. The crash spike still exists.huanr@chromium.org2009-05-092-26/+6
| | | | | | Review URL: http://codereview.chromium.org/113181 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15713 0039d316-1c4b-4281-b951-d872f2087c98
* Retry r15294. The previous check in exposed bug 11659huanr@chromium.org2009-05-082-6/+26
| | | | | | | | | | | | | | | and caused a crash spike in ChromeBot. Original change description: Close browser window synchronously during UI test tear down. This is an effor to reduce random failure due to browser crash with multiple window open during shutdown. Review URL: http://codereview.chromium.org/113171 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15693 0039d316-1c4b-4281-b951-d872f2087c98
* Adding a test for a testing that the bug http://crbug.com/9791 is really fixed.jcampan@chromium.org2009-05-061-28/+20
| | | | | | | | | | | | Removing the interstitial UI tests: they test the same functionalities as the unit-tests but are flacky and most of them have been disabled (a new unit-test for the "show interstitial and then navigate back" has been added to cover for a case that the unit-tests were not covering). TEST=Run the unit-tests. BUG=6729,3327 Review URL: http://codereview.chromium.org/109038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15416 0039d316-1c4b-4281-b951-d872f2087c98
* Uncomment the crash checks in UITest::TearDown since CountFilesCreatedAfterevan@chromium.org2009-05-061-6/+0
| | | | | | | | | | | has been implemented for POSIX environment. BUG=9833 Review URL: http://codereview.chromium.org/99360 Patch from Albert Bachand <albertb@google.com>. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15364 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r15294 that causes crash spike in chromebot.huanr@chromium.org2009-05-052-26/+6
| | | | | | Review URL: http://codereview.chromium.org/108023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15305 0039d316-1c4b-4281-b951-d872f2087c98
* Close browser window synchronously during UI testhuanr@chromium.org2009-05-052-6/+26
| | | | | | | | | | tear down. This is an effor to reduce random failure due to browser crash with multiple window open during shutdown. Review URL: http://codereview.chromium.org/100363 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15294 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: enable omni box ui test and automation proxy ui test.estade@chromium.org2009-05-051-3/+3
| | | | | | | | Enable a lot of (already essentially working) automation code along the way. Review URL: http://codereview.chromium.org/100278 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15258 0039d316-1c4b-4281-b951-d872f2087c98
* Yet more deprecation of the wstring version of PathService::Get() for UI tests.thestig@chromium.org2009-05-026-20/+19
| | | | | | Review URL: http://codereview.chromium.org/99298 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15127 0039d316-1c4b-4281-b951-d872f2087c98
* Fix BROWSER_WRAPPER env for ui tests so it works with commandstc@google.com2009-05-011-8/+4
| | | | | | | | | | longer than a single token. This lets me do things like BROWSER_WRAPPER='xterm -e gdb --args' ui_tests Review URL: http://codereview.chromium.org/99296 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15106 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-31 12:35:13 +0000