Inconsistency is the topic here. I have a large Selenium test suite that gives me problems on Mac. My employees use Windows and they have no problem with that. In fact, when I run the entire set using TestNG, the tests behave differently than every time I run. Individually, the tests are completed without any problems. When run as a whole set, there are currently about ten tests, the third test that will be executed always freezes in the same place. It tries to find an element and never exits the Selenium API. A point with no return is marked XXXbelow.
driver.manage().timeouts().pageLoadTimeout(20000, TimeUnit.MILLISECONDS);
driver.manage().timeouts().implicitlyWait(0, TimeUnit.SECONDS);
try {
element = driver.findElement(By.xpath(xpathLocator));
} catch (NoSuchElementException | org.openqa.selenium.TimeoutException e)
Dialing does not start in parallel. The same behavior is observed in Chrome, Firefox and Safari, although the element that is requested when the program freezes varies between browsers. I am currently using Mac 10.10.6 with the latest versions of Selenium, Eclipse, and TestNG. The same behavior occurs on individual Mac computers. The behavior is the same regardless of whether I run the TestNG suite in Eclipse or from the command line. The whole package runs without any problems when logging is enabled in node via-log someFileor when node is running on a remote computer, i.e. not locally. The set is quite large, so if there is other code that I can post here, which would be useful in diagnosing the problem, please let me know. Any ideas pointing me in the right direction will be very helpful.