Skip to main content

  • Increase Speed to Market
    Deliver quality quicker by optimising your delivery pipeline, removing bottlenecks, getting faster feedback from customers and iterating quickly.

  • Enhance Customer Experience
    Delight your customers in every digital interaction by optimising system quality and performance to provide a smooth, speedy and seamless user experience.

  • Maximise Your Investment
    Realise a positive ROI sooner and maximise your investment by focusing your energy on high-value features, reducing waste, and finding and fixing defects early.
  • The Wellington City Council (WCC) wanted to deliver quality outcomes without breaking the bank. Find out how Planit’s fast and flexible resources helped WCC achieve this goal.

this is a test Who We Are Landing Page

Synchronisation in Selenium Synchronisation in Selenium
INSIGHTS / Articles

Synchronisation in Selenium

 7 Sep 2022 
Synchronisation in Selenium
INSIGHTS / Articles

Synchronisation in Selenium

 7 Sep 2022 

    When two or more components work together to perform any action at the same pace, the process is called synchronisation. In Selenium, there should be synchronisation between the Selenium script, web app, and the script execution speed.

    You might have noticed that sometimes pages load successfully without any time delay, while in other cases it takes a few seconds to load. I.e., the web elements on a webpage are taking time to load.

    How do you resolve such an issue? This is where “Waits” enter the picture from the perspective of the Selenium automated testing suite.

    Selenium provides synchronisation in the form of Implicit Wait and Explicit Wait. These synchronisation points are inserted in the script using WebDriverWait class.

    Implicit Wait

    Implicit Wait is a global wait. Implicit Wait time is applied to all the web elements in a test script with which the driver is interacting.

    Implicit Wait is given immediately after driver is initialised. It tells driver to poll the DOM for a certain amount of time when trying to find an element if the element is not immediately available.

    The syntax for implicit wait is simply and just one line:


    In this example, ten seconds is the maximum time the driver will wait for an element to be found. If an element is not located on the web page within that time frame, it will throw an exception.


    The subsequent step in your script will only execute when ten seconds have elapsed.

    Implicit wait is useful when certain elements on the webpage are not immediately available and need some time to load. The default setting for implicit wait is zero meaning disabled. Once set, it will be globally applicable to the script.

    Code snippet:

    public static void main(String[] args) {
    // TODO Auto-generated method stub

    System.setProperty("","E://Selenium Tutorial//chromedriver.exe")
    WebDriver driver = new ChromeDriver();


    Explicit Wait

    Explicit Wait is applied to a specific element on a web page. It allows your code to halt program execution until the condition is resolved or the expected condition is met.

    Once you declare an Explicit Wait, “ExpectedConditions” needs to be used on the element to be located. When elements take a long time to load and you want to verify the property of the element, there is (VisitbilityOfElementLocated,elementToBeClickable,elementToBeSelected)

    Syntax for Explicit Wait:

    New WebDriverWait(driver,timeout).until(ExpectedConditions.elementToBeClickable(element));

    Code snippet:

    // By default it will accepts in Seconds
    WebDriverWait wait = new WebDriverWait(driver, 20);
    // Here we will wait until element is not visible, if element is visible then it will return web element
    // or else it will throw exception
    WebElement element = wait

    Note that Thread.sleep() always pauses the current thread execution. It interacts with the thread scheduler to put the current thread in Wait state for a specified period of time.

    Once the wait time is over, the thread state is changed to runnable state and waits for the CPU for further execution. Thread.sleep() is a static wait and it is not recommended for use it in our automation script.

    This is just an introduction to the differences between these Waits. When you feel confident in using these, there are newer and smarter Fluent Waits commands that you can go on to use.

Mukta Sharma


Get the Most Out of Your Tools

No matter where you are on your journey, Planit can help you make the appropriate choices to ultimately deliver your applications faster, with better quality, and at lower cost. With expertise across the spectrum of tools, our consultants can be leveraged from ideation to operations and everywhere in between.
Find out how our certified experts across the spectrum of testing toolsets can help you find the right tools for your needs, get the most out of your tools, and achieve a CI/CD toolchain.


Find out more

Get updates

Get the latest articles, reports, and job alerts.