summaryrefslogtreecommitdiffstats
path: root/chrome/test/mini_installer_test
Commit message (Collapse)AuthorAgeFilesLines
* Fix the redness on the new Google Chrome continuous builder by notnsylvain@chromium.org2009-06-191-1/+3
| | | | | | | | running the mini_installer_tests that need to access the previous installers, since they are not accessible from this buildbot. Review URL: http://codereview.chromium.org/131070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18812 0039d316-1c4b-4281-b951-d872f2087c98
* Enabling the tests after sgk reverted CL18441.anantha@chromium.org2009-06-161-2/+2
| | | | | | Review URL: http://codereview.chromium.org/125165 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18461 0039d316-1c4b-4281-b951-d872f2087c98
* Disabled mini_installer tests to investigate the failures.anantha@chromium.org2009-06-151-2/+2
| | | | | | Review URL: http://codereview.chromium.org/125157 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18448 0039d316-1c4b-4281-b951-d872f2087c98
* Added another command line option to run the tests after profile backup.anantha@chromium.org2009-06-117-30/+83
| | | | | | | Also, Changed the hardcoded build labels (1.0, 2.0) to (2.0, 3.0). Review URL: http://codereview.chromium.org/118463 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18214 0039d316-1c4b-4281-b951-d872f2087c98
* Added a command line parameter(-clean), which up on passing will uninstall ↵anantha@chromium.org2009-06-082-5/+19
| | | | | | | | | current version of chrome on users machine. if the parameter is not passed then a message is displayed with usage details. Also, standalone insatller test was looking for 1.0 to build the version number. Changed it to 2.0. Review URL: http://codereview.chromium.org/119192 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17912 0039d316-1c4b-4281-b951-d872f2087c98
* Roll back this part of my earlier test. Looks like these tests are still ↵ben@chromium.org2009-06-021-2/+2
| | | | | | | | | | | | badly affected. TBR=sky BUG=none TEST=none Review URL: http://codereview.chromium.org/118140 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17450 0039d316-1c4b-4281-b951-d872f2087c98
* Properly initialize the native wrapper to NULL to avoid a crash. Also ↵ben@chromium.org2009-06-021-2/+2
| | | | | | | | | | re-enables tests I disabled last night when trying to find this. http://crbug.com/13200 TEST=Start chrome with --first-run. Review URL: http://codereview.chromium.org/118136 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17440 0039d316-1c4b-4281-b951-d872f2087c98
* Disable this test since I can't run it without trashing my profile.ben@chromium.org2009-06-021-1/+1
| | | | | | TBR=anantha git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17397 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling this test since I can't run the suite without them erasing my profile.ben@chromium.org2009-06-021-1/+1
| | | | | | TBR=anantha git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17393 0039d316-1c4b-4281-b951-d872f2087c98
* Added more installer tests. Here is the list:anantha@chromium.org2009-05-135-57/+165
| | | | | | | | | | | | | | | | | 1. Install latest dev/beta channel build. 2. Install latest stable build. 3. Install latest dev/beta channel build at System level. 4. Install latest stable build at system level. 5. Install latest dev/beta full installer over previous dev/beta full installer. 6. Install latest stable full installer over previous stable full installer. 7. Install latest dev/beta diff installer over previous dev/beta full installer. 8. Install latest stable diff installer over previous stable full installer. 9. Install latest stable full installer over ChromeSetup.exe 10. Install latest beta full installer over beta ChromeSetup.exe Review URL: http://codereview.chromium.org/115159 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15994 0039d316-1c4b-4281-b951-d872f2087c98
* Fix missing assignment in chrome_mini_installer.thestig@chromium.org2009-05-051-1/+1
| | | | | | | TBR=tony Review URL: http://codereview.chromium.org/109048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15339 0039d316-1c4b-4281-b951-d872f2087c98
* Remove uses of deprecated version of PathService::Get() in the installer.thestig@chromium.org2009-05-052-14/+14
| | | | | | Review URL: http://codereview.chromium.org/109033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15325 0039d316-1c4b-4281-b951-d872f2087c98
* Enable two more installer tests.kuchhal@chromium.org2009-04-291-2/+2
| | | | | | | Review URL: http://codereview.chromium.org/100177 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14888 0039d316-1c4b-4281-b951-d872f2087c98
* Try --force-uninstall param to see if that fixes installer tests.kuchhal@chromium.org2009-04-292-5/+5
| | | | | | | Review URL: http://codereview.chromium.org/99204 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14884 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling the tests again. anantha@chromium.org2009-04-281-1/+1
| | | | | | Review URL: http://codereview.chromium.org/99150 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14783 0039d316-1c4b-4281-b951-d872f2087c98
* Forgot to enable the test in last check-in. Enabled the test now.anantha@chromium.org2009-04-281-3/+3
| | | | | | Review URL: http://codereview.chromium.org/99145 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14766 0039d316-1c4b-4281-b951-d872f2087c98
* One more try to make these tests pass. Added a while loop to wait until the ↵anantha@chromium.org2009-04-283-3/+19
| | | | | | | | | key is open. Sorry for enabling and disabling the tests for few times. I really want these tests to run asap, so that I can add new tests. Review URL: http://codereview.chromium.org/99142 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14761 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling the tests again. Looking into them.anantha@chromium.org2009-04-281-1/+1
| | | | | | Review URL: http://codereview.chromium.org/101010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14749 0039d316-1c4b-4281-b951-d872f2087c98
* Added a check to look for setup.exe before looking at registry. This test is ↵anantha@chromium.org2009-04-282-8/+13
| | | | | | | | failing becase of race conditon. This fix should resolve the problem. Review URL: http://codereview.chromium.org/99134 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14747 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling the test again. This time the test doesn't fail at mulitple ↵anantha@chromium.org2009-04-281-1/+1
| | | | | | | | places. It fails at only one place. investigating... Review URL: http://codereview.chromium.org/102003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14696 0039d316-1c4b-4281-b951-d872f2087c98
* Enabling the user install tests to see if they pass. They were failing ↵anantha@chromium.org2009-04-283-4/+3
| | | | | | | | | | | | | | | because of two reasons: 1. the new profile dialog closes the setup.exe process as soon as the dialog is closed. The testcase used to wait for setup.exe to start/end, which would never happen. heence the test failed. 2. Closing of new profile dialog also deletes the reg keys right away. looks like there were some timing issues.Added a sleep of 400 to see if the test passes now. if it passes, then I will look into other options and remove the sleep. ----- The standalone installer path got changed recently. modified that path also. Review URL: http://codereview.chromium.org/100086 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14693 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling user install testcase to investigate why it fails on the bot and ↵anantha@chromium.org2009-04-271-1/+1
| | | | | | | | not locally. Review URL: http://codereview.chromium.org/99080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14660 0039d316-1c4b-4281-b951-d872f2087c98
* Its strange that these tests are failing only on bots, but not on local ↵anantha@chromium.org2009-04-272-4/+16
| | | | | | | | machines. I added few checks to get rid of cascading errors. Enabled only one test to see if it passses this time. Review URL: http://codereview.chromium.org/100003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14654 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "try enabling installer tests again."kuchhal@chromium.org2009-04-222-3/+3
| | | | | | | | | This reverts commit 8269e3cc8929f8348d0ed1ec13cb69f90cc928f6. Review URL: http://codereview.chromium.org/93020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14190 0039d316-1c4b-4281-b951-d872f2087c98
* try enabling installer tests again.kuchhal@chromium.org2009-04-222-3/+3
| | | | | | | Review URL: http://codereview.chromium.org/92016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14189 0039d316-1c4b-4281-b951-d872f2087c98
* comment test again as the fix didnt work.kuchhal@chromium.org2009-04-211-2/+2
| | | | | | | Review URL: http://codereview.chromium.org/89008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14145 0039d316-1c4b-4281-b951-d872f2087c98
* Fix installer tests broken by r13926.kuchhal@chromium.org2009-04-215-7/+44
| | | | | | | Review URL: http://codereview.chromium.org/87011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14140 0039d316-1c4b-4281-b951-d872f2087c98
* Disable installer tests while I work on fixing them.kuchhal@chromium.org2009-04-171-4/+4
| | | | | | | | | TBR=ananthak Review URL: http://codereview.chromium.org/69035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13927 0039d316-1c4b-4281-b951-d872f2087c98
* Two of the installer tests were failing because of path issues. Looks like ↵anantha@chromium.org2009-04-033-31/+47
| | | | | | | | buildbots like absolute paths. Fixed the issue now. Review URL: http://codereview.chromium.org/60075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13071 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling the tests temporarily.anantha@chromium.org2009-04-021-3/+3
| | | | | | Review URL: http://codereview.chromium.org/60065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13040 0039d316-1c4b-4281-b951-d872f2087c98
* Added two more installer tests: 1. Testcase to install and verify ↵anantha@chromium.org2009-04-023-37/+129
| | | | | | | | | differenial installer. 2. Testcase to install and verify full installer. Review URL: http://codereview.chromium.org/56159 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13035 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the checked-in scons configuration files.sgk@google.com2009-04-011-155/+0
| | | | | | Review URL: http://codereview.chromium.org/53121 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12982 0039d316-1c4b-4281-b951-d872f2087c98
* Added logic to get the latest diff installer, full installer, previous full ↵anantha@chromium.org2009-03-265-78/+213
| | | | | | | | | installer from nightly location. It will now be easy to automate more of the installer testing. Review URL: http://codereview.chromium.org/49024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12617 0039d316-1c4b-4281-b951-d872f2087c98
* re-enable this now the bug causing it to fail has been fixed.ben@chromium.org2009-03-241-4/+0
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12330 0039d316-1c4b-4281-b951-d872f2087c98
* Disable the mini installer tests because they startednsylvain@chromium.org2009-03-231-0/+4
| | | | | | | | failing at revision 12317. Review URL: http://codereview.chromium.org/49012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12325 0039d316-1c4b-4281-b951-d872f2087c98
* NO CODE CHANGEdeanm@chromium.org2009-03-105-5/+0
| | | | | | | | | Normalize end of file newlines in chrome/. All files end in a single newline. Review URL: http://codereview.chromium.org/42015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11331 0039d316-1c4b-4281-b951-d872f2087c98
* Added a test for testing standalone installer.anantha@chromium.org2009-03-065-34/+179
| | | | | | | | Automated the steps listed at: https://sites.google.com/a/google.com/chrome-pmo/standalone-installers/testing-standalone-installers Review URL: http://codereview.chromium.org/39150 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11138 0039d316-1c4b-4281-b951-d872f2087c98
* Add a test case to be sure that InstallerUtil::IsOSSupported returnsnsylvain@chromium.org2009-02-261-0/+6
| | | | | | | | | | true for all the versions we support (or test on) bug: 7735 Review URL: http://codereview.chromium.org/27171 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10444 0039d316-1c4b-4281-b951-d872f2087c98
* Fix all places where we used the GetWinVersion functionnsylvain@chromium.org2009-02-251-2/+2
| | | | | | | | | incorrectly. bug:7802 Review URL: http://codereview.chromium.org/28128 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10366 0039d316-1c4b-4281-b951-d872f2087c98
* Disabled system level install tests on Vista. System level install tests are ↵anantha@chromium.org2009-02-043-29/+44
| | | | | | | | | launching UAC dialog on vista and hence making the tests fail. I am trying to figure out how to handle that case. Hence disabled the system level test for time being. I have also modified GetRegistryKey method to have a out parameter and return bool. The previous could lead to a crash if the reg key value "pv" was not present. Review URL: http://codereview.chromium.org/21054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9185 0039d316-1c4b-4281-b951-d872f2087c98
* This CL fixes bugs with EULAcpu@google.com2009-01-291-1/+1
| | | | | | | | | | | | | | - The first run import will trigger the eula again : this requires changes in browser_main.cc so the master prefs are not processed again by the importer process - The launch of setup.exe to show the eula was using a path that only works on developer builds this requires relocating a constant from setup_constants to util_constants BUG=1468838 Review URL: http://codereview.chromium.org/19680 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8928 0039d316-1c4b-4281-b951-d872f2087c98
* Disabling the failing testsnsylvain@chromium.org2009-01-291-3/+3
| | | | | | | tbr Review URL: http://codereview.chromium.org/19652 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8852 0039d316-1c4b-4281-b951-d872f2087c98
* Added a test for checking system install.anantha@chromium.org2009-01-295-89/+153
| | | | | | Review URL: http://codereview.chromium.org/18131 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8848 0039d316-1c4b-4281-b951-d872f2087c98
* Generate all chrome .vcproj files:sgk@google.com2009-01-171-12/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Path name translation (/ to \) of various MSVSTool attributes. * Explicit keyword= arguments to MSVSProject. This will likely go away eventually in favor of uniform behavior. * Add a relative_path_substitutions array that can be used to substitute in Visual Studio variable like $(OutDir). * Add a local_directory_prefix that can be set to './' to only affect files in the current directory. * Additional Keyword ordering in Tool attributes to continue to match the default order Visual Studio generates. * Add a Derived() proxy class that can wrap a File node to tell the .vcproj generation that we want the derived file, not its source(s), in the file list. * In the individual *.scons files, add the necessary files (mostly .h files) to file lists, and update MSVSProject() calls with the additional necessary information. Result is identical .vcproj files modulo the following differences: * Four locales .vcproj files (da, en-US, he and zh-TW) with source file orders that don't match the other locale .vcproj files have re-ordered file lists to match the rest. * Cosmetic XML changes (white space, ending tags) in: chrome/app/chrome_dll.vcproj chrome/app/generated_resources.vcproj net/build/net_resources.vcproj * Removal or addition of ./ prefixes from various files that don't match the other file specifications within their individual .vcproj files: chrome/installer/util/util.vcproj net/build/net.vcproj net/build/net_unittests.vcproj * Add missing empty sections (<ToolFiles>, <References>, <Globals>) for consistency with other .vcproj files: chrome/tools/test/image_diff/image_diff.vcproj third_party/libpng/libpng.vcproj third_party/zlib/zlib.vcproj * Add missing RootNameSpace attribute: chrome/test/automation/automation.vcproj testing/gtest.vcproj * Use && instead of \r\n as a command separator, to sidestep XML-generation problems: chrome/app/chrome_exe.vcproj * Remove unnecessary (?) duplicate files in the file list: chrome/browser/views/browser_views.vcproj (event_utils.cc and event_utils.h were duplicated) Review URL: http://codereview.chromium.org/17603 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8253 0039d316-1c4b-4281-b951-d872f2087c98
* Initial generation of native Visual Studio solution filessgk@google.com2008-12-191-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (project files still to come). To wit: * Solution file configuration is in *_sln.scons files (base\base_sln.scons, chrome\chrome_sln.scons). * Individual Project file configuration is in the the .scons file for the relevant target (base\base_unittests.scons, third_party\libxml\libxml.scons, etc.)--that is, where their file lists will live. * MSVSProject() calls are currently placeholders that establish the existence of Project Nodes (and Project dependencies) but don't yet have actual Project configuration information (file lists, .vsprops, etc.). * Configuraiton is very manual. In particular, the entries in the .sln file will be written out in exactly the order specified in the configuration(s). The current ordering is taken from our existing .sln files, so we can generate virtually the same configurations on output. * Generated solution files are nearly byte-for-byte identical with our existing .sln files, modulo: * net\dump_cache has a WebsiteProperties sections (making that configurable per project isn't important right now); * sandbox\sandbox.sln was missing a dependency of base.vcproj on on debug_message.vcproj (present in other .sln files) * webkit\webkit.sln was missing dependencies of WebCore.vcproj on libxml_config.vcproj and libxslt_config.vcproj (present in chrome.sln); * add a handful of other miscellaneous missing dependencies on various .vcproj definitions in chrome.sln (present in other .sln files). * remove stats_viewer.csproj from chrome.sln (sorry, mbelshe), which was complicating the solution configuration with unnecessary (for us) "Mixed Platform" types; * All MSVSFolder(), MSVSProject() and MSVSSolution() calls have hard-wired guid= values taken from our existing configuration, so we can: 1) verify generation of working configs; 2) minimize diffs when checking in generated .sln files. We can remove these in the future in favor of extracting them from existing .sln files if we wish. * Add ChromeMSVSFolder(), ChromeMSVSProject() and ChromeMSVSSolution() wrappers to chromium_builders.py, that gate the underlying call to the env.MSVS*() builders based on whether env.Bit('msvs') is set (i.e., we're in --mode=msvs). * Remove platform-specific gating of to-be-ported .scons files that we now need to load on any platform to generate coheren MSVS files. Move the env.Bit('windows') tests for actually building their executables into the individual .scons files. Review URL: http://codereview.chromium.org/14472 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7297 0039d316-1c4b-4281-b951-d872f2087c98
* Convert from using env['PLATFORM'] directly to using the more flexiblesgk@google.com2008-12-181-1/+1
| | | | | | | | | | | | | | | | | | and better-thought-out Hammer env.Bits() idioms: * env['PLATFORM'] == 'win32' => env.Bit('windows') * env['PLATFORM'] == 'posix' => env.Bit('linux') * env['PLATFORM'] == 'darwin' => env.Bit('mac') New idioms: * env.Bit('posix') => really does mean "any POSIX platform" * env.AnyBits('mac', 'linux') => specifically mac or linux, excluding other POSIX platforms Where we were using compound conditionals (e.g., "env['PLATFORM'] in ('posix', 'darwin')") I tried to take my best shot at translating the intent (i.e., "env.Bits('posix')" for something POSIX, "not env.Bits('mac')" for something not yet ported to Mac, etc.) Review URL: http://codereview.chromium.org/15051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7270 0039d316-1c4b-4281-b951-d872f2087c98
* Switch back svn:eol-style=native for .sln, .vcproj and .vsprops files.maruel@chromium.org2008-12-161-176/+176
| | | | | | | Patch fails otherwise on non-Windows platforms. Review URL: http://codereview.chromium.org/14478 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7093 0039d316-1c4b-4281-b951-d872f2087c98
* Changed svn:eol-style of all .sln and .vcproj files to CRLFscherkus@chromium.org2008-12-041-176/+176
| | | | | | Review URL: http://codereview.chromium.org/13133 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6372 0039d316-1c4b-4281-b951-d872f2087c98
* Next round of SCons changes:sgk@google.com2008-11-142-64/+68
| | | | | | | | | | | | | | | | | | | * Add 'gdm_fp' to the $LIBS setting in base\using_base.scons (to be removed when that library moves into base\third_party). * Have the grit Scanner search the Repository() copy of the source file (necessary now that $TARGET_ROOT has changed). * Change all the SConscript files underneath chrome\test and chrome\tools to *.scons files, including updating their contents with the current patterns. * Add dependencies of the local_settings_*.res files on the corresponding google_chrome_string_*.rc files, so they get generated properly. * Add generation of the chrome_exe.res resource file. * Comment out some unnecessary .lib settings in the base construction environment. Review URL: http://codereview.chromium.org/10745 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5480 0039d316-1c4b-4281-b951-d872f2087c98
* Add Terminate() to the Process object, have RenderProcessHost use this to ↵brettw@google.com2008-11-141-13/+13
| | | | | | | | | | avoid some more Windows specific code. Move Process and SharedMemory into the base namespace (most changes). Review URL: http://codereview.chromium.org/10895 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@5446 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-01 09:02:46 +0000