SeleniumHQ / SeleniumHQ/selenium

[🚀 Feature]: Testing Selenium Manager

Open
#16,741 3 comments 0 reactions 1 assignee Claimed by @titusfortner View on GitHub
B-build B-manager C-dotnet C-java C-nodejs C-py C-rb I-enhancement
Dominant language
Java
Stars
34.5k
Forks
8.7k
Avg merge
2d 1h
Merged PRs (30d)
92

Description

### Description

We made a change here to always use pin_browsers in CI: https://github.com/SeleniumHQ/selenium/pull/15987

~This removed all testing of Selenium Manager.~ This removed testing our suites with Selenium Manager.

Ideally each binding has Service class tests that exercise Selenium Manager (some of them seem to do this already), and these tests will only work on GitHub Actions and not on RBE.

### Have you considered any alternatives or workarounds?

I think we may want to make pin_browsers the default for Bazel, and explicitly set it to false for Selenium Manager tests:
implemented the first part here: #16743

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.