SyncFakeServerTestCase: setup/teardown cleanup Before this CL, the setup and teardown logic in SyncFakeServerTestCase was a bit inconsistent: A bunch of cleanup was done in both setUp and tearDown (redundant), but clearBookmarks was only called in tearDown (inconsistent). After this CL, the same cleanup is done once in setUpForTestCase, i.e. before any of the tests in this file run, and then once in tearDown, i.e. after each individual test. Bug: 1486420 Change-Id: Iaa460c2814959972b558aed561dc6d9843318c02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5130054 Reviewed-by: Gauthier Ambard <gambard@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/main@{#1238586}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.