[rust] Offline mode in Selenium Manager (#11639) - #12373
Conversation
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## trunk #12373 +/- ##
=======================================
Coverage 57.28% 57.28%
=======================================
Files 86 86
Lines 5333 5333
Branches 193 193
=======================================
Hits 3055 3055
Misses 2085 2085
Partials 193 193 ☔ View full report in Codecov by Sentry. |
|
Excellent! My only concern is would it confuse people to set SE_OFFLINE if it only applies to Selenium manager? I know it follows the convention we use elsewhere, so wondering if a different name might be more clear? |
Yes, the prefix |
|
I think I would prefer that? But I'll agree with whatever Diego thinks is best overall. |
|
I think we can leave |
Description
This PR includes a new flag in Selenium Manager called
--offlinethat forbids making any network call from Selenium Manager. This way, Selenium Manager can only execute shell commands to find drivers in PATH (and browser binary paths).Selenium Manager throws no errors but warnings when the offline mode is enabled. The following snippets showcase its behavior for different cases:
Offline mode with empty cache
Offline mode with driver in cache
Offline mode with driver in PATH
As usual, the flag
--offlineflag is equivalent to using the configuration file (offline = true) or an environment variableSE_OFFLINE=true.Motivation and Context
This PR implements #11639.
Types of changes
Checklist