While quitting in an ensure/finally block would be the safest option, configuring the idle timeout for your browser session would be a good safety release. See the section on timeouts in the Grid 2 wiki page:
how do I quit a web driver session after the code has finished executing?
-
28-09-2022 - |
Question
We're using Selenium's Python bindings at work. Occasionally I forget to put the call to WebDriver.quit() in a finally clause, or the tear down for a test. Something bad happens, an exception is thrown, and the session is abandoned and stuck as "in use" on the grid.
How can I quit those sessions and return them to being available for use without restarting the grid server?
La solution
Autres conseils
You can restart the node instead of the server.
Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow