summaryrefslogtreecommitdiffstats
path: root/chrome/app/chrome_main_uitest.cc
Commit message (Collapse)AuthorAgeFilesLines
* Removing references to off the record in comments and log messages.akalin@chromium.org2011-03-081-1/+1
| | | | | | | | | | | Original patch by vipul.bhasin@gmail.com. BUG=3333 TEST=None Review URL: http://codereview.chromium.org/6625076 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77331 0039d316-1c4b-4281-b951-d872f2087c98
* Fix "chrome --incognito <URL>" opening in non-incognito window (or vice-versa).mattm@chromium.org2010-11-161-0/+63
| | | | | | | | | BUG=9636 TEST=ui_tests Review URL: http://codereview.chromium.org/4873004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66302 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
* GTTF: Remove flaky and/or useless UI tests.phajdan.jr@chromium.org2010-10-191-31/+1
| | | | | | | | | | | | | | | | | An example of a flake: ChromeMainTest.AppLaunch: c:\b\slave\win\build\src\chrome\app\chrome_main_uitest.cc(28): error: Value of: UITest::GetBrowserProcessCount() Actual: 3 Expected: 2 BUG=none TEST=ui_tests Review URL: http://codereview.chromium.org/3796009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63033 0039d316-1c4b-4281-b951-d872f2087c98
* ifdef out tests that don't apply to the Macstuartmorgan@chromium.org2010-09-231-9/+6
| | | | | | | | | | | 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
* CommandLine: eliminate wstring-accepting AppendLooseValueevan@chromium.org2010-08-131-1/+1
| | | | | | | | 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
* Cleanup: remove use_existing_browser infrastructure from ui_test.phajdan.jr@chromium.org2010-07-031-2/+0
| | | | | | | | | | | It was Windows-only, probably broken, and unused. BUG=46135 TEST=ui_tests Review URL: http://codereview.chromium.org/2859042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51602 0039d316-1c4b-4281-b951-d872f2087c98
* Compile all the chrome_test UI tests on the Macstuartmorgan@chromium.org2010-05-271-0/+9
| | | | | | | | | | | Removes the last of the ui test exceptions on the Mac, disabling a couple of tests as necessary to keep things green. BUG=45108,45243 TEST=Tests run Review URL: http://codereview.chromium.org/2234007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48447 0039d316-1c4b-4281-b951-d872f2087c98
* [GTTF] Reduce number of automation methods ending with WithTimeout.phajdan.jr@chromium.org2010-03-221-1/+1
| | | | | | | | | | | | | | | | | | | | | 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
* Lazy AppLauncher creation to make tests stable.oshima@chromium.org2010-03-051-5/+1
| | | | | | | | | | | | | | | | | There seems to be a timing issue in renderer deletion and io thread deletion, and the resource that has to be deleted before io thread are not deleted by the time io thread is deleted. Since this will soon be changed, i just chagned this to be created on demand for now. This also reverts commit dd6c4ab11002a308bf8eede36bb632e95d3a1382. TBR=sky@chromium.org BUG=32641 TEST=none Review URL: http://codereview.chromium.org/669196 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40780 0039d316-1c4b-4281-b951-d872f2087c98
* Fixing a comment.oshima@chromium.org2010-03-041-1/+1
| | | | | | | | | | TBR=sky@chromium.org BUG=none TEST=none Review URL: http://codereview.chromium.org/669094 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40668 0039d316-1c4b-4281-b951-d872f2087c98
* ui_tests fixoshima@chromium.org2010-03-041-1/+5
| | | | | | | | | BUG=none TEST=ui_tests should cycle green Review URL: http://codereview.chromium.org/669093 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40665 0039d316-1c4b-4281-b951-d872f2087c98
* Remove deprecated CommandLine(std::wstring) ctor.evan@chromium.org2009-10-261-3/+3
| | | | | | | | | | | Add a ctor for creating a CommandLine for carrying arguments; convert all the users to either that or the FilePath version. BUG=24672 Review URL: http://codereview.chromium.org/329017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30117 0039d316-1c4b-4281-b951-d872f2087c98
* Avoid an automation call which may induce flakiness in some tests.phajdan.jr@chromium.org2009-09-011-2/+1
| | | | | | | | | | | After a change in another place this change is now safe to make. TEST=Covered by ui_tests. BUG=none Review URL: http://codereview.chromium.org/173650 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25098 0039d316-1c4b-4281-b951-d872f2087c98
* More correctly run the second browser in ChromeMainTest.phajdan.jr@chromium.org2009-08-311-2/+2
| | | | | | | | | | | | | | - wait for the second browser process to finish - only initialize user dir once Will it kill flakiness? Who knows. TEST=none http://crbug.com/20546 Review URL: http://codereview.chromium.org/181016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24902 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: Add support for chrooted renderers.agl@chromium.org2009-06-151-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://code.google.com/p/chromium/wiki/LinuxSandboxIPC Without filesystem access from the renderers, we need another way of dealing with fontconfig and font loading. This add support for: * An "SBX_D" environment variable in the renderers which is used to signal the end of dynamic linking so that the chroot can be enforced. * A sandbox_host process, running outside the sandbox, to deal with fontconfig requests from the renderers. See the wiki page for the reasoning behind making it a separate process. * A new, custom SkFontHost for Skia. Because this is Chrome specific, it will live outside the upstream Skia tree. This FontHost can be configured either to drive fontconfig directly (for the browser process and for any unsandboxed renderers) or to use an IPC system. Since the same SkFontHost has to be linked into both the browser and renderer (they are the same binary), this switch has to be made at run time. Sandbox IPC calls are rare (a couple of dozen at page load time) and add about 50us of overhead for each call. (Reland of r17575 which was reverted in r17577) http://codereview.chromium.org/112074 BUG=8081 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18405 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: refactor zygote supportagl@chromium.org2009-06-121-0/+5
| | | | | | | | | | | | | | | | | | | http://code.google.com/p/chromium/wiki/LinuxZygote * Move Chrome specific bits out of base * Move away from the idea of reserved file descriptors (which don't really work with zygotes) * Load resources before forking renderers (means that we don't need communication between the zygote process and the renderers) * Make sure that gdb works against the browser again * Make sure that we have different ASLR between the renderers and the browser. http://codereview.chromium.org/119335 (This is a reland. First landed in r18109, reverted in r18112.) git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18291 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 18109, 18111: Windows UI tests failed.agl@chromium.org2009-06-101-5/+0
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18112 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: refactor zygote supportagl@chromium.org2009-06-101-0/+5
| | | | | | | | | | | | | | | | | | http://code.google.com/p/chromium/wiki/LinuxZygote * Move Chrome specific bits out of base * Move away from the idea of reserved file descriptors (which don't really work with zygotes) * Load resources before forking renderers (means that we don't need communication between the zygote process and the renderers) * Make sure that gdb works against the browser again * Make sure that we have different ASLR between the renderers and the browser. http://codereview.chromium.org/119335 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18109 0039d316-1c4b-4281-b951-d872f2087c98
* Yet more deprecation of the wstring version of PathService::Get() for UI tests.thestig@chromium.org2009-05-021-7/+3
| | | | | | Review URL: http://codereview.chromium.org/99298 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15127 0039d316-1c4b-4281-b951-d872f2087c98
* Make SecondLaunch UI test not-flaky by using more reliablephajdan.jr@chromium.org2009-03-091-6/+2
| | | | | | | | | | automation calls. BUG=5671 Review URL: http://codereview.chromium.org/40301 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11259 0039d316-1c4b-4281-b951-d872f2087c98
* Add regression test for bug 7900 and necessary infrastructure.phajdan.jr@chromium.org2009-03-091-1/+22
| | | | | | | | | | | | The test simulates following scenario: user opens a local html page with Chrome when a browser instance is already running. The new Chrome process should notify the existing process about new page and exit. Bug 7900 broke this behavior causing the new process to crash. I verified that the ui_tests infrastructure would catch this crash and cause the test to fail. BUG=7900, 8056 Review URL: http://codereview.chromium.org/39257 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11247 0039d316-1c4b-4281-b951-d872f2087c98
* Disable the SecondLaunch test. It fails all the timensylvain@chromium.org2009-02-041-1/+2
| | | | | | | | | now. See bug 5671 Review URL: http://codereview.chromium.org/21046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9137 0039d316-1c4b-4281-b951-d872f2087c98
* Revert my change to get the tree green. Not sure why the tests became ↵jam@chromium.org2009-02-041-1/+1
| | | | | | | | | | flaky. I'll try to check them in again but in smaller chunks tomorrow. TBR=mpcomplete Review URL: http://codereview.chromium.org/21039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9132 0039d316-1c4b-4281-b951-d872f2087c98
* Disable SecondLaunch which started failing after I did a clean build.jam@chromium.org2009-02-041-1/+1
| | | | | | | | I verified that this was broken before my changes by syncing to r9122. Review URL: http://codereview.chromium.org/21036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9130 0039d316-1c4b-4281-b951-d872f2087c98
* Fix SecondLaunch unit test.evan@chromium.org2009-01-211-1/+1
| | | | | | | | | BUG=6722 Review URL: http://codereview.chromium.org/18472 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8410 0039d316-1c4b-4281-b951-d872f2087c98
* disable test\ntc@google.com2009-01-211-1/+1
| | | | | | | | | | disable SecondLaunch. This looks command line related. tbr=evan Review URL: http://codereview.chromium.org/18617 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8369 0039d316-1c4b-4281-b951-d872f2087c98
* Make CommandLine into a normal object, with some statics for getting at the ↵evan@chromium.org2009-01-211-1/+1
| | | | | | | | | | | current process's command line. One explicit goal of this change is to *not* deal with the string/wstring issues at the API on POSIX; the functions are the same as before, which means they remain as broken as before. (I did try to fix the internals, though, so migrating the callers is now possible by adding platform-appropriate hooks.) Review URL: http://codereview.chromium.org/18248 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8347 0039d316-1c4b-4281-b951-d872f2087c98
* Initial support for running the ui_tests under Purify on thepaulg@google.com2008-12-181-1/+1
| | | | | | | | | | | | | | | | | | buildbots. With these changes, I've been able to get 106 of about 185 ui_tests running under Purify on my machine (I haven't gotten to the remaining tests yet) with minimal changes. The changes here are timeout related, allowing us to specify longer timeouts in chrome_tests.py rather than hard coding them in the tests themselves. We'll likely have to experiment on the buildbots with different timeout values, depending on how fast the bots are. Review URL: http://codereview.chromium.org/14184 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7226 0039d316-1c4b-4281-b951-d872f2087c98
* Use a more compact license header in source files.license.bot2008-08-241-28/+4
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1287 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome to the repository.initial.commit2008-07-261-0/+69
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-10 04:30:11 +0000