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

QE: Update selenium-webdriver version to 4.27 #9569

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nodeg
Copy link
Member

@nodeg nodeg commented Dec 13, 2024

What does this PR change?

This updates the selenium-webdriver version from 4.24 to 4.27.

4.27.0 (2024-11-21)
=========================
* Add CDP for Chrome 131 and remove 128
* Add Firefox CDP deprecation warnings (#14763)
* Add Bidi network commands for authentication and interception (#14523)
* Handle graceful webdriver shutdown (#14430)
* Reduce RBS errors to 0 (#14661)
* Resolve `uri` gem deprecation warning (#14770)
* Update minimum Ruby to 3.1 (#14685)
* Implement navigation commands with BiDi (#14094)

4.26.0 (2024-10-28)
=========================
* Add CDP for Chrome 130 and remove 127
* Add missing RBS methods (#14621)
* Update Ruby BiDi script structs to match spec
* Add RBS type support for BiDi related classes (#14611)

4.25.0 (2024-09-19)
=========================
* Add CDP for Chrome 129 and remove 126
* Fix add_cause method not being able to process an array of hashes (#14433)
* replace `fedcm` links with new ones (#14478)
* Allow driver path to be set using ENV variables (#14287)

https://github.com/SeleniumHQ/selenium/blob/trunk/rb/CHANGES

Since we always use the latest chromedriver, it makes sense to bump the selenium-webdriver version from time to time, too.

suma-ci-head-controller:~ # rpm -qi chromedriver
Name        : chromedriver
Version     : 131.0.6778.108
Release     : bp155.2.147.1
Architecture: x86_64

GUI diff

No difference.

  • DONE

Documentation

  • No documentation needed: only internal and user invisible changes

  • DONE

Test coverage

ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite

  • Cucumber tests were added/edited

  • DONE

Links

Port(s): Manager 5, Manager 4.3

  • DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

  • No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

  • Re-run test "changelog_test"
  • Re-run test "backend_unittests_pgsql"
  • Re-run test "java_pgsql_tests"
  • Re-run test "schema_migration_test_pgsql"
  • Re-run test "susemanager_unittests"
  • Re-run test "javascript_lint"
  • Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

@nodeg nodeg self-assigned this Dec 13, 2024
Copy link
Contributor

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (aprox. 1h), please be patient ☕
You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/9569/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/9569/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

KNOWN ISSUES

Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience.

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!
⚠️ You should not merge if acceptance tests fail to pass. ⚠️

@nodeg nodeg marked this pull request as ready for review December 13, 2024 10:44
@nodeg nodeg requested a review from a team as a code owner December 13, 2024 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant