使用 Android Studio 3.1 开发 AOSP 无法为插桩测试构建测试 apk [英] Developing AOSP with Android Studio 3.1 Cannot build test apk for instrumented tests

问题描述

我正在尝试使用 Android Studio 构建一个定制的 AOSP(在 Android M，api 23 上)，因为我想在硬件上运行的定制应用程序上运行仪器测试.这是在 ubuntu 64 上.这对我来说非常令人沮丧，因为没有明确的路径.

I am trying to build a customized AOSP (on Android M, api 23) using Android Studio because I want to run instrumented tests on custom apps running on the hardware. This is on ubuntu 64. It is very frustrating for me as there is no clear cut path.

我的目标:我想遵循本 AS 用户指南中的步骤 用于仪器测试.

My goal: I want to follow the steps in this AS user guide for instrumented tests.

我运行了脚本

~/myAOSP/development/tools/idegen/intellij-gen.sh myApp company/apps/MY_APP

~/myAOSP/development/tools/idegen/intellij-gen.sh myApp company/apps/MY_APP

并在 Android Studio 中打开 MY_APP.iml.

and opened MY_APP.iml in Android Studio.

现在我正在尝试使用 gradle 为我的项目构建 apk，还有测试 apk.

Now I am trying to build the apk using gradle just for my project, and also the test apk.

主要的 myAOSP 使用 makefile.

我按照此处的说明操作，并使用 build.gradle 作为模板 https://developer.android.com/studio/intro/migrate#migrate-intellij

I followed the instructions here and also used the build.gradle as a template https://developer.android.com/studio/intro/migrate#migrate-intellij

// This buildscript{} block configures the code driving the build
buildscript {
   /**
    * The nested repositories{} block declares that this build uses the
    * jcenter repository.
    */
    repositories {
        jcenter()
        google()
    }

   /**
    * This block declares a dependency on the 3.1.0 version
    * of the Gradle plugin for the buildscript.
    */
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.2'
    }
}

/**
 * This line applies the com.android.application plugin. Note that you should
 * only apply the com.android.application plugin. Applying the Java plugin as
 * well will result in a build error.
 */
apply plugin: 'com.android.application'

/**
 * This dependencies block includes any dependencies for the project itself. The
 * following line includes all the JAR files in the libs directory.
 */
dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    testImplementation 'junit:junit:4.12'
    // Add other library dependencies here (see the next step)
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
}

/**
 * The android{} block configures all of the parameters for the Android build.
 * You must provide a value for at least the compilation target.
 */
android {
    compileSdkVersion 23
    buildToolsVersion '27.0.3'
    defaultConfig {
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    /**
    * This nested sourceSets block points the source code directories to the
    * existing folders in the project, instead of using the default new
    * organization.
    */
    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
            java.srcDirs = ['src']
            resources.srcDirs = ['src']
            aidl.srcDirs = ['src']
            renderscript.srcDirs = ['src']
            res.srcDirs = ['res']
            assets.srcDirs = ['assets']
        }

        // Move the tests to tests/java, tests/res, etc...
        androidTest.setRoot('tests')

       /**
        * Move the build types to build-types/<type>
        * For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ...
        * This moves them out of them default location under src/<type>/... which would
        * conflict with src/ being used by the main source set.
        * Adding new build types or product flavors should be accompanied
        * by a similar customization.
        */
        debug.setRoot('build-types/debug')
        release.setRoot('build-types/release')
     }
}

repositories {
    jcenter()
    google()
}

还有一个 gradle 错误:由于 Android M 是用 JDK 1.7 构建的，但 Android Studio gradle 使用 1.8，我按照步骤操作但出现了 gradle 错误，Could not set unknown property 'sourceCompatibility' for root project 'MY_PROJECT' of`输入org.gradle.api.Project.docs.gradle.org/current/userguide/building_java_projects.html # 在 $HOME/.gradle/gradle.propertiesjavaHome=/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home

There was also a gradle error: Since Android M is being built with JDK 1.7 but Android Studio gradle uses 1.8, I followed the steps but had gradle error, Could not set unknown property 'sourceCompatibility' for root project 'MY_PROJECT' of `type org.gradle.api.Project. docs.gradle.org/current/userguide/building_java_projects.html # in $HOME/.gradle/gradle.properties javaHome=/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home

targetJavaVersion=1.7 build.gradle sourceCompatibility = targetJavaVersion –`

targetJavaVersion=1.7 build.gradle sourceCompatibility = targetJavaVersion –`

我看到了类似使用 Android Studio 开发 AOSP 之类的帖子，但它们已经过时了日期或不相关.还有 http://ronubo.blogspot.com/2016/01/debugging-aosp-platform-code-with.html?view=magazine 和 错误:(23, 17) 无法解析:junit:junit:4.12

I saw posts like Developing AOSP with Android Studio but they are out of date or not relevant. Also http://ronubo.blogspot.com/2016/01/debugging-aosp-platform-code-with.html?view=magazine and Error:(23, 17) Failed to resolve: junit:junit:4.12

我正在寻找一个可行的解决方案，用于在 Android Studio 3.1(或更高版本)中为自定义 AOSP 中的应用构建检测测试 apk，并在其上运行检测测试.

I am looking for a working solution to the problem of building an instrumented test apk for an app in customized AOSP, and running instrumented tests on it, in Android Studio 3.1 (or later).

a) 如果可以在 gradle AS 3.1(或更高版本)中构建检测测试 apk，那么请建议修复显示的 gradle 错误.

a) if it is possible to build the instrumented test apk in gradle AS 3.1 (or later), then please suggest a fix to the gradle error shown.

b) 如果上面 a) 中的 gradle 构建是不可能的，那么我是否需要使用自定义 AOSP 中的当前 makefile 构建检测的测试 apk?

b) if gradle build in a) above is NOT possible, then do I need to build instrumented test apk using the current makefiles in the customized AOSP?

c) 如果我使用 makefile 构建插装测试 apk，那么我还可以使用 AS 中的插装 UI 在硬件上运行测试吗?

c) if I build the instrumented test apk using makefiles, then can I still use the instrumentation UI in AS to run the tests on the hardware?

推荐答案

是的，可以在 AOSP 中使用 Gradle 构建应用 APK 和测试应用 APK，但难度取决于它们的依赖关系，即 Makefile 可能引用的位置对于预先构建的二进制文件或 AOSP 中的其他模块，公共 Maven 存储库中可能没有等效的依赖项，因此您需要通过其他方式引入这些依赖项.如果您的应用是系统应用，则您需要为签名步骤提供平台签名.

Yes, it's possible to build an app APK and a test app APK with Gradle in AOSP, but the difficulty depends on their dependencies, i.e. where the Makefile may refer to a pre-built binary or another module in AOSP, there may not be an equivalent dependency in the public Maven repos so you'll need to pull in those dependencies by other means. And if your app is a system app, you'll need to provide the platform signature for the signing step.

a) 您收到的 Gradle 错误是什么?哪个 Gradle 任务给了你这个错误?

a) What is the Gradle error you're getting? And which Gradle task gives you that error?

b) 您可以设置一个 Makefile 来构建已检测的 APK，例如查看它是如何完成的 此处.您还可以使用贸易联盟框架来处理执行和报告生成 - 但您不会在 AS 中获得集成.

b) You can set up a Makefile to just build the instrumented APK, for example see how it's done here. You can also use the Trade Federation framework to handle the execution and report generation - but you won't get the integration in AS.

c) 通过检测 UI，您是指使用播放按钮"开始测试，还是在测试运行时实时显示测试结果?如果您的意思是显示实时结果，那么我认为这是不可能的 - 据我所知，这取决于 connectedAndroidTest 任务.如果您只想执行测试，您可以创建一个自定义 Gradle 任务，该任务只运行adb shell am instrument ..."命令.

c) By instrumentation UI, do you mean starting the tests with the "play button", or showing the test results live as the tests are running? If you mean showing the live results, then I don't believe that's possible - as far as I know it depends on the connectedAndroidTest task. If you just want to execute tests you can create a custom Gradle task that just runs the "adb shell am instrument ..." command.

这篇关于使用 Android Studio 3.1 开发 AOSP 无法为插桩测试构建测试 apk的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！