Add command line options to set appActivity and appPackage capabilities #616
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal
Add command line options to set
appActivityandappPackagecapabilities.Design
Android apps have regularly failed to start with Appium 2, the fix for which is to set the
appActivityandappPackagecapabilities. This isDocumentation
Included in the
helpoutput for the command line options.Changeset
New command line options and associated processing added. Capabilities set in BitBar appium sessions when provided.
Tests
Mostly covered by unit tests and I've also run a simple test locally to verify that the the capabilities are actually set in the session.