How to use beforeFindBy method of org.openqa.selenium.support.events.AbstractWebDriverEventListener class

The behaviour is intended. Here is how it works -

1. You issue driver.get(B). It triggers the browser to open the webpage and then it doesnt have anything to do with the browser, so it doesnt care whether an alert is open or not.
2. When the page loads, pop-up dialog appears, but nothing happens on your code side or Eclipse.
3. When you try to perform another operation, it interacts with browser and sees an unexpected popup dialog.

Now, the problem occurs that modal dialog closes and still exception occurs, so try the following.

1. Enclose your second operation in a try/catch and handle UnhandledAlertException
2. Inside that catch block, perform, driver -> switch to -> alert -> accept
3. After the catch block, perform the second operation again.

Yes, when you choose Java as your programming language while working with selenium, you can perform all things that are logically possible in Java.

Take your example, xpath is a function which takes string arguments. So Like in Java we concatenate multiple strings using +. you can do the same thing here.

String newUser = "NewUser123";
driver.findElement(By.xpath("//td[normalize-space(text())='"+newUser+"']/a")).click();

You seem to have the PDF Viewer Chrome extension installed which does the PDF renderring if you run Chrome manually. If Chrome is started by chromedriver however, it runs without any browser extensions, which is why in that case you get the default behavior of Chrome (which is to render the PDF by itself).

If you actually need to verify that the PDF is loaded and rendered with that particular extension, then you can use the following method to load the extension also when Chrome is started by chromedriver (code taken from here):

ChromeOptions options = new ChromeOptions();
options.addExtensions(new File("/path/to/extension.crx"));
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(ChromeOptions.CAPABILITY, options);
ChromeDriver driver = new ChromeDriver(capabilities);

See here on how to get the crx file of your extension: Location of CRX in chrome after installation?

Use findElements instead of findElement.

findElements will return an empty list if no matching elements are found instead of an exception.

To check that an element is present, you could try this

Boolean isPresent = driver.findElements(By.yourLocator).size() > 0

This will return true if at least one element is found and false if it does not exist.

The official documentation recommends this method:

findElement should not be used to look for non-present elements, use findElements(By) and assert zero length response instead.

Just specify the path to the binary of the version..may be, like-

FirefoxBinary binary = new FirefoxBinary(new File("path_to_bin"));
FirefoxProfile profile = new FirefoxProfile();
WebDriver driver = new FirefoxDriver(binary, profile);

Until issue is resolved you can bypass this with:

Custom window size

driver.manage().window().setSize(new Dimension(1920, 1080));

You can get screen resolution

Toolkit toolkit = Toolkit.getDefaultToolkit();
int width = (int) toolkit.getScreenSize().getWidth();
int height = (int) toolkit.getScreenSize().getHeight();

Argument to chrome

ChromeOptions options = new ChromeOptions();
options.addArgument("--start-maximized");

Javascript Executor

((JavascriptExecutor) driver).executeScript("if(window.screen){
    window.moveTo(0, 0);
    window.resizeTo(window.screen.availWidth, window.screen.availHeight);
    };");

It should be like this:

for(int i = 1; i <= totalRows; i++) {
    Row row = sheet.getRow(i);
    Cell cell = row.getCell(2);
    if (cell == null) {
        cell = row.createCell(2);
    }
    cell.setCellType(Cell.CELL_TYPE_STRING);
    cell.setCellValue("some value");
}

To save the workbook you could just write:

FileOutputStream fos = new FileOutputStream(fileName);
workbook.write(fos);
fos.close();

You should take a look at POI's Busy Developers' Guide.

This is a common source of XPath confusion. First the straightforward parts:

• //a selects all a elements in the document.
• //a//b selects all b elements in the document that are descendants of a elements.

Normal stuff so far. Next is the tricky part:

1. To select the last b elements among siblings (beneath a elements):

   //a//b[last()]
   

   Here, the filtering is a part of the b selection criteria because [] has a higher precedence than //.

2. To select the last b element in the document (beneath a elements):

   (//a//b)[last()]
   

   Here, the last() is an index on the list of all selected b elements because () is used to override the default precedence.

Try adding the selenium-java dependency to your POM.xml for example:

<dependency>
    <groupId>org.seleniumhq.selenium</groupId>
    <artifactId>selenium-java</artifactId>
    <version>3.141.0</version>
</dependency>

It worked for me!