New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 615104 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
not available
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Separate BaseInstrumentationTestRunner from BaseChromiumInstrumentationTestRunner

Project Member Reported by yolandyan@chromium.org, May 26 2016

Issue description

Current BaseInstrumentationTestRunner utilize CommandLineFlags.getRegistrationHook() would be default regard/cast the test target apk application as BaseChromiumApplication. However, there are WebView related apks (system webview shell) that doesn't use BaseChromiumApplication as their <application>.

This CL is to separate none BaseChromiumApplication related component from BaseInstrumentationTestRunner, so that the webview related apks can still utilize features like customized test annotations
https://codereview.chromium.org/2013113002
 
Status: Started (was: Untriaged)
After the CL, apks that uses BaseChromiumApplication should use BaseChromiumInstrumentationTestRunner instead of BaseInstrumentationTestRunner
Status: Fixed (was: Started)

Sign in to add a comment