How to use getUseTechnologyPreview method of org.openqa.selenium.safari.SafariOptions class

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.

You can select text nodes using the axis step text().

//div[@class='A']/text()

If you only want text nodes following the <input/> node, use this:

//div[@class="A"]/input/following-sibling::text()

You can add arbitrary predicates to the <input/> element, too - like you did for the <div/>.

DatePicker are not Select element. What your doing in your code is wrong.

Datepicker are in fact table with set of rows and columns.To select a date you just have to navigate to the cell where our desired date is present.

So your code should be like this:

WebElement dateWidget = driver.findElement(your locator);
List<WebElement> columns=dateWidget.findElements(By.tagName("td"));

for (WebElement cell: columns){
   //Select 13th Date 
   if (cell.getText().equals("13")){
      cell.findElement(By.linkText("13")).click();
      break;
 }

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

I ran into a similar issue. The click method worked on other pages, then didn't work at all on a particular page.

A race condition caused the issue:

1. HTML content is rendered with the button disabled.
2. The selenium web driver script was executed before the javascript onload event was triggered (Or finished executing). So the button.click would occur on a disabled element. And nothing would happen.
3. Then the javascript onload event would trigger (or finish executing) and the javascript would enable the button.
4. I looked at the page and couldn't figure out why my code wasn't working because the button appeared to be enabled upon inspection, and if I manually clicked the button, it worked.

Once I figured out that it was a timing issue, I found the solution here: How can I get Selenium Web Driver to wait for an element to be accessible, not just present?

To paraphrase the solution in Ruby:

//This will not return the button until it is enabled.
button = driver.find_element(:xpath,  "//button[@id='myButtonId' and not(@disabled)]")
button.click

The type command may not be enough to trigger the autocomplete. Dave Webb's suggestions are otherwise spot on. My only addition would be that you might need the typeKeys command, which causes slightly different JavaScript events to be fired, which may be more likely to trigger the autocomplete widget.

You can follow the Appium news section to get updates about the concerned dependency for selenium - java.

Example: To know about the Java - Client 5.0.2 release and to know about it's dependency visit the below link

Java-client-5-0-2

You will find the update like this

Cucumber scenarios are tools we use to describe behaviour i.e. what is happening and why its important. They are not tools to program tests. The way to use Cucumber effectively is to keep your scenarios simple, and let code called by step definitions do your programming for you.

Step definitions and the methods they call are written in a programming language. This gives you all the power you need to deal with the details of how you interact with your system.

The art of writing Cucumber scenarios is for each one to talk about

1. The state we need setup so we can do something (Givens)
2. Our interaction (When)
3. What we expect to see after our interaction. (Then)

So for your scenario we have

Scenario: Login
  Given I am registered
  When I login
  Then I should be logged in

When we make this scenario work our program has the behaviour that we can login. So then we can use that behaviour in other scenarios e.g.

Scenario: See my profile
  Given I am logged in
  When I view my profile
  Then I should see my profile

Now to make this work we might need a bit more work because this scenario doesn't have a registered user yet. We can deal with this in a number of ways

1) Add another Given, perhaps in a background

Background:
    Given I am registered

  Scenario ...
    Given I am logged in

2) We can register in the login step e.g.

   Given "I am logged in" do
      @i = register_user
      login_as user: @i
    end 

Notice how in this step we are calling helper methods register_user and login_as to do the work for us.

This is the way to start using Cucumber. Notice how my scenarios have no mention of how we login, no email, no password, no filling in anything. To use Cucumber effectively you have to push these details down into the step definitions and the helper methods they call.

Summary

Keep you scenarios simple and use them to describe WHAT and explain WHY. Use the step definitions and helper methods to deal with HOW. There is no need to use Scenario Outlines when using Cucumber and you should never be nesting them.

Chances are this problem is caused by an already-running instance of the Selenium server. The new instance needs to listen on the same port number, but can't, because the port is already in use.

Let's say your Selenium server is configured to start on port 4444. Determine if the port is in use using the 'netstat' command:

On Windows: netstat -an | find "4444"

Expect to see output like this:

  TCP    0.0.0.0:4444           0.0.0.0:0              LISTENING
  TCP    [::]:4444              [::]:0                 LISTENING

On Linux, use: netstat -anp | grep 4444

(No Linux box to hand, so can't show example output!)

If you see any output, you need to kill the process that's listening on the port that Selenium wants to use. On Windows, use netstat -anb to find the process name (it'll be listed after the line specifying the port number). Kill it using the Task Manager. On Linux, the process PID and name will be listed by the command above - kill it using kill <PID>.