Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple module support #141

Open
jannisveerkamp opened this issue Dec 15, 2021 · 1 comment
Open

Multiple module support #141

jannisveerkamp opened this issue Dec 15, 2021 · 1 comment

Comments

@jannisveerkamp
Copy link

I want to use the Plugin for instrumentation tests in multiple gradle modules.

I'm not sure if I'm missing something, but I would need to add the plugin to each module.

When I invoke the connectedAndroidTest task it will generate and start an Emulator instance for each module.

I also tried to run the Emulator manually, e.g.:

./gradlew feature1:waitForAndroidEmulator
./gradlew connectedAndroidTest
./gradlew feature1:stopAndroidEmulator

or

./gradlew feature1:waitForAndroidEmulator connectedAndroidTest

But it seems the waitForAndroidEmulator is finalized by stopAndroidEmulator already (see here)

Is there any way to prevent the automatic closing of the emulator or some way to run the emulator module independent, e.g. config and start from the root build.gradle file?

@quittle
Copy link
Owner

quittle commented Dec 15, 2021

Hey, thanks for reaching out. No, this is not currently a supported usecase but I suppose it would be possible. I'm not actively developing on the plugin but if you are interested in contributing, I'd be happy to help you implement it yourself and review your changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants