Deprecate direct usage of ChromeActivityTestRule
I'm doing a series of cleanups on ChromeActivityTestRule. 1. ActivityTestRules are supposed to take in the exact class to be launched - we hack around this in ChromeActivityTestRule, but we really don't need to and it's confusing for those familiar with ActivityTestRule. To this end I plan to prevent directly using ChromeActivityTestRule in favor of derived classes specific to the Activity you actually want to launch. 2. (Almost) All existing usage of ChromeActivityTestRule is actually using ChromeTabbedActivity, and so should be using ChromeTabbedActivityTestRule. 3. A bunch of functions on ChromeActivityTestRule only apply to ChromeTabbedActivity, so I'll be moving the functions to ChromeTabbedActivityTestRule instead. 4. Right now some types of ActivityTestRule will finish the Activity between tests, and some won't (for batched tests). I intend to make this behavior consistent for all ActivityTestRules. This change kicks this off by deprecating the public ChromeActivityTestRule constructor and migrating some of the usages. A few followups will get the remainder of the usages as there are many. Bug: 989569 Change-Id: Ia16a252f0d77a053dc9e1733d52d8ea290574a48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435724Reviewed-by:Andrew Grieve <agrieve@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#811860}
Showing
Please register or sign in to comment