How to use getDefaultConfig method of org.openqa.selenium.grid.distributor.httpd.DistributorServer class

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. :)

Use .getOptions() method and store them in a list .Then find its size.

Select se = new Select(driver.findElement(By.id("select drop down locator")));

List<WebElement> l = se.getOptions();
l.size();

-Ajay

There are few types of waitFor available in Selenium. In your test case if you are aware that a particular text would appear on page load you can use waitForText. If there are different DOM elements getting populated (via Ajax/pageload) you can sequentially add waitForText.

LE: I see quite a lot of people are interested in the full-page screenshot, so I thought I might update the answer with some positives (silver bullets).

There are quite a handful of web testing frameworks that can (with minimal setup & effort) produce a full-page screenshot. I come from a NodeJS testing environment, so I can only vouch the following: WebdriverIO & Google's Puppeteer.

If anyone is interested in an easy way to do it with WebdriverIO, check this answer.

Short answer is NO, YOU CANNOT, if you're only using Selenium (detailed reason bellow). But, what you can do is make the most out of your device's(monitor) viewport.

So, start your browser instance (driver) using ChromeOptions(), which is the method for setting ChromeDriver-specific capabilities. We can do the following:

• maximize the window (using the --start-maximized switch);
• go full-screen (F11-key on Windows, Control+Cmd+F on Mac, using the --start-fullscreen switch).
• Note: complete list of Chrome command-line-switches can be found here.

Your code should look like this:

// Setting your Chrome options (Desired capabilities)
ChromeOptions options = new ChromeOptions();
options.add_argument('--start-maximized');
options.add_argument('--start-fullscreen');

// Creating a driver instance with the previous capabilities
WebDriver driver = new ChromeDriver(options);

// Load page & take screenshot of full-screen page
driver.get("http://google.com");
File scrFile = ((TakesScreenshot)driver).getScreenshotAs(OutputType.FILE);

Now regarding the full page problem, all drivers (chromedriver, geckodriver, IEDriver, EdgeDriver, etc.) are implementing the WebDriver W3C standard. Thus, they are dependent on the way the WebDriver team wants to expose the functionality of different features, in our case, 'Take Screenshot'.

If you read the definition, it clearly states the following:

The Take Screenshot command takes a screenshot of the top-level browsing context’s VIEWPORT.

Legacy-wise, some drivers were able to produce a full-page screenshot (read more about it here), like the old FirefoxDriver, IEDriver, etc. That is no longer the case as they now all implement (to the letter) the WebDriver W3C standard.

As a rule of thumb, try to select more elements by one query, if possible. Searching for many elements one-by-one will get seriously slow.

If I understand your needs well, a good way to do this would be using

driver.findElement(By.id("someId::button")).click();
driver.findElement(By.xpath("//*[contains(@id, 'someId--popup::popupItem') " +
    "and text()='" + myDesiredValue + "']"))
    .click();

For more information about XPath, see the spec. It's surprisingly a very good read if you can skip the crap!

That finds and clicks an element with text equal to you desired value which contains "someId--popup::popupItem" in its ID.

List<WebElement> list = driver.findElements(By.xpath("//*[contains(@id, 'someId--popup::popupItem')]"));

That finds all just all elements that contain "someId--popup::popupItem" in their ID. You can then traverse the list and look for your desired element.

Did you know you can call findElement() on a WebElement to search just it's children? - driver.findElement(By.id("someId")).findElements(By.className("clickable"))

Without a peek on the underlying HTML, I guess I can't offer the best approach, but I have some in my head.

You can send an Enter key to an element. However, you can't press Enter to, say, confirm a download dialog.

WebElement elem = driver.findElement(By.id("damnit")); // obtain an element
elem.sendKeys(org.openqa.selenium.Keys.ENTER); // this sends an Enter key to the element
elem.sendKeys("hey" + org.openqa.selenium.Keys.ENTER); // this writes and then confirms by Enter

You can simulate hit Enter key by adding "\n" to the entered text. For example textField.sendKeys("text you type into field" + "\n").

upd: BTW, it has been already asked here Typing Enter/Return key in Selenium

Assuming that you use Java 8, you could do that using the Stream API with joining(CharSequence delimiter) as collector allowing to concatenate the input elements, separated by the specified delimiter, in encounter order as next:

String emails = emailAddresses.stream().collect(Collectors.joining(";"));

The problem is with how your initialising the webdriver instance. The below code snippet

@BeforeTest
@Parameters({"browser", "baseURL"})
public void setUp(@Optional String browser, @Optional String baseURL) {
    driver = getBrowserType(browser);
    driver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);
    driver.manage().window().maximize();
    driver.navigate().to(baseURL);
}

causes the setUp method to be invoked only once per <test> tag because its part of a common base class to both your test classes.

So if there are two test classes in your <test> tag such as

<test name="chromeTest" >
    <parameter name="browser" value="chrome"></parameter>
    <classes>
        <class name="tests.HomePageTest"></class>
        <class name="tests.NavigationMenuTest"></class>
    </classes>
</test>

then the setUp method would get invoked only for HomePageTest and be skipped when executing NavigationMenuTest

That explains why you see a NullPointerException for your second test class within the <test> tag. You would need to change this by perhaps annotating the setUp method with @BeforeClass instead of @BeforeTest