summaryrefslogtreecommitdiffstats
path: root/chrome/test/browser
Commit message (Collapse)AuthorAgeFilesLines
* Adds support for the gtest_also_run_disabled_tests flag in the browser tests.jcampan@chromium.org2009-07-073-3/+12
| | | | | | | | BUG=None TEST=Run the browser tests with the --gtest_also_run_disabled_tests flag. Disabled tests should be run. Review URL: http://codereview.chromium.org/155112 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20060 0039d316-1c4b-4281-b951-d872f2087c98
* Browser tests would launch disabled tests.jcampan@chromium.org2009-07-011-0/+4
| | | | | | | | | | | | The tests would then not be run by GUnit, polluting the outputs. This CL makes sure we don't launch the disabled tests. BUG=None TEST=Run the browser tests. Look at the output, it should not show disabled tests have been run. Review URL: http://codereview.chromium.org/150177 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19767 0039d316-1c4b-4281-b951-d872f2087c98
* The browser test runner was returning the wrong value on success/failure.jcampan@chromium.org2009-06-241-2/+2
| | | | | | | | BUG=None TEST=browser_tests.exe should return 0 on success, 1 on failure. Review URL: http://codereview.chromium.org/147060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19128 0039d316-1c4b-4281-b951-d872f2087c98
* This CL makes the browser_tests.exe runnable from outside its directory.jcampan@chromium.org2009-06-231-12/+6
| | | | | | | | BUG=None TEST=Run browser_tests.exe from the command line from a directory that is not the directory containing it. Review URL: http://codereview.chromium.org/146018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19024 0039d316-1c4b-4281-b951-d872f2087c98
* Remove checked-in .vcproj files that have been converted to gyp.sgk@google.com2009-06-102-488/+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
* Clean-up following sgk's suggestions.jcampan@chromium.org2009-06-091-0/+3
| | | | | | | | | | | | | Also few fixes: - we need an AtExitManager instanciated for some calls to succeed (see browser_test_launcher_in_proc.cc) - the browser_tests.dll PDB file was getting overridden by the one for browser_tests.exe (making it hard to debug tests...) - the browser tests require the browser_resources.rc or some tests will fail. BUG=None TEST=Run the browser tests. Review URL: http://codereview.chromium.org/119270 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17959 0039d316-1c4b-4281-b951-d872f2087c98
* Porting the browser tests to Unix.jcampan@chromium.org2009-06-055-87/+300
| | | | | | | | | | | | | The browser tests are an alternative to UI tests. They provide a way to exercise the browser from within the test (without having the test and the browser running in different processes). In order to ensure atexit hanlders are run after each tests and static initializers start fresh for each test, each test is run in a new process (on Linux and Mac). On Windows, a DLL containing the test is loaded/unloaded for each tests. BUG=None TEST=Run the browser tests. Review URL: http://codereview.chromium.org/115896 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17781 0039d316-1c4b-4281-b951-d872f2087c98
* Convert to gyp generation of chrome_resources and chrome_strings.sgk@chromium.org2009-06-041-4/+4
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/119128 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17609 0039d316-1c4b-4281-b951-d872f2087c98
* Revert last checkin to fix resources in Release builds.sgk@chromium.org2009-06-031-4/+4
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/119075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17468 0039d316-1c4b-4281-b951-d872f2087c98
* Convert to gyp generation of chrome_resources and chrome_strings.sgk@chromium.org2009-06-031-4/+4
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/119061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17467 0039d316-1c4b-4281-b951-d872f2087c98
* Fix crash as a result of my previous change to fix the memory leak in ↵jam@chromium.org2009-05-221-0/+8
| | | | | | | | | | WebCacheManager. BUG=12362 TEST=added regression test Review URL: http://codereview.chromium.org/113754 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16775 0039d316-1c4b-4281-b951-d872f2087c98
* Fix a crash on browser exit after opening TaskManager.phajdan.jr@chromium.org2009-05-201-0/+8
| | | | | | | | | | | | | | | | | | | | | TaskManager is a singleton, so it's destroyed by AtExitManager. At the time of destruction it cannot register AtExit callbacks (AtExitManager requires that). It turns out that some Windows view code wants to register an AtExit callback during destruction. For more info about view code, see http://src.chromium.org/viewvc/chrome?view=rev&revision=9161 The fix is to destroy the view early, using EnsureShutdown static method of TaskManager. It was also necessary to delete child views a bit earlier to avoid another crashed. Added a regression browser_test and verified that it's broken without this fix. http://crbug.com/11180 Review URL: http://codereview.chromium.org/114031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16474 0039d316-1c4b-4281-b951-d872f2087c98
* Move the ChildProcessSecurityPolicy browser test to the browser_tests dll.jam@chromium.org2009-05-191-0/+8
| | | | | | Review URL: http://codereview.chromium.org/115544 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16434 0039d316-1c4b-4281-b951-d872f2087c98
* Convert the webkit build on Windows to gyp:sgk@google.com2009-05-081-1/+1
| | | | | | | | | | | | | | | | | * build\all.gyp now uses webkit\webkit.gyp and webkit\tools\test_shell\test_shell.gyp. * 'svn remove' checked-in .sln and .vcproj files that will now become gyp-generated files. (We'll leave the other old ones in place, uncalled, and remove them with a later CL.) * Add generated *.sln and *.vcproj files to svn:ignore on the relevant directories. * Update various chrome\**.vcproj files with the new gyp directory in which various generated webkit files will now appear. * Update the checked-in chrome\chrome.sln with all (?) the changes necessary to reflect the new gyp generation. Review URL: http://codereview.chromium.org/115115 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15618 0039d316-1c4b-4281-b951-d872f2087c98
* Rolling back webkit-gyp switch. r14382bradnelson@google.com2009-04-291-1/+1
| | | | | | Review URL: http://codereview.chromium.org/99182 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14837 0039d316-1c4b-4281-b951-d872f2087c98
* Switching webkit over to gyp on windows.bradnelson@google.com2009-04-291-1/+1
| | | | | | Review URL: http://codereview.chromium.org/99173 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14832 0039d316-1c4b-4281-b951-d872f2087c98
* Relanding this: jcampan@chromium.org2009-04-284-0/+683
| | | | | | | | | | | | | | | | | | | | | | | | | This patch adds a new kind of tests: browser tests. They are intended to provide an alternative to the UI tests, hopefully helping with flackiness. These tests are in-process browser test. There are 2 projects to build the tests: - the browser_test.dll that contains the tests, the gtest framework and the browser classes. - the browser_test_launcher.exe. The launcher loads the browser_test.dll for each test, run the test and then unloads the DLL. This insures the static initializers are run before each test and that any atexit handler is invoked properly. This is Windows only for now. BUG=9764 TEST=Run browser_test.exe TBR=maruel Review URL: http://codereview.chromium.org/99097 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14738 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting my change it breaks release compilation on Windows.jcampan@chromium.org2009-04-274-675/+0
| | | | | | | TBR=maruel Review URL: http://codereview.chromium.org/103001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14669 0039d316-1c4b-4281-b951-d872f2087c98
* This patch adds a new kind of tests: browser tests.jcampan@chromium.org2009-04-274-0/+675
They are intended to provide an alternative to the UI tests, hopefully helping with flackiness. These tests are in-process browser test. There are 2 projects to build the tests: - the browser_test.dll that contains the tests, the gtest framework and the browser classes. - the browser_test_launcher.exe. The launcher loads the browser_test.dll for each test, run the test and then unloads the DLL. This insures the static initializers are run before each test and that any atexit handler is invoked properly. This is Windows only for now. BUG=9764 TEST=Run browser_test.exe Review URL: http://codereview.chromium.org/88066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14664 0039d316-1c4b-4281-b951-d872f2087c98