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

[🐛 Bug]: Improve Appium - Selenium integration tests #11453

Closed
nir-tal-talkspace opened this issue Dec 20, 2022 · 3 comments
Closed

[🐛 Bug]: Improve Appium - Selenium integration tests #11453

nir-tal-talkspace opened this issue Dec 20, 2022 · 3 comments

Comments

@nir-tal-talkspace
Copy link
Contributor

What happened?

As a result of appium/java-client#1823
Appium always pulls the latest Selenium version - and there is no way to override this (I used the dependency management tag in the pom.xml for Selenium and also try to exclude it from Appium dependency).
The Appium client will fail if there are deprecation tickets that weren't implemented
Here is an example:
#11347

A native mobile-web cross-platform test is performed on our project using Chrome devtools (which forces us to use the most recent version of Selenium).
As a result, devtools-related bugs can also terminate our mobile efforts, such as this one:
#11401

From a Selenium perspective, I wonder if there is a better way to test Appium. prior to this implementation:
#11355

Thanks.

How can we reproduce the issue?

N/A

Relevant log output

N/A

Operating System

N/A

Selenium version

N/A

What are the browser(s) and version(s) where you see this issue?

N/A

What are the browser driver(s) and version(s) where you see this issue?

N/A

Are you using Selenium Grid?

No response

@nir-tal-talkspace nir-tal-talkspace changed the title [🐛 Bug]: Improve Appium - Selenium integration [🐛 Bug]: Improve Appium - Selenium integration tests Dec 20, 2022
@github-actions
Copy link

@nir-tal-talkspace, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@nir-tal-talkspace
Copy link
Contributor Author

@titusfortner
Copy link
Member

The fix we have planned for this issue is #11355. If you have a specific suggestion for what else we can do differently, I think both projects would be receptive. Questions or discussions for alternatives should be in either Selenium or Appium Slack, not in a Github issue.

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

No branches or pull requests

2 participants