android.testOptions.unitTests are ignored for connected.*AndroidTest [64021082]

Fixed

Bug

[AOSP] Version-Studio-2.3

Migrated-Tools-testing

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Jul 25, 2017 04:01PM

Hi,

as the developer guide implies [1] the testOptions.unitTests.all should also be respected in the connected.*AndroidTest.

Current behavior:
The testOptions are _only_ respected for test.*UnitTest task and _not_ for the AndroidTest tasks.

Expected behaviour:
The testOptions _are respected_ for test.*UnitTest task _and_ for the AndroidTest tasks.

Is there a workaround inside the build.gradle to exclude specific tests from execution on the connected.*AndroidTest,
if the testOptions are not working? I tried it to manipulate it on build time, but this could lead to dependency issues.

Kind Regards
Michael

[1]

https://developer.android.com/studio/test/index.html#test_options (second code listing)

Gradle version: 3.3
Android Plugin Version: 2.3.3
Module Compile Sdk Version: API 23
Module Build Tools Version: 25.0.3
Android SDK Tools version: 26.0.2

Comments

mi...@gmail.com <mi...@gmail.com> #2Jul 25, 2017 04:06PM

Maybe the issue #37087605 has the same background.

mi...@gmail.com <mi...@gmail.com> #3Jul 25, 2017 08:42PM

Same holds true for:
Gradle version: 4.1-rc1
Android Plugin Version: 3.0.0-alpha8

uc...@google.com <uc...@google.com> Jul 25, 2017 11:01PM

Assigned to be...@google.com.

be...@google.com <be...@google.com> #4Jul 26, 2017 10:41AM

Reassigned to be...@google.com.

This is WAI, so the issue seems to be with the docs.

Michael - can you explain why you think the docs imply that? The page you linked starts by making the distinction between "local unit tests"
(under src/test) and "instrumented tests" (under src/androidTest). The testOptions.unitTests block is used to configure the former.

As for skipping instrumented tests: this can be done either by @Ignoring them or passing arguments to the instrumentation test runner, for example:

android.defaultConfig {
instrumentationTestRunnerArgument 'notClass' 'com.android.foo.FooTest'
}

See

https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner.html

mi...@gmail.com <mi...@gmail.com> #5Jul 26, 2017 10:59AM

Hi, IMHO the docks imply that because of the code line:
'if (

it.name == 'connectedDebugAndroidTest') {`
inside the android.testOptions.unitTests.all in the second listing of [1]. And the whole paragraph ([1]) talks about unit tests without distinguishing between
local unit tests and instrumented (unit) tests.

[1]

https://developer.android.com/studio/test/index.html#test_options

be...@google.com <be...@google.com> #6Jul 26, 2017 11:07AM

Reassigned to ad...@google.com.

Thanks - that line is definitely wrong. Adarsh - can you assign the bug to the right person?

ad...@google.com <ad...@google.com> #7Jul 28, 2017 07:23PM

Marked as fixed.

Thanks for the catch, all! Docs have been updated :)