How to use ProfilerLogEntry class of org.openqa.selenium.logging.profiler package

Short answer is that isVisible is method of old Selenium RC and isDisplayed is method of Selenium 2.

If you are talking about WebDrivers WebElement, it contains only isDisplayed() method, which by the doc:

Is this element displayed or not? This method avoids the problem of having to parse an element's "style" attribute.

Before webdriver we had Selenium RC, which is now long deprecated, the DefaultSelenium class had isVisible() method that:

Determines if the specified element is visible. An element can be rendered invisible by setting the CSS "visibility" property to "hidden", or the "display" property to "none", either for the element itself or one if its ancestors. This method will fail if the element is not present.

reference

I met the same issue. cucumber-java 1.2.2 is working for me.

<dependency>
    <groupId>info.cukes</groupId>
    <artifactId>cucumber-java</artifactId>
    <version>1.2.2</version>
</dependency>

1. They are tools to help you organize your tests. You can define what you want to run before/after tests, you can group your tests, and reporting on them is made easier.

2. It is usually mentioned with Selenium because Selenium is a common testing tool. The two work together well, but they are completely separate. (Selenium connects you to your browser, TestNG/JUnit organizes the tests)

3. Yes. You should be able to pick them up. They are designed to be fairly easy to learn.

You can also do like this

    WebDriver driver = new ChromeDriver();

    waitForDriverToClose(driver);

waitForDriverToClose

private static void waitForDriverToClose(WebDriver driver) {
        try {
            WebDriverWait wait = new WebDriverWait(driver, 20);
            wait.until(ExpectedConditions.not(new ExpectedCondition<Boolean>() {
                @Override
                public Boolean apply(WebDriver driver) {
                    try {
                        driver.getTitle();
                        return true;
                    } catch (Exception ex) {
                        System.out.println("Couldn't Connect Driver / Driver Closed");
                        return false;
                    }
                }
            }));
        } catch (org.openqa.selenium.TimeoutException ex) {
            System.out.println("Timeout Trying Again");
            waitForDriverToClose(driver);
        }
    }

You could do something like...

List<WebElement> links = driver.find elements(By.cssSelector('#tblPriorEventsBody td a'));

Iterator<WebElement> iter = links.iterator();

while(iter.hasNext()) {
    WebElement we = iter.next();

    if (we.text.equals("whatever") {
        we.click;
    // do something in else perhaps
    }
}

Ok - per the comments, you specified that you weren't running against the hub, yet, in your code - you point to a hub. I think it has something to do with this.

Change this block of code:

try {
    driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), capabilities);
} catch (MalformedURLException e) {
    // TODO Auto-generated catch block
    e.printStackTrace();
}

to:

driver = new IEDriver(capabilities);

RemoteWebDriver(new URL("http://localhost:4444/wd/hub") this piece here is pointing your test to some remote driver, which means "a selenium node that is connected to a hub." You've already confirmed that this you are not using a hub, so this answer should solve your issue.

A breakdown:

RemoteWebDriver() = Selenium Node that is connected to a hub
ChromeDriver|IEDriver|FirefoxDriver = Local browser session

This error message...

2018-08-31 09:16:26,570 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /crawlerClass/myCrawler/5922: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.

...implies that the ChromeDriver was unable to initiate/spawn a new WebBrowser i.e. Chrome Browser session.

Your base exception is the org.openqa.selenium.WebDriverException as your program Timed out waiting for driver server to start because of the following reason:

• Your JDK version is 1.8.0_92 which is pretty ancient.

So there is a clear mismatch between the JDK v8u92 and current Selenium Client v3.14.0.

Solution

• Upgrade JDK to recent levels JDK 8u181.
• Upgrade Selenium to current levels Version 3.14.0.
• Upgrade ChromeDriver to current ChromeDriver v2.41 level.
• Keep Chrome version between Chrome v66-68 levels. (as per ChromeDriver v2.41 release notes)
• Take a System Reboot.
• Execute your @Test.

Right click(on the Listeners class ) -> go to source-> click on overide/implement methods -> select the check boxes for the ITest listener (make sure all check box inside it should be checked )->click on oK. That's it !!!

One workaround is to set the runOrder parameter to alphabetical and then rename your tests to have alphabetical order.

<plugin>
   <groupId>org.apache.maven.plugins</groupId>
   <artifactId>maven-surefire-plugin</artifactId>
   <configuration>
      <runOrder>alphabetical</runOrder>
   </configuration>
</plugin>

This isn't recommended, though - unit tests should be independent of each other. The execution order shouldn't matter.