Using the solution provided by yeshwanth.intelli may have an impact on overall testing performance since the implicit wait will be used in all FindElement calls. Many times you'll want the FindElement to fail right away when an element is not present (you're testing for a malformed page, missing elements, etc.). With the implicit wait, these operations would wait for the whole timeout to expire before throwing the exception. The default implicit wait is set to 0 seconds.
I've written a little extension method to IWebDriver that adds a timeout (in seconds) parameter to the FindElement() method. It's quite self-explanatory:
public static class WebDriverExtensions
public static IWebElement FindElement(this IWebDriver driver, By by, int timeoutInSeconds)
if (timeoutInSeconds > 0)
var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(timeoutInSeconds));
return wait.Until(drv => drv.FindElement(by));
I didn't cache the WebDriverWait object as its creation is very cheap, this extension may be used simultaneously for different WebDriver objects, and I only do optimizations when ultimately needed.
Usage is straight-forward:
var driver = new FirefoxDriver();
var btn = driver.FindElement(By.CssSelector("#login_button"));
var employeeLabel = driver.FindElement(By.CssSelector("#VCC_VSL"), 10);