Test Orchestrator Should Run "pm clear" After Each Test [77549481]

Fixed

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Apr 4, 2018 04:23PM

Android Test Orchestrator should run "pm clear" after each test to reset app data and shared prefs. The original documentation stated that this step would be done for completeness, and it's needed to clear all state and remove dependencies between tests.

Refer to this thread for some history:

https://groups.google.com/forum/#!topic/android-testing-support-library/VUT97mrwWQY

Comments

gg...@google.com <gg...@google.com> Apr 5, 2018 06:48AM

Assigned to gg...@google.com.

gg...@google.com <gg...@google.com> #2Apr 5, 2018 09:12AM

Is this not a bug in AGP? It doesnt feel like an androidx issue.

nk...@google.com <nk...@google.com> #3Apr 5, 2018 06:04PM

Reassigned to nk...@google.com.

Probably yes, feel free to reroute or CC the right people. I was not 100% sure since the project uses the androidXMultiplatform DSL, but looking at the DSL it simply forwards things to AGP.

dn...@google.com <dn...@google.com> #4Apr 16, 2018 02:30PM

Do you have an example of what a broken consuming project looks like? which plugins are they applying?

nk...@google.com <nk...@google.com> #5Apr 16, 2018 09:30PM

Marked as fixed.

I've uploaded a sample project, to repro run: ./gradlew test

It is a simple Kotlin JVM project, it only uses plugins { kotlin("jvm") version "2.1.10" }

I was also able confirm that without AGP KMP (aosp/3493350) the project works as expected.

we...@gmail.com <we...@gmail.com> #6Aug 30, 2018 07:13AM

Looking at the Gradle metadata diff (https://diff.googleplex.com/#key=EY2FqaJWQbUQ), maybe the issue is the addition of "org.gradle.libraryelements": "jar" ? Should that be an aar instead? ` https://screenshot.googleplex.com/hjNF5GgDDC5CYEt

ta...@gmail.com <ta...@gmail.com> #7Apr 9, 2019 09:44PM

yes, androidApiElements/runtimeElements variant publications should have aar value on the libraryelements attribute. What version of Gradle, AGP, KGP are you using in your library?

What's bizarre is that the compileClasspath is using the jvm vairant (in the test project you shared), it's only at runtime that it resolves the -android artifact of your library...