ImplicitlyWait Command

Purpose: Selenium WebDriver has borrowed the idea of implicit waits from Watir. This means that we can tell Selenium that we would like it to wait for a certain amount of time before throwing an exception that it cannot find the element on the page. We should note that implicit waits will be in place for the entire time the browser is open. This means that any search for elements on the page could take the time the implicit wait is set for.

FluentWait Command

Purpose: Each FluentWait instance defines the maximum amount of time to wait for a condition, as well as the frequency with which to check the condition. Furthermore, the user may configure the wait to ignore specific types of exceptions whilst waiting, such as NoSuchElementExceptions when searching for an element on the page.

Java

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

// Waiting 30 seconds for an element to be present on the page, checking

// for its presence once every 5 seconds.

Wait wait=newFluentWait(driver)

.withTimeout(30,SECONDS)

.pollingEvery(5,SECONDS)

.ignoring(NoSuchElementException.class);

WebElement foo=wait.until(newFunction(){

publicWebElement apply(WebDriver driver){

returndriver.findElement(By.id("foo"));

}

});

ExpectedConditions Command

Purpose: Models a condition that might reasonably be expected to eventually evaluate to something that is neither null nor false.

PageLoadTimeout Command

Purpose: Sets the amount of time to wait for a page load to complete before throwing an error. If the timeout is negative, page loads can be indefinite.

Java

1

driver.manage().timeouts().pageLoadTimeout(100,SECONDS);

SetScriptTimeout Command

Purpose: Sets the amount of time to wait for an asynchronous script to finish execution before throwing an error. If the timeout is negative, then the script will be allowed to run indefinitely.

Java

1

driver.manage().timeouts().setScriptTimeout(100,SECONDS);

Sleep Command

Purpose: This is rarely used, as it always force the browser to wait for a specific time. Thread.Sleep is never a good idea and that’s why Selenium provides wait primitives. If you use them you can specify much higher timeout value which makes tests more reliable without slowing them down as the condition can be evaluated as often as it’s required.

Java

1

thread.sleep(1000);

Practice Exercise

1) Launch new Browser

2) Open URL “http://toolsqa.com/automation-practice-switch-windows/”

3) Click on the Button “Timing Alert”

4) Accept the Alert (Alert will take 3 second to get displayed, Use WebDriverWait to wait for it)

Solution

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

packagepracticeTestCases;

import java.util.concurrent.TimeUnit;

import org.openqa.selenium.Alert;

import org.openqa.selenium.By;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.firefox.FirefoxDriver;

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

import org.openqa.selenium.support.ui.WebDriverWait;

publicclassPracticeWaitCommands{

publicstaticWebDriver driver;

publicstaticvoidmain(String[]args){

// Create a new instance of the Firefox driver

driver=newFirefoxDriver();

// Put an Implicit wait, this means that any search for elements on the page could take the time the implicit wait is set for before throwing exception

driver.manage().timeouts().implicitlyWait(10,TimeUnit.SECONDS);

// Launch the URL

driver.get("http://toolsqa.com/automation-practice-switch-windows/");

// Click on the Button "Timing Alert"

driver.findElement(By.name("Timing Alert")).click();

System.out.println("Timer JavaScript Alert is triggered but it is not yet opened");