summaryrefslogtreecommitdiffstats
path: root/chrome_frame/test_utils.cc
Commit message (Collapse)AuthorAgeFilesLines
* Some Chrome Frame cleanup:robertshield@chromium.org2010-01-051-3/+4
| | | | | | | | | | | | | | | | | | 1) Rearrange the chrome_frame.gyp file to: a) Split out most of CF into a static lib to make writing unit tests easier (not having to re-include source files). b) Remove most of the un-needed xulrunner-sdk includes. 2) Move all OBJECT_ENTRY_AUTO macros to chrome_tab.cc since they don't work without extra work when residing in a lib. 3) Rename npchrome_tab.dll to npchrome_frame.dll. BUG=none TEST=none Review URL: http://codereview.chromium.org/523040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35543 0039d316-1c4b-4281-b951-d872f2087c98
* Kill all browser instances at test start up in addition to at tear down ↵robertshield@chromium.org2009-12-071-0/+164
| | | | | | | | | | | | | which should improve test reliability. Make running the Chrome Frame integration tests slightly less onerous by not killing non-ChromeFrame instances of Chrome. BUG=All chrome.exe instances would die when running these tests, which made them annoying to run. TEST=Only Chrome Frame instances of Chrome will be killed when running the integration tests. Review URL: http://codereview.chromium.org/467036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33991 0039d316-1c4b-4281-b951-d872f2087c98
* ChromeFrame perf tests should use the reference builds checked in under ↵ananta@chromium.org2009-10-161-2/+2
| | | | | | | | | | | | | | | chrome\tools\test\reference_builds. This CL updates the chrome frame tests to register the chrome frame dll from the correct path and deletes the reference build used by ChromeFrame. Fixes http://code.google.com/p/chromium/issues/detail?id=23382 Bug=23382 Review URL: http://codereview.chromium.org/284016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29342 0039d316-1c4b-4281-b951-d872f2087c98
* Re-try r29078: Remove some deprecated file_util wstring functions.estade@chromium.org2009-10-151-6/+7
| | | | | | | | | | | | | With the previous patch, the try bots failed with mysterious messages, so I ignored them, patched it into my windows box and tested it there manually, and found no problems. As it turns out, the try failures were real :(. But nsylvain and I found the problem: the behavior of file_util::GetDirectoryFromPath() differs from DirName() when the path is empty (officially, GetDirectoryFromPath is not supposed to support non-absolute paths, but that is not enforced). Here is a green win try result: http://build.chromium.org/buildbot/try-server/builders/win/builds/3705 mac: http://build.chromium.org/buildbot/try-server/builders/mac/builds/3491 linux: http://build.chromium.org/buildbot/try-server/builders/linux/builds/3466 I also applied this patch locally in Windows to test that it doesn't break the chrome frame compile or tests, since that's not covered by the trybots yet. Review URL: http://codereview.chromium.org/271099 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29094 0039d316-1c4b-4281-b951-d872f2087c98
* Revert wstring patch (r29078 and follow up commits). It is causing failures ↵estade@chromium.org2009-10-151-7/+6
| | | | | | | | | | on the buildbots. TBR=nsylvain Review URL: http://codereview.chromium.org/280004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29085 0039d316-1c4b-4281-b951-d872f2087c98
* Try to fix chrome frame build again.estade@chromium.org2009-10-151-6/+7
| | | | | | | | TBR=nsylvain Review URL: http://codereview.chromium.org/276040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29083 0039d316-1c4b-4281-b951-d872f2087c98
* Initial import of the Chrome Frame codebase. Integration in chrome.gyp ↵slightlyoff@chromium.org2009-09-241-0/+95
coming in a separate CL. BUG=None TEST=None Review URL: http://codereview.chromium.org/218019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27042 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-19 17:58:05 +0000