Explicit Wait, Implicit Wait, Fluent Wait in Selenium using C#

-
What are Wait commands?

Waits are the command in Selenium which is very useful for the execution of the automated test scripts. During execution of automated test script, there might be some situation where issues may occur due to variations in time lag for loading web elements. In these situation Wait commands helps in troubleshooting these issues.

Wait commands helps in directing a test script to pause for a certain time before throwing exception.

Types of  Wait Commands

Selenium WebDriver provides three types of wait commands to implement in tests.

1. Implicit Wait
2. Explicit Wait
3. Fluent Wait

Implicit Wait

Implicit wait directs the Selenium WebDriver to wait for a certain measure of time before throwing an exception. Once this time is set, WebDriver will wait for the webelement before throwing exception.

So by implicitly wait, the WebDriver will wait for certain duration to find any webelement. This can helpful when certain elements on the webpage are not available immediately and need some time to load. The default setting is 0, meaning disabled. Once set, the implicit wait is set for the life of the session.

Example Using C#

IWebDriver driver = new ChromeDriver();
driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(10);
driver.Url = "http://somedomain/url_that delays_loading";
IWebElement dynamicElement = driver.FindElement(By.Name("dynamicElement"));

Explicit Wait

Explicit wait command helps in redirecting the WebDriver to wait until a certain condition occurs before proceeding with executing the code.

Explicit wait is important in the cases where there certain elements that naturally take more time to load. Implicit wait causes unnecessary delay in executing the test script which will wait for the same time frame before loading every web element. Explicit wait is an improvement on implicit wait since it allows the program not to wait the entire provided timespan, if the webelement is available before the timespan it will proceed to the next line of code, thus saving time and executing the script faster.    

Using C#

WebDriverWait wait = new WebDriverWait(driver,30)
wait.until(ExpectedCondition.visibilityOf ElementLocated(By.Xpath("reference of webelement")));

Fluent Wait

Fluent wait command defines the maximum amount of time for Selenium WebDriver to wait for a certain condition to appear.

To be more precise, Fluent wait looks for a web element repeatedly at regular intervals until timeout happens or until the object is found.
















Comments

Post a Comment

Popular posts from this blog

Assertion

-
PURPOSE OF ASSERT IN A TEST AUTOMATION SUITE  Assert plays vital role in automation testing. Without assertion we cannot provide the status of the test cases passed, failed etc. Assertion is used to validate the status of a test case. Let's take an example of a login page where a user logged in through valid username , valid password and clicking the login button. With valid credential it should login to the home page successfully. Now that a user has been logged in successfully there should be some sort of commands which helps to validate the user has successfully logged in. Hence assertion comes into picture, where we can use assertion command to validate whether the user has been successfully logged in by comparing any text in the homepage with the text provided in the command. eg. Assert.assertEquals(expected, actual) Here if the actual and expected matches , then the test case will be marked as a passed.
Read more

CI/CD Pipelines & DevOps

-
Image
CI/CD Pipelines & DevOps A CI/CD Pipeline implementation, or Continuous Integration/Continuous Deployment, is the backbone of the modern DevOps environment. It bridges the gap between development and operations teams by automating the building, testing, and deployment of applications. CI/CD is o ne of the best practices for DevOps teams to implement . It is also an  agile methodology  best practice, as it enables software development teams to focus on meeting business requirements, code quality, and security because deployment steps are automated. Before moving onto the CI/CD pipeline, let's start by understanding DevOps. DevOps is a software development approach which involves continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring of the software throughout its development lifecycle. Let us now look at the DevOps lifecycle and explore how it is related to the software development stages.
Read more