Skip to content

[🚀 Feature]: Testing Selenium Manager #16741

@titusfortner

Description

@titusfortner

Description

We made a change here to always use pin_browsers in CI: #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

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-buildIncludes scripting, bazel and CI integrationsB-managerSelenium ManagerC-dotnet.NET BindingsC-javaJava BindingsC-nodejsJavaScript BindingsC-pyPython BindingsC-rbRuby BindingsI-enhancementSomething could be better

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions