diff options
author | skerner@chromium.org <skerner@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-17 16:13:57 +0000 |
---|---|---|
committer | skerner@chromium.org <skerner@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-17 16:13:57 +0000 |
commit | f8d73bc892048b4c5398b90d2978e3bda8317a66 (patch) | |
tree | b5a950da532dd3abb4e08a5f8aaed995963add87 /chrome/browser/background_contents_service.h | |
parent | b3e2d5c802b83d8873e61db78a21ce2600ffb77c (diff) | |
download | chromium_src-f8d73bc892048b4c5398b90d2978e3bda8317a66.zip chromium_src-f8d73bc892048b4c5398b90d2978e3bda8317a66.tar.gz chromium_src-f8d73bc892048b4c5398b90d2978e3bda8317a66.tar.bz2 |
Test download manager fetching CRXes.
First round of tests for the download manager handling CRXes.
Platform-specific UI interactions are not covered by these tests. It would be nice to test that animations are running. I can't see a way to do that without adding accessors to the platform-specific download item UI classes. Paweł, you expressed concern about *ForTesting() methods before. Is there a better way to test that animations are working?
BUG=80010
TEST=DownloadTest.Crx*
Review URL: http://codereview.chromium.org/7104060
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@89496 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/background_contents_service.h')
0 files changed, 0 insertions, 0 deletions