We’ve started to do regular scheduled test jobs every night on a Windows Server 2019 Edition. These tests run with data sources which create 20 variations of each test, so there’s a lot of testing going on in the night.
However, we regularly (= every night) run into problems. Not because the test runs into testing problems, but because the test itself doesn’t start. It always is the same problem:
WebDriverException: java.net.ConnectException: Connection refused: connect
Usually, this exception kills the test after ~ 5 seconds, and after that happens once, the entire test with all variations as well as the subsequent other tests of the same job fail.
During daytime, we only test with one data source (=one variation of the test) and usually that works just fine. Has anyone run into the same problem and found a solution?