summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browsing_data_remover_unittest.cc
Commit message (Expand)AuthorAgeFilesLines
* Fix a build break from http://codereview.chromium.org/7740084/ .erikwright@chromium.org2011-09-021-1/+1
* Re-landing http://codereview.chromium.org/7210034/ , which was reverted due t...erikwright@chromium.org2011-09-021-15/+104
* Switch ChromeTestSuite to the same convention as ContentTestSuite:phajdan.jr@chromium.org2011-08-271-2/+1
* Reorganize chrome/test, part #9phajdan.jr@chromium.org2011-08-111-1/+1
* Revert 96035 - Update BrowsingDataRemover with the asynchronous CookieMonster...fischman@chromium.org2011-08-091-92/+3
* Update BrowsingDataRemover with the asynchronous CookieMonster API.ycxiao@chromium.org2011-08-091-3/+92
* GTTF: Use a fresh TestingBrowserProcess for each test, part #4phajdan.jr@chromium.org2011-08-031-1/+2
* Move more files from chrome/test to chrome/test/base, part #4phajdan.jr@chromium.org2011-08-011-1/+1
* Time-based removal of temporary file systems via BrowsingDataRemovermkwst@chromium.org2011-08-011-121/+209
* The problem:marja@google.com2011-07-221-102/+13
* Adding a test for the appcache removal functionality of BrowsingDataRemover.marja@google.com2011-07-121-0/+147
* Integrate file systems with BrowsingDataRemovermkwst@chromium.org2011-06-071-18/+139
* Breaking the BrowserDataRemover test out into modular pieces.mkwst@chromium.org2011-06-011-31/+99
* Add unit test for removing history via BrowsingDataRemoverjochen@chromium.org2011-05-301-0/+78