[Android] Don't subclass ChromeActivityTestRule in SyncTestRule
Removes subclassing of ChromeActivityTestRule in SyncTestRule. This subclassing meant that every test using SyncTestRule would start ChromeActivity before starting the test. This was producing several issues: 1. It's hard and confusing to use SyncTestRule in tests that start other activity types: FRE tests, bookmark tests, settings tests. 2. It makes tests longer. 3. It might make tests flaky. Some tests need ChromeActivity to be started, so this CL adds a bunch of explicit ChromeTabbedActivityTestRule fields along with calls to startMainActivityOnBlankPage. This CL also fixes and cleans up FirstRunTest. Tests will be enabled in a separate CL (in case they're still flaky). Bug: 616456, 1135990 Change-Id: I5a3d4a27f051cdfc4df2d4dc12a27899084b91db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450291 Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#818891}
Showing
Please register or sign in to comment