summaryrefslogtreecommitdiffstats
path: root/chrome/test/data
Commit message (Collapse)AuthorAgeFilesLines
* Cleanup to move other Panels test data files to new panels test dir.jennb@chromium.org2011-11-161-0/+0
| | | | | | | | | BUG=None TEST=PanelBrowserTest.AutoResize, CreateWithExistingContents, OnBeforeUnloadOnClose Review URL: http://codereview.chromium.org/8568034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110226 0039d316-1c4b-4281-b951-d872f2087c98
* - Adding CPU performance test to calculate extrapolation of the utilization ↵rohitbm@chromium.org2011-11-151-1/+1
| | | | | | | | | | to play the test video. - Modify existing performance test by first buffer 100% video, ignore first 10 seconds to get rid of initial dropped frames noise. Then test for next 60 seconds. - Replaced the test video to Transformers 3 high-motion trailer for better testing. Review URL: http://codereview.chromium.org/8548002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110117 0039d316-1c4b-4281-b951-d872f2087c98
* Fix panels being removed from PanelManager prematurely.prasadt@chromium.org2011-11-151-0/+26
| | | | | | | | | BUG=102720 TEST=Manual repro steps in the bug report. Review URL: http://codereview.chromium.org/8505047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110110 0039d316-1c4b-4281-b951-d872f2087c98
* Tests for WebUI Hung Renderer Dialogwyck@chromium.org2011-11-152-0/+116
| | | | | | | | | | | | | | | Adds a WebUIBrowserTest for WebUI Hung Renderer Dialog. Also modifies HungRendererDialog to allow it to be called in a test without killing processes or restarting hang timers. Fixed revert issue with win_aura. BUG=102073 TEST=browser_tests HungRendererDialogUITest.* Review URL: http://codereview.chromium.org/8555027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110082 0039d316-1c4b-4281-b951-d872f2087c98
* Print Preview: Making margin selection sticky (part 2/2, again)dpapad@chromium.org2011-11-151-2/+2
| | | | | | | | | | | | This is a reland of http://codereview.chromium.org/8351048/ with minor changes to fix the compilation errors on the shared builders. BUG=102446 TEST=See bug description. Review URL: http://codereview.chromium.org/8528053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110055 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 110035 - Print Preview: Making margin selection sticky (part 2/2)dpapad@chromium.org2011-11-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL makes "Custom" margins sticky across different preview sessions but also within the same preview session. Here is a summary of all changes. - Within same preview session: So far selecting "Custom" was picking up from whatever the previous selected option was. Now, "Custom" remembers the specified margins. To test this select "Custom", do some dragging, then change to another option and back to "Custom". - Across preview sessions: Select "Custom", do some dragging, then print. Open print preview again, the last used custom margins are remembered. - There was a bunch of messages sent from JS to get various info/settings (initiator tab title, measurement system and number format, last used margin settings, default printer). I created a single message "getInitialSettings" to get all at once (they are needed before the 1st preview is is requested). BUG=102446 TEST=See bug description. Review URL: http://codereview.chromium.org/8351048 TBR=dpapad@chromium.org Review URL: http://codereview.chromium.org/8564040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110040 0039d316-1c4b-4281-b951-d872f2087c98
* Print Preview: Making margin selection sticky (part 2/2)dpapad@chromium.org2011-11-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL makes "Custom" margins sticky across different preview sessions but also within the same preview session. Here is a summary of all changes. - Within same preview session: So far selecting "Custom" was picking up from whatever the previous selected option was. Now, "Custom" remembers the specified margins. To test this select "Custom", do some dragging, then change to another option and back to "Custom". - Across preview sessions: Select "Custom", do some dragging, then print. Open print preview again, the last used custom margins are remembered. - There was a bunch of messages sent from JS to get various info/settings (initiator tab title, measurement system and number format, last used margin settings, default printer). I created a single message "getInitialSettings" to get all at once (they are needed before the 1st preview is is requested). BUG=102446 TEST=See bug description. Review URL: http://codereview.chromium.org/8351048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110035 0039d316-1c4b-4281-b951-d872f2087c98
* Seed test for SyncUI: sign in successfully with mocks.scr@chromium.org2011-11-154-107/+83
| | | | | | | | | | | R=binji@chromium.org BUG=102750 TEST=browser_tests --gtest_filter=SyncSetupWebUITest.* Review URL: http://codereview.chromium.org/8503003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110006 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109984 - Tests for WebUI Hung Renderer Dialogkmadhusu@chromium.org2011-11-152-116/+0
| | | | | | | | | | | | | | | | | | | | Adds a WebUIBrowserTest for WebUI Hung Renderer Dialog. Also modifies HungRendererDialog to allow it to be called in a test without killing processes or restarting hang timers. See previous attempt: http://codereview.chromium.org/8372042 See revert of that attempt: http://codereview.chromium.org/8497001/ BUG=102073 TEST=browser_tests HungRendererDialogUITest.* Review URL: http://codereview.chromium.org/8462015 TBR=wyck@chromium.org Review URL: http://codereview.chromium.org/8510071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109989 0039d316-1c4b-4281-b951-d872f2087c98
* Tests for WebUI Hung Renderer Dialogwyck@chromium.org2011-11-152-0/+116
| | | | | | | | | | | | | | | | | Adds a WebUIBrowserTest for WebUI Hung Renderer Dialog. Also modifies HungRendererDialog to allow it to be called in a test without killing processes or restarting hang timers. See previous attempt: http://codereview.chromium.org/8372042 See revert of that attempt: http://codereview.chromium.org/8497001/ BUG=102073 TEST=browser_tests HungRendererDialogUITest.* Review URL: http://codereview.chromium.org/8462015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109984 0039d316-1c4b-4281-b951-d872f2087c98
* Updating the Flapper version number for PyAuto plugins verification test.rohitbm@chromium.org2011-11-141-9/+9
| | | | | | Review URL: http://codereview.chromium.org/8565020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109945 0039d316-1c4b-4281-b951-d872f2087c98
* Enable extension APIs for content scripts.aa@chromium.org2011-11-125-15/+29
| | | | | | | | | | | This only enables extension functions. I will do events in a separate change. BUG=81760,80308 Review URL: http://codereview.chromium.org/8540012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109812 0039d316-1c4b-4281-b951-d872f2087c98
* Add tests to make sure gpu blacklist actually block gpu features.zmo@google.com2011-11-123-0/+89
| | | | | | | | | | | | (Retry after a fix.) The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched. BUG=101222 TEST=browser_tests Review URL: http://codereview.chromium.org/8510032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109740 0039d316-1c4b-4281-b951-d872f2087c98
* WebUI test framework: fix Mock4JS verification, allow chrome.send passthrough.scr@chromium.org2011-11-115-13/+292
| | | | | | | | | | | | | | | | | | 1) Add test for Bug 99970 Comment 6 & fix 2) Allow chrome.send to be mocked outside of preLoad call. 3) add chrome.originalSend to allow mocked messages to pass through to C++. Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules. R=flackr@chromium.org,wyck@chromium.org BUG=103740,99970,102794 TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.* Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=109678 Review URL: http://codereview.chromium.org/8515016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109711 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109678 - WebUI test framework: fix Mock4JS verification, allow ↵nduca@chromium.org2011-11-114-269/+13
| | | | | | | | | | | | | | | | | | | | | chrome.send passthrough. 1) Add test for Bug 99970 Comment 6 & fix 2) Allow chrome.send to be mocked outside of preLoad call. 3) add chrome.originalSend to allow mocked messages to pass through to C++. Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules. R=flackr@chromium.org,wyck@chromium.org BUG=103740,99970,102794 TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.* Review URL: http://codereview.chromium.org/8515016 TBR=scr@chromium.org Review URL: http://codereview.chromium.org/8480027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109680 0039d316-1c4b-4281-b951-d872f2087c98
* WebUI test framework: fix Mock4JS verification, allow chrome.send passthrough.scr@chromium.org2011-11-114-13/+269
| | | | | | | | | | | | | | | | 1) Add test for Bug 99970 Comment 6 & fix 2) Allow chrome.send to be mocked outside of preLoad call. 3) add chrome.originalSend to allow mocked messages to pass through to C++. Also to address need for .cc file to be correct for clang, and prevent ugliness in js with a lot of GEN lines, allow the header and .cc to not have a suffix, and the generated file to end in -gen.cc. While doing this, addressed crbug.com/102794 to put in <(INTERMEDIATE_DIR) preventing collisions across rules. R=flackr@chromium.org,wyck@chromium.org BUG=103740,99970,102794 TEST=browser_tests --gtest_filter=Mock4JS*.* AND ChromeSend*.* Review URL: http://codereview.chromium.org/8515016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109678 0039d316-1c4b-4281-b951-d872f2087c98
* zip: Add an evil zip file that contains an absolute file name.satorux@chromium.org2011-11-101-0/+0
| | | | | | | | | | | | | | | | | | | | | Try bots cannot handle patches with binary files nicely. We should add this file before adding a test that depends on the file. % unzip -l chrome/test/data/zip/evil_via_absolute_file_name.zip Archive: chrome/test/data/zip/evil_via_absolute_file_name.zip Length Date Time Name --------- ---------- ----- ---- 4 2011-11-09 23:40 /evil.txt --------- ------- 4 1 file BUG=chromium-os:22351 TEST=none Review URL: http://codereview.chromium.org/8523015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109536 0039d316-1c4b-4281-b951-d872f2087c98
* Remove old reliability repression that appears to be fixed now.zea@chromium.org2011-11-101-3/+0
| | | | | | | | | | | TBR=antonm@chromium.org BUG=75352 TEST=reliability tests Review URL: http://codereview.chromium.org/8525006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109518 0039d316-1c4b-4281-b951-d872f2087c98
* Fix FileSystemExtensionApiTest.FileBrowserTesttbarzic@chromium.org2011-11-101-3/+3
| | | | | | | | | BUG=103406 TEST=FileBrowserExtensionApiTest.* Review URL: http://codereview.chromium.org/8495044 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109351 0039d316-1c4b-4281-b951-d872f2087c98
* Test data for verifying signatures in downloads.bryner@chromium.org2011-11-102-0/+2
| | | | | | | | BUG=102540 TEST=none Review URL: http://codereview.chromium.org/8507033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109345 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109328 - Add tests to make sure gpu blacklist actually block gpu ↵zmo@google.com2011-11-093-89/+0
| | | | | | | | | | | | | | | features. The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched. BUG=101222 TEST=browser_tests Review URL: http://codereview.chromium.org/8497034 TBR=zmo@google.com Review URL: http://codereview.chromium.org/8510030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109334 0039d316-1c4b-4281-b951-d872f2087c98
* Add tests to make sure gpu blacklist actually block gpu features.zmo@google.com2011-11-093-0/+89
| | | | | | | | | | The general idea is to use jbates's newly added tracing: if a feature is blacklisted, we check the tracing data to make sure gpu process hasn't launched. BUG=101222 TEST=browser_tests Review URL: http://codereview.chromium.org/8497034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109328 0039d316-1c4b-4281-b951-d872f2087c98
* Media files for the defer audio video test.shishir@chromium.org2011-11-092-0/+0
| | | | | | | | | BUG=98690 TEST=None Review URL: http://codereview.chromium.org/8505038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109326 0039d316-1c4b-4281-b951-d872f2087c98
* Updating ChromeOS plugin data file with new Flapper version.rohitbm@chromium.org2011-11-091-1/+1
| | | | | | Review URL: http://codereview.chromium.org/8510028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109321 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109316 - Revert 109254 - Change WebGL conformance tests from UI tests ↵zmo@google.com2011-11-091-25/+25
| | | | | | | | | | | | | | | | | | | | to InProcessBrowserTests. InProcessBrowserTest is enough for our purpose. This change is to get ready to use a GPU BrowserTest framework where we could have more specific test expectations (like per RENDERER), and InProcessBrowserTest seems like the way to go. Also, we simplify the test mechanism on how to report back results: from three states to a simple message. BUG=none TEST=gpu bots: gpu_tests Review URL: http://codereview.chromium.org/8477048 TBR=zmo@google.com Review URL: http://codereview.chromium.org/8506030 TBR=zmo@google.com Review URL: http://codereview.chromium.org/8497051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109318 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109254 - Change WebGL conformance tests from UI tests to ↵zmo@google.com2011-11-091-25/+25
| | | | | | | | | | | | | | | | | InProcessBrowserTests. InProcessBrowserTest is enough for our purpose. This change is to get ready to use a GPU BrowserTest framework where we could have more specific test expectations (like per RENDERER), and InProcessBrowserTest seems like the way to go. Also, we simplify the test mechanism on how to report back results: from three states to a simple message. BUG=none TEST=gpu bots: gpu_tests Review URL: http://codereview.chromium.org/8477048 TBR=zmo@google.com Review URL: http://codereview.chromium.org/8506030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109316 0039d316-1c4b-4281-b951-d872f2087c98
* Make it possible to include another file and port print_preview unit test to ↵scr@chromium.org2011-11-092-41/+97
| | | | | | | | | | | | | | | | | | | | | | | | unit_tests. Print Preview unit_tests were good to tackle because it brought in a dependency on the need to include another js file. This also hilighted another need - that of being able to include non-generative js files in gyp and have them copied to the test_data dir, while doing both generation and copy for gtest files. I changed the "extension" of files which generate C++ with gtest-like syntax to .gtestjs and added a copyjs rule to the chrome_tests.gypi. FWIW, I believe this is mostly needed for unit_tests and only applied it there, although I would be amenable to also making this change for the webui tests to make it clear that they are not plain js files. R=dpapad@chromium.org BUG=101443,102222 TEST=unit_tests --gtest_filter=PrintPreviewUtilsUnitTest.* Review URL: http://codereview.chromium.org/8438063 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109310 0039d316-1c4b-4281-b951-d872f2087c98
* IndexedDB: IPC support for compound (array) keysjsbell@chromium.org2011-11-092-0/+185
| | | | | | | | | | WebKit side is: https://bugs.webkit.org/show_bug.cgi?id=62284 BUG=92038 Review URL: http://codereview.chromium.org/8417055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109266 0039d316-1c4b-4281-b951-d872f2087c98
* Change WebGL conformance tests from UI tests to InProcessBrowserTests.zmo@google.com2011-11-091-25/+25
| | | | | | | | | | | | InProcessBrowserTest is enough for our purpose. This change is to get ready to use a GPU BrowserTest framework where we could have more specific test expectations (like per RENDERER), and InProcessBrowserTest seems like the way to go. Also, we simplify the test mechanism on how to report back results: from three states to a simple message. BUG=none TEST=gpu bots: gpu_tests Review URL: http://codereview.chromium.org/8477048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109254 0039d316-1c4b-4281-b951-d872f2087c98
* Various changes to the Extension Settings API.kalman@chromium.org2011-11-092-90/+137
| | | | | | | | | | | | | | | Goals: 1 - Make it so that chrome.experimental.settings.get() can take an object with the default values to return in settings if any settings aren't set. 2 - Make it so that options pages get change events when the background page changes a setting. 3 - To solve the above: make it so that onChanged events are sent to all registered listeners, not just those which are on different processes (i.e. the incognito extension process). 4 - Remove any result in the callback from chrome.experimental.settings.set(), so that there is an unambiguous way to get changed settings (the event). It's also just generally pointless. BUG=100825,101452,101459 TEST=*ExtensionSetting* Review URL: http://codereview.chromium.org/8465002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109155 0039d316-1c4b-4281-b951-d872f2087c98
* Verify that VERSION_CHANGE transactions are rolled back after crash.jsbell@chromium.org2011-11-082-0/+91
| | | | | | | | | | | This pyautolib-based test verifies the fix for https://bugs.webkit.org/show_bug.cgi?id=70974 by preparing a database, starting a VERSION_CHANGE transaction, crashing the browser mid-transaction, then validating that nothing was committed. BUG=98562 TEST=python chrome/test/functional/indexeddb.py Review URL: http://codereview.chromium.org/8341092 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109092 0039d316-1c4b-4281-b951-d872f2087c98
* Added internal Protector key to official buildavayvod@chromium.org2011-11-081-0/+29
| | | | | | | | | | | | Increase WebData version, rewrite DSP backup signature. R=sky@chromium.org BUG=94447 TEST=Verify that Web Data version is 41, Default Search Provider ID Backup Signature is not empty in any build, different for official build. Review URL: http://codereview.chromium.org/8502019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109038 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108924 - Tests for WebUI Hung Renderer Dialogcsilv@chromium.org2011-11-082-115/+0
| | | | | | | | | | | | | | | | | This CL adds a WebUIBrowserTest to test the WebUI Hung Renderer Dialog. (Reverted due to repeated failures in .testHungRenderer) BUG=102073 TEST=browser_tests HungRendererDialogUITest.testHungRenderer Review URL: http://codereview.chromium.org/8372042 TBR=wyck@chromium.org Review URL: http://codereview.chromium.org/8497001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108960 0039d316-1c4b-4281-b951-d872f2087c98
* Add platform_app flag to manifest.miket@chromium.org2011-11-072-0/+22
| | | | | | | | | | | | | | | Enforce constraint that a platform app must declare a panel as its launch container. BUG=none TEST=unit tests added. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108885 Review URL: http://codereview.chromium.org/8429023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108936 0039d316-1c4b-4281-b951-d872f2087c98
* Tests for WebUI Hung Renderer Dialogwyck@chromium.org2011-11-072-0/+115
| | | | | | | | | | | | This CL adds a WebUIBrowserTest to test the WebUI Hung Renderer Dialog. BUG=102073 TEST=browser_tests HungRendererDialogUITest.testHungRenderer Review URL: http://codereview.chromium.org/8372042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108924 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108885 - Add platform_app flag to manifest.csilv@chromium.org2011-11-072-22/+0
| | | | | | | | | | | | | | | | Enforce constraint that a platform app must declare a panel as its launch container. BUG=none TEST=unit tests added. Review URL: http://codereview.chromium.org/8429023 TBR=miket@chromium.org Review URL: http://codereview.chromium.org/8467022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108887 0039d316-1c4b-4281-b951-d872f2087c98
* Add platform_app flag to manifest.miket@chromium.org2011-11-072-0/+22
| | | | | | | | | | | | | Enforce constraint that a platform app must declare a panel as its launch container. BUG=none TEST=unit tests added. Review URL: http://codereview.chromium.org/8429023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108885 0039d316-1c4b-4281-b951-d872f2087c98
* Support UTF8 in header values in webRequest API.battre@chromium.org2011-11-071-0/+184
| | | | | | | | | | | | | This support for UTF8 in header values is necessary to prevent DCHECKs and to ensure that extensions using the webRequest API don't modify headers unintentionally because the headers cannot be serialized correctly on the roundtrip between the network stack and the extension. BUG=none TEST=no Review URL: http://codereview.chromium.org/8480008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108879 0039d316-1c4b-4281-b951-d872f2087c98
* Add a browsertest for bug 75604gavinp@chromium.org2011-11-071-0/+8
| | | | | | | | | | | | | | | | | | | This browser test tickles the webkit bug described in crbug.com/75604 . The bug is very hard to repliably reproduce in a layout test, so my plan is to land this browser_test, update webkit to fix the bug, and update this test as we garden past the fix. BUG=75604 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107949 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108864 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108868 Review URL: http://codereview.chromium.org/8404001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108878 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108868 - Add a browsertest for bug 75604gavinp@chromium.org2011-11-071-8/+0
| | | | | | | | | | | | | | | | | | | | This browser test tickles the webkit bug described in crbug.com/75604 . The bug is very hard to repliably reproduce in a layout test, so my plan is to land this browser_test, update webkit to fix the bug, and update this test as we garden past the fix. BUG=75604 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107949 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108864 Review URL: http://codereview.chromium.org/8404001 TBR=gavinp@chromium.org Review URL: http://codereview.chromium.org/8494011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108870 0039d316-1c4b-4281-b951-d872f2087c98
* Add a browsertest for bug 75604gavinp@chromium.org2011-11-071-0/+8
| | | | | | | | | | | | | | | | | This browser test tickles the webkit bug described in crbug.com/75604 . The bug is very hard to repliably reproduce in a layout test, so my plan is to land this browser_test, update webkit to fix the bug, and update this test as we garden past the fix. BUG=75604 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107949 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108864 Review URL: http://codereview.chromium.org/8404001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108868 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108864 - Add a browsertest for bug 75604gavinp@chromium.org2011-11-071-8/+0
| | | | | | | | | | | | | | | | | | This browser test tickles the webkit bug described in crbug.com/75604 . The bug is very hard to repliably reproduce in a layout test, so my plan is to land this browser_test, update webkit to fix the bug, and update this test as we garden past the fix. BUG=75604 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107949 Review URL: http://codereview.chromium.org/8404001 TBR=gavinp@chromium.org Review URL: http://codereview.chromium.org/8479031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108865 0039d316-1c4b-4281-b951-d872f2087c98
* Add a browsertest for bug 75604gavinp@chromium.org2011-11-071-0/+8
| | | | | | | | | | | | | | | This browser test tickles the webkit bug described in crbug.com/75604 . The bug is very hard to repliably reproduce in a layout test, so my plan is to land this browser_test, update webkit to fix the bug, and update this test as we garden past the fix. BUG=75604 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107949 Review URL: http://codereview.chromium.org/8404001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108864 0039d316-1c4b-4281-b951-d872f2087c98
* Review URL: http://codereview.chromium.org/8474011rohitbm@chromium.org2011-11-051-1/+2
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108800 0039d316-1c4b-4281-b951-d872f2087c98
* Allow javascript unit tests using webui test_api framework.scr@chromium.org2011-11-051-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I moved javascript2webui.js over to chrome/test/base/js2gtest.js and shared it across webui and unit tests with an extra parameter for test type, which governs the few differences, such as what to include/subclass from and the flavor of gtest (TEST_F v. IN_PROC_BROWSER_TEST_F). v8_unit_test implemented 2 main methods to make it work with the generated C++ - AddLibrary - loads the file in the test context - RunJavascriptF - launches the runTest with the testFixture and testName, coordinating with Error and ChromeSend to report results. Helper functions: - Error - watches for console.error, noting failure if seen. - ChromeSend - pulls apart the result from the test_api's call to chrome.send('testResult', [ok, msg]) R=arv@chromium.org BUG=87820 TEST=unit_tests --gtest_filter=FrameworkUnitTest.* Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=108391 Review URL: http://codereview.chromium.org/8418015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108773 0039d316-1c4b-4281-b951-d872f2087c98
* Added parentFrameId to webRequest API callsbattre@chromium.org2011-11-043-17/+44
| | | | | | | | | | BUG=98048 TEST=no Review URL: http://codereview.chromium.org/8429007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108666 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor Instant tests.sreeram@chromium.org2011-11-031-19/+9
| | | | | | | | | | BUG=none TEST=interactive_ui_tests --gtest_filter=Instant* Review URL: http://codereview.chromium.org/8409005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108580 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108186 - Ensure forced process swaps use the correct page_id and ↵creis@chromium.org2011-11-031-1/+0
| | | | | | | | | | | | | | SiteInstance. BUG=102408 TEST=See bug Review URL: http://codereview.chromium.org/8372036 TBR=creis@chromium.org Review URL: http://codereview.chromium.org/8443006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108567 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108391 - Broke 'compile' on Mac clobber builderrsleevi@chromium.org2011-11-031-42/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow javascript unit tests using webui test_api framework. I moved javascript2webui.js over to chrome/test/base/js2gtest.js and shared it across webui and unit tests with an extra parameter for test type, which governs the few differences, such as what to include/subclass from and the flavor of gtest (TEST_F v. IN_PROC_BROWSER_TEST_F). v8_unit_test implemented 2 main methods to make it work with the generated C++ - AddLibrary - loads the file in the test context - RunJavascriptF - launches the runTest with the testFixture and testName, coordinating with Error and ChromeSend to report results. Helper functions: - Error - watches for console.error, noting failure if seen. - ChromeSend - pulls apart the result from the test_api's call to chrome.send('testResult', [ok, msg]) R=arv@chromium.org BUG=87820 TEST=unit_tests --gtest_filter=FrameworkUnitTest.* Review URL: http://codereview.chromium.org/8418015 TBR=scr@chromium.org Review URL: http://codereview.chromium.org/8440060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108407 0039d316-1c4b-4281-b951-d872f2087c98
* Allow javascript unit tests using webui test_api framework.scr@chromium.org2011-11-031-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | I moved javascript2webui.js over to chrome/test/base/js2gtest.js and shared it across webui and unit tests with an extra parameter for test type, which governs the few differences, such as what to include/subclass from and the flavor of gtest (TEST_F v. IN_PROC_BROWSER_TEST_F). v8_unit_test implemented 2 main methods to make it work with the generated C++ - AddLibrary - loads the file in the test context - RunJavascriptF - launches the runTest with the testFixture and testName, coordinating with Error and ChromeSend to report results. Helper functions: - Error - watches for console.error, noting failure if seen. - ChromeSend - pulls apart the result from the test_api's call to chrome.send('testResult', [ok, msg]) R=arv@chromium.org BUG=87820 TEST=unit_tests --gtest_filter=FrameworkUnitTest.* Review URL: http://codereview.chromium.org/8418015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108391 0039d316-1c4b-4281-b951-d872f2087c98