This repository was archived by the owner on Dec 7, 2019. It is now read-only.
Adding support for Android Test Orchestrator#157
Merged
yunikkk merged 2 commits intogojuno:masterfrom Oct 14, 2018
Merged
Conversation
pazone
approved these changes
Sep 24, 2018
Contributor
|
@jonas-m- would you add some unit tests? |
Contributor
Author
Sure - will do |
Contributor
|
@jonas-m- sorry again for the delays, finally can handle the PR. Weird enough that issue with orchestrator not printing output is resolved but issue https://issuetracker.google.com/issues/64486480 is not closed) Thanks a lot for contribution! |
yunikkk
approved these changes
Oct 14, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes #90, closes #131 and closes #135
Tested in production - works perfectly, also the report generation
One point of uncertainty - the requirement to install test orchestrator and test services APKs before running the tests. I'm not convinced that this should be something
composeritself should be concerned with, as those APKs just need to be installed, no parsing is done on them otherwise (as opposed to normal app/test APKs)The installation can either be done manually (as described in the official docs) OR, if used with Gradle - with a custom task, something like this: