Motivation
Follow-up to #17832/#17833. That PR's round-2 review pass fixed the identical fixture-hygiene gap (test setup only saving/clearing selenium.debug, not its legacy alias selenium.webdriver.verbose) in LoggingOptionsTest.java, RemoteWebDriverInitializationTest.java, and RetryRequestTest.java.
java/test/org/openqa/selenium/remote/service/DriverFinderTest.java:81-100 has the same gap: its property save/restore only handles selenium.debug, so a JVM with selenium.webdriver.verbose set externally could leak state across tests in this file. It was out of scope for the round-2 coder (not in the original findings list) so it's tracked here rather than fixed silently.
Suggested fix
Mirror the fixture pattern already applied to the three files above: save both properties before the test, clear both, restore both after.
Context
Umbrella tracker: #17833
Motivation
Follow-up to #17832/#17833. That PR's round-2 review pass fixed the identical fixture-hygiene gap (test setup only saving/clearing
selenium.debug, not its legacy aliasselenium.webdriver.verbose) inLoggingOptionsTest.java,RemoteWebDriverInitializationTest.java, andRetryRequestTest.java.java/test/org/openqa/selenium/remote/service/DriverFinderTest.java:81-100has the same gap: its property save/restore only handlesselenium.debug, so a JVM withselenium.webdriver.verboseset externally could leak state across tests in this file. It was out of scope for the round-2 coder (not in the original findings list) so it's tracked here rather than fixed silently.Suggested fix
Mirror the fixture pattern already applied to the three files above: save both properties before the test, clear both, restore both after.
Context
Umbrella tracker: #17833