How to use Enum PrintOptions.Orientation class of org.openqa.selenium.print package

I have had similar problems with calling sendKeys(). The problem usually is, that the signature is a var-ary, that is CharSequence... instead of just CharSequence.

Of course this should not be a problem with Java 6. My guess would be that your maven compile uses a different compiler setting. Anyways you could change your code to

searchField.sendKeys(new String[] { "sample" });

to help diagnose the problem.

The problem is in the XPATH of the Product locators.

Below xpath expression in selenium means you are looking for a matching element which CAN BE ANYWHERE in document. Not relative to the parent as you are thinking!!

//div[@class='url']/a

This is why it always returns the same first element.

So, in order to make it relative to the parent element it should be as given below. (just a . before //)

public final static String URL_PATTERN = ".//div[@class='url']/a";
public final static String TITLE_PATTERN = ".//div[@class='title']";

Now you make it search for matching child element relative to the parent.

XPATH in selenium works as given below.

/a/b/c   --> Absolute - from the root

//a/b    --> Matching element which can be anywhere in the document (even outside the parent).

.//a/b   --> Matching element inside the given parent

In Webdriver, you should use driver.switchTo().defaultContent(); to get out of a frame. You need to get out of all the frames first, then switch into outer frame again.

// between step 4 and step 5
// remove selenium.selectFrame("relative=up");
driver.switchTo().defaultContent(); // you are now outside both frames
driver.switchTo().frame("cq-cf-frame");
// now continue step 6
driver.findElement(By.xpath("//button[text()='OK']")).click(); 

Webdriver has findElements API, which can be used for this purpose..

List<WebElement> allElements = driver.findElements(By.xpath("//div[@id='...']/ul/li")); 

for (WebElement element: allElements) {
      System.out.println(element.getText());
}

Yes, this is a known problem and as of Selenium 2.21.0, there is a way to go around.

The problem is that implicit wait is designed to wait for unloaded elements when you search for some, but the click() method just waits until the browser states that the page is fully loaded.

Try driver.manage().timeouts().pageLoadTimeout() which is a new method in 2.21.0 and should deal exactly with this.

I know this is rather old, but you can get a simpler solution by using org.openqa.selenium.support.Color:

import org.openqa.selenium.support.Color;
String color = driver.findElement(By.xpath("//div[@class='gb_e gb_f gb_g gb_xb']/a")).getCssValue("color");
System.out.println(color);
String hex = Color.fromString(color).asHex();
System.out.println(hex);

It gives you a single line solution and even adds leading zeroes when required (something that the previous answers aren't accounting for)

The submit() function is there to make life easier. You can use it on any element inside of form tags to submit that form.

You can also search for the submit button and use click().

So the only difference is click() has to be done on the submit button and submit() can be done on any form element.

It's up to you.

http://docs.seleniumhq.org/docs/03_webdriver.jsp#user-input-filling-in-forms

How are you defining your threads in your xml file? Found some stuff using the parallel variable to kill all specific threads immediately. Maybe if you name your threads with something common and increment a counter to put a "_1" ... "_2" and so on at the end of the common name, you could loop through quickly and kill the thread directly? You mentioned a queue of tests that you weren't positive on how it worked, maybe take the queue into your own hands manually and kill them all.

After some hours I finally found a solution by using Actions without JavascriptExecuter:

Actions actions = new Actions(driver);
actions.moveToElement(website);
actions.click();
actions.sendKeys("Some Name");
actions.build().perform();

Well, it worked for me. However, is this way the better solution ?