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.
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
Fix visible commands for Appium. #3566
Fix visible commands for Appium. #3566
Changes from all commits
8a6df55
fe571b7
64132ee
43e4cb8
6782f1b
35bfe4f
199fd3a
e16fbcb
96af4dc
46228d6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use isMobile from utils
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cannot use
isMobile
from utils here because that method only considersdesiredCapabilites
whereas over here we need to check isandroid
orios
is present asplatformName
inside thecapabilities
returned by BrowserStack.This is necessary because users might not explicitly specify
platformName
in theirdesiredCapabilites
(for example, when testing on mobile browser on BrowserStack,platformName
in desired capabilites is not necessary) but BrowserStack would always send back theplatformName
incapabilities
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would also need to tweek
isAndroid()
andisIOS()
methods available in our API accordingly for it to considercapabilities
as well, but that is out of scope of this PR and I'll create a separate issue for that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created an issue here: #3603
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not use api methods here. We can move isAppium client to util and api method can use take use of that util function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following up on the above response, this method cannot be moved to utils in its current form since for handling the BrowserStack case, we'd need the
capabilities
returned by BrowserStack after a session is established with it, and thosecapabilities
are only made available inclient.js
asthis.capabilities
.