How to use SpanWrappedRoutable class of org.openqa.selenium.remote.tracing package

One other way to launch chrome in incognito mode is to add argument "-incognito" like following:

ChromeOptions options = new ChromeOptions();
options.addArguments("--incognito");
DesiredCapabilities capabilities = DesiredCapabilities.chrome();
capabilities.setCapability(ChromeOptions.CAPABILITY, options);

This solution works for me.

Naif,

Actually, your above question is different than the actual question hence you should have asked it as a separate question. Still, I'm answering to your previous question.

The error is because the element you're trying to click on isn't visible. Before you click on element, it should be visible. You can do this by following -

WebElement element = driver.findElement(By.xpath("//div[2]/div[2]"));
WebDriverWait wait = new WebDriverWait(driver, 20); //here, wait time is 20 seconds

wait.until(ExpectedConditions.visibilityOf(element)); //this will wait for elememt to be visible for 20 seconds
element.click(); //now it clicks on element

If above doesn't work, you can click on element by executing javascript(but this isn't a good practice)

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("arguments[0].click();", element);

Unfortunately the Selenium WebDriver designers explicitly decided not to include this functionality in Selenium 2.

It's a deliberate decision to not include this feature in WebDriver, since it's usually a hack to work around synthesized events not behaving properly. We'd rather eliminate this need by providing great support for native events, so we'll continue improving that going forward. A user would never fire a focus event, they would click the form control. That's what your tests should be doing as well.

With that said, you can execute any javascript code you want. Thus you should look into how to fire events with javascript. Take at look at this StackOverflow question for inspiration.

Then you can do something like this:

FirefoxDriver driver = new FirefoxDriver();
driver.ExecuteScript("[your fire event javascript code]");

I'm sure you could create a wrapper function to basically accomplish the same thing as fireEvent.

I've run into the same issue.

Apparently Chrome automatically updates itself. Yesterday (Oct 29 '19) My ChromeDriver started complaining that it was not compatible with Chrome 78. I updated the driver to the 78 version. I started to get random org.openqa.selenium.NoSuchElementException exceptions when trying to find elements that I confirmed were there. The findElement[s] also work when I used breakpoints. I also tried implicit waits, with only limited success.

I tried zsbappa's ChromeOption solution but no joy.

Google makes it hard to get old versions of Chrome, but I found version 76 at https://www.neowin.net/news/google-chrome-76-offline-installer/. Beware, the online installer installs the latest version. I reverted to the driver for 76 and all is good. All my Selenium tests are working again.

My conclusion is that the Chrome 78 and it's associated driver has a race condition where Selenium attempts to interrogate the web page before it's complete.

You have to give your chromeDriver.exe file path instead of taking the path from the URL.

example:

 System.setProperty("webdriver.chrome.driver",
            "C:\\Downloads\\chromedriver.exe");

You can try this one too as CSS Selector

driver.findElement(By.cssSelector("input[type='button'][value='Open device access']")).click();

or

driver.findElement(By.cssSelector("input[type='button']")).click();

Each time, before you change page, retrieve the text, i.e, the number of records. Then, Click on the Next button to navigate to the next page. And then, wait for that to be invisible using explicit wait.

Below code might help you out:

String retrieved_text = driver.findElement(By.xpath("//xpath of the element related to records")).getText(); //Retrieving text, i.e., the innerHtml representing number of records

/*Click on the next button to navigate to the next page*/
driver.findElement(By.xpath("//next button's xpath")).click();

WebDriverWait wait = new WebDriverWait(driver,30);
wait.until(ExpectedConditions.invisibilityOfElementWithText(By.xpath("//xpath of the element related to records"), retrieved_text)); 

NOTE: In the last line of code use xpath that locates the element that shows text 'displaying 1-10 of 2100', i.e, the element that shows display per page information and use the retrieve text to infer that the concerned element with that certain text is invisible or not in the next page.

This will help in identifying the invisibility of the concerned element easily.

OTHER WAY: In case you want to navigate to next pages till you detect a certain element

(PUT EVERYTHING IN A DO-WHILE LOOP)

• Wait for the element to appear in the page.
• If found, then write code to act on the element and break out of loop.
• Else, click on the Next button
• CONDITION will be till the NEXT button gets disabled.

I could notice that you haven't closed your InputStream. If you do not close the stream, file will be locked until inputstream has been closed or JVM is shutdown.

So probably, the easiest thing in your context above is to auto-close by using a try-with-resources construct as,

try (FileInputStream inp = new FileInputStream(workbookPath)) {
    tempWB = (org.apache.poi.ss.usermodel.Workbook) new HSSFWorkbook(new POIFSFileSystem(inp)); 
} catch (Exception e) {
    Log.error("Class Utils | Method setExcelFile | Exception desc : "+ e.getMessage());
}

Hope it helps you. :)

One of the differences between Katalon and groovy is that groovy is lightweight as compared to Katalon. Since Katalon offers variety of features in a container, it is easier to use. Scripting is very much encapsulated within it. Groovy on other had provides many features for testing - Do check out Spock (http://spockframework.org) which is mainly used for testing Java/Groovy applications.

In a nut shell; which should be chosen really depends on the team composition of programmers, tech stack on which your app is built, maintainability of the application in scope. Hope it helps...