davideDimolaFincons
davideDimolaFincons
Yes, the session is closed only in the afterEach() lifecycle of Jest, so there's no way this can happened during the test. By the way, from further analisys it seems...
I've increased the session timeout by starting nodes and hub in this way (windows machine): ``` start "Selenium HUB" java -jar .\selenium-server.jar hub --session-request-timeout 600 --log "hub.log" --log-level "CONFIG" start...
> In seconds. > > What do the warnings say? You can check them in the first comment of mine in this issue
> It looks like you are trying to execute JS in the browser, and it returns a 404. For some reason, the session timeout kicks off and it ends. >...