Skip to content

fix: use reliable selenium methods for actions in integration tests #10061

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.

Sign up for GitHub

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

Jump to bottom
Merged
balanikaran merged 9 commits into from
Jan 21, 2026
Merged

fix: use reliable selenium methods for actions in integration tests #10061

balanikaran merged 9 commits into from
Jan 21, 2026

Conversation

@balanikaran
Copy link
Contributor

@balanikaran balanikaran commented Jan 20, 2026 •
edited
Loading

📄 Summary

We have been seeing failures in integration tests due to some active issues with ChromeDriver or/and Selenium, more details here: SeleniumHQ/selenium#15401

  • Use element_to_be_clickable method which is more reliable
  • fix CI webdriver step to correctly replace chromedriver
  • update selenium version

✅ Change Type

Select all that apply

  • ✨ Feature
  • 🐛 Bug fix
  • ♻️ Refactor
  • 🛠️ Infra / Tooling
  • 🧪 Test-only

@github-actions github-actions bot added the bug Something isn't working label Jan 20, 2026
@balanikaran balanikaran added the safe-to-integrate Run integration tests label Jan 20, 2026
@balanikaran balanikaran force-pushed the fix/tests-selenium-issue branch from d066242 to c95ca4a Compare January 20, 2026 16:57
@balanikaran balanikaran added safe-to-integrate Run integration tests and removed safe-to-integrate Run integration tests labels Jan 20, 2026
@balanikaran balanikaran changed the title fix: use reliable selenium methods for actions in integration test fix: use reliable selenium methods for actions in integration tests Jan 20, 2026
@balanikaran balanikaran added safe-to-integrate Run integration tests docs not required and removed safe-to-integrate Run integration tests labels Jan 20, 2026
therealpandey
therealpandey requested changes Jan 20, 2026
View reviewed changes
@balanikaran balanikaran requested a review from a team as a code owner January 20, 2026 19:12
@balanikaran balanikaran added safe-to-integrate Run integration tests and removed safe-to-integrate Run integration tests labels Jan 20, 2026
@balanikaran balanikaran added safe-to-integrate Run integration tests and removed safe-to-integrate Run integration tests labels Jan 20, 2026
@balanikaran
Copy link
Contributor Author

balanikaran commented Jan 20, 2026

This warning is now fixed:

Screenshot 2026-01-21 at 1 04 53 AM

@balanikaran balanikaran force-pushed the fix/tests-selenium-issue branch from 9ee49ff to 7240431 Compare January 20, 2026 19:41
@balanikaran balanikaran added safe-to-integrate Run integration tests and removed safe-to-integrate Run integration tests labels Jan 20, 2026
@vikrantgupta25 vikrantgupta25 added safe-to-integrate Run integration tests and removed safe-to-integrate Run integration tests labels Jan 21, 2026
@balanikaran balanikaran enabled auto-merge (squash) January 21, 2026 06:06
@balanikaran balanikaran merged commit 1417e22 into main Jan 21, 2026
73 of 74 checks passed
@balanikaran balanikaran deleted the fix/tests-selenium-issue branch January 21, 2026 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@therealpandey therealpandey therealpandey approved these changes

@vikrantgupta25 vikrantgupta25 vikrantgupta25 approved these changes

Assignees

No one assigned

Labels

bug Something isn't working docs not required safe-to-integrate Run integration tests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@balanikaran @therealpandey @vikrantgupta25