Some related issues:
  *  issue 841628 : Combine chrome_public_test_apk with chrome_public_for_test_apk
  *  issue 833545 : Get rid of chrome_sync_shell
  * issue 688465: Stop -keeping all Java native methods (weird proguard apk/apk_under_test interaction)

Idea here is that we'll still have the apk_under_test variable exposed to the instrumentation_test_apk target but then we'll just use the apk_under_test to build the final apk.

The test_runner should be a little simpler after this.

Any reason to not do this?
 

Some related issues:
  *  issue 841628 : Combine chrome_public_test_apk with chrome_public_for_test_apk
  *  issue 833545 : Get rid of chrome_sync_shell
  * issue 688465: Stop -keeping all Java native methods (weird proguard apk/apk_under_test interaction)

Idea here is that we'll still have the apk_under_test variable exposed to the instrumentation_test_apk template but then we'll use parts of the apk_under_test to build the final apk.

The test_runner should be a little simpler after this.

Any reason to not do this?