Skip to content

ci: Run tests against latest Selenium release #1978

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

Merged
merged 1 commit into from
Aug 18, 2023

Conversation

valfirst
Copy link
Collaborator

@valfirst valfirst commented Aug 8, 2023

Change list

Make sure to run tests against the latest Selenium release.

Types of changes

What types of changes are you proposing/introducing to Java client?
Put an x in the boxes that apply

  • No changes in production code.
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Details

  • Make sure to run tests against the latest Selenium release
  • Once new version of Selenium is out, dependabot will create a PR bumping Selenium

in this way it will be possible to test integration with latest Selenium clients in automated way

@valfirst
Copy link
Collaborator Author

@mykola-mokhnach @saikrishna321 @SrinivasanTarget could you please review the changes?

@saikrishna321
Copy link
Member

LGTM

prefer "${seleniumVersion}"
}
}
testImplementation platform(group: 'org.seleniumhq.selenium', name: 'selenium-bom', version: '4.11.0')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure you want to merge this? how about seleniumVersion then?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seleniumVersion will be used in published POM and will declare minimal support version of Selenium
as for the test stage Gradle will resolve conflicts and will pick up the latest version (== declared in test scope), so all tests will be run against the latest version

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is only for tests then should be ok

@valfirst valfirst merged commit 547e063 into appium:master Aug 18, 2023
@valfirst valfirst deleted the ci-run-tests-against-selenium-4-11 branch August 18, 2023 12:20
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

Successfully merging this pull request may close these issues.

3 participants