How to use ConfigException class of org.openqa.selenium.grid.config package

Is this a timing issue? Is the element (or the whole page) AJAX-loaded? It's possible that it's not present on the page when you're trying to look for it, WebDriver is often "too fast".

To solve it, is either implicit or explicit wait.

The Implicit Wait way. Because of the implicit wait set, this will try to wait for the element to appear on the page if it is not present right away (which is the case of asynchronous requests) until it times out and throws as usual:

// Sooner, usually right after your driver instance is created.
driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

// Your method, unchanged.
@Test
public void Appointments() {
    ...
    driver.findElement(By.id("ctl00_Header1_liAppointmentDiary")).doSomethingWithIt();
    ...
}

The Explicit Wait way. This will only wait for this one element to be present on the page when looking for it. Using the ExpectedConditions class, you can wait for different things, too - the element to be visible, clickable etc.:

import static org.openqa.selenium.support.ui.ExpectedConditions.*;

@Test
public void Appointments() {
    ...
    WebDriverWait wait = new WebDriverWait(driver, 10);
    wait.until(presenceOfElementLocated(By.id("ctl00_Header1_liAppointmentDiary")))
        .doSomethingwithIt();
    ...
}

It doesn't look like you're actually using the regex. It seems like maybe this is what you're trying to do?

Assert.assertTrue(driver.getTitle().matches("*TST-*[0-9]{5}"));

EDIT #1:

It also seems like your regex might not be quite right, try:

Assert.assertTrue(driver.getTitle().matches(".*TST-\\d{5}.*"));

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.

I need to click the link who's href has substring "long" in it. How can I do this?

With the beauty of CSS selectors.

your statement would be...

driver.findElement(By.cssSelector("a[href*='long']")).click();

This means, in english,

Find me any 'a' elements, that have the href attribute, and that attribute contains 'long'

You can find a useful article about formulating your own selectors for automation effectively, as well as a list of all the other equality operators. contains, starts with, etc... You can find that at: http://ddavison.io/css/2014/02/18/effective-css-selectors.html

java.lang.UnsupportedClassVersionError happens because the code was compiled with a higher version of Java than the one you're running it.

Version 51.0 of a class file corresponds to java 7

J2SE 8 = 52,
J2SE 7 = 51,
J2SE 6.0 = 50,
J2SE 5.0 = 49,
JDK 1.4 = 48,
JDK 1.3 = 47,
JDK 1.2 = 46,
JDK 1.1 = 45

You need to upgrade your JDK from Java 6 to Java 7 or higher.

I figured out the answer.

• Start Sauce Connect, and pass proxy server information

  java -jar Sauce-Connect.jar myname xxxxxx -p localhost:9091
  

  Running the above command will pass all requests to localhost 9091 port, and you may use netcat to confirm.

  nc -l 9091
  

• Run Java Client

  ProxyServer proxyServer = new ProxyServer(9091);
  proxyServer.start();    
  
  Proxy proxy = proxyServer.seleniumProxy();
  DesiredCapabilities capabilities = DesiredCapabilities.firefox();
  // DO NOT set proxy for RemoteWebDriver
  // capabilities.setCapability(CapabilityType.PROXY, proxy);
  capabilities.setCapability("version", "5");
  capabilities.setCapability("platform", Platform.XP);
  this.driver = new RemoteWebDriver(
          new URL("http://myname:xxxxxx@ondemand.saucelabs.com:80/wd/hub"),
          capabillities);
  

  The Java Client should starts a proxy at Port 9091. Unlike using FirefoxDriver directly, proxy should not be set in capabilities.

What you're describing is called a Sandbox DB. For every new deploy you'll have to provide/populate this DB with the data you need and after tests are done, to drop it.

have several versions/snapshots of DB state

This is what a Fresh Fixture pattern and Prebuilt Fixture pattern will help you with. Also you could look at the Fixture Teardown patterns.

Here you can find some considerations when dealing with such big-data-sandbox-strategies. Like scheduling, master data repository and monitoring.

To successfully manage all that - a CI server have to be put to work. Since you've tagged JAVA, a good options are:

• Jenkins and Database plugin
• Bamboo
• Hudson

Okay, the script obviously kicks in when the clear() method clears the input and leaves it empty. The solutions it came up with are given below.

1. The naïve one, presses Backspace 10 times:

   String b = Keys.BACK_SPACE.toString();
   searchField.sendKeys(b+b+b+b+b+b+b+b+b+b + username);
   

   (StringUtils.repeat() from Apache Commons Lang or Google Guava's Strings.repeat() may come in handy)

2. The nicer one using Ctrl+A, Delete:

   String del = Keys.chord(Keys.CONTROL, "a") + Keys.DELETE; 
   searchField.sendKeys(del + username);
   

3. Deleting the content of the input via JavaScript:

   JavascriptExecutor js = (JavascriptExecutor)driver;
   js.executeScript("arguments[0].value = '';", searchField);
   searchField.sendKeys(username);
   

4. Setting the value of the input via JavaScript altogether:

   JavascriptExecutor js = (JavascriptExecutor)driver;
   js.executeScript("arguments[0].value = '" + username + "';", searchField);
   

Note that javascript might not always work, as shown here: Why can't I clear an input field with javascript?

isElementPresent() - This method basically tests if the element we are looking for is present somewhere on the page.

isVisible() - looks for display: none style tag - this might throw a null pointer if we aren't careful...thus to see if an element is visible first check if the element is present using isElementPresent() method. Then try checking if the element is visible!

Observe that isElementPresent() won't mind even if our element is not visible.

For ex: lets say the below is the html code for a component on my test application:

now if you test the above component with

selenium.isElementPresent("testinput") - returns true!
selenium.isVisible("testinput") - returns false!