Q. What is Selenium?
A. Selenium is a suite of tools for browser automation (i.e. automated Web testing). It is composed of
Selenium IDE: A tool for recording and playing back. This is a Fire-fox plugin.
WebDriver and RC provide the APIs for a variety of languages like Java, .NET, PHP, etc. A Java example is shown below. The WebDriver and RC work with most browsers.
Grid transparently distribute your tests on multiple machines so that you can run your tests in parallel, cutting down the time required for running in-browser test suites.
Q. How would you go about using selenium for your web testing?
A. The example below shows the steps involved in testing a simple login page with selenium + Web Driver. The pages have HTML snippets as shown below
Login Page:
1
2
3
4
5
6
7
8
9
10
11
12
13
| ...<form method="POST" action="some/url"> <input type="text" name="username"/> <input type="text" name="password" /> </form>... |
Login response page:
1
2
3
4
5
6
7
| ...<table> <tr> <td>John</td>< /tr></table>... |
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
| <properties> <junit.version>4.4</junit.version> <selenium.version>2.7.0</selenium.version> <slf4j.version>1.5.2</slf4j.version></properties><dependencies> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>${selenium.version}</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>${junit.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>${slf4j.version}</version> </dependency></dependencies> |
The selenium-java-x.x.x.jar will transitively bring in the other relevant driver jars for different browsers.
STEP 2: It is a best practice to have separate page objects as these page objects can be shared by multiple JUnit test cases. If a particular page element changes, you will have to change it only in one place, which is page object, and not in all JUnit test cases where a paricular element is used. The JUnit test cases will depend on the page objects and should not refer to the page elements directly.
1
2
3
4
5
6
7
8
9
10
11
12
| package fsg.wrap.systemtest;import org.openqa.selenium.WebDriver;public class SystemTestPage { protected WebDriver driver; protected SystemTestPage(WebDriver driver) { this.driver = driver; }} |
You can have your page objects extend the above generic SystemTestPage class.
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
| package com.systemtest.page;import org.openqa.selenium.By;import org.openqa.selenium.WebDriver;import org.openqa.selenium.WebElement;import org.openqa.selenium.support.CacheLookup;import org.openqa.selenium.support.FindBy;import fsg.wrap.systemtest.SystemTestPage;public class LoginPage extends SystemTestPage { @FindBy(name = "username") @CacheLookup private WebElement userNameInput; @FindBy(name = "password") @CacheLookup private WebElement passwordInput; @FindBy(xpath ="//input[@type=\"submit\"]") @CacheLookup private WebElement submitButton; public LoginPage(WebDriver driver){ super(driver); } public void login(String userName, String password) { userNameInput.sendKeys(userName); userNameInput.sendKeys(password); submitButton.submit(); } public String getUserName(String userName) { WebElement element = driver.findElement(By.xpath("//td[text()=" + userName + "]")); return element.getText(); }} |
STEP 3: Write the JUnit class using the page objects defined above and assert the results. These JUnit test cases can be run to test your web pages.
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
| package com.unittests;import junit.framework.Assert;import org.junit.After;import org.junit.Before;import org.junit.Test;import org.openqa.selenium.WebDriver;import org.openqa.selenium.firefox.FirefoxDriver;import org.openqa.selenium.support.PageFactory;import org.openqa.selenium.support.ui.WebDriverWait;import com.systemtest.page.LoginPage;public class LoginTest { private static final String USER_NAME = "John"; private static final String PASSWORD = "aa44" private WebDriver driver; private WebDriverWait wait; private LoginPage loginPage; // the page object @Before public void setUp() { driver = new FirefoxDriver(); wait = new WebDriverWait(driver, 5); driver.get(BASE_URL); loginPage = PageFactory.initElements(driver, LoginPage.class); } @Test public void testLogin() throws Exception { loginPage.login(USER_NAME, PASSWORD); Assert.assertEquals(MAC, loginPage.getUserName(USER_NAME)); } @After public void tearDown() { driver.quit(); }} |
Q. What are selenium locators? What tools do you use to locate them?
A. Selenium Locators are the way of finding the HTML element on the page to perform a Selenium action on. The example above has a line asshown below to extract the username element from the Login response page. This uses an XPath expression to locate the element.
1
2
3
4
| public String getUserName(String userName) { WebElement element = driver.findElement(By.xpath("//td[text()=" + userName + "]")); return element.getText();} |
The XPath expression will be something like //td[[text()=John] which looks for a td element with text value "John".
The annotation in the above example is also a locator by name as shown below
1
2
3
| @FindBy(name = "username")@CacheLookupprivate WebElement userNameInput; |
This will match the HTML snippet
1
| <input type="text" name="username"> |
You could also find by tagName, id, css, etc.
There are handy tools to identify the HTML elements or locators.
Selenium IDE, which is a Firefox plugin useful in identifying the locators, debugging, etc.
The Fire-bug plugin, which allows you to inspect the elements by right clicking on the page and then selecting "Inspect Element". Google chrome provides a similar functionality to inspect element out of the box.
Q. In your experience, what are some of the challenges with Selenium?
A. In general, badly written test cases whether junit tests or web tests, the biggest complaint is about writing test cases that are not maintainable. Unmaintainable automated test cases can take more time than manual tests. So, it is important to write quality test cases by clearly separting the page objects from the test cases as demonstrated in the Q&A above. The use of the locators need to be carefully thought through. For example, some frameworks like JSF dynamically generate HTML element IDs. So, if IDs are used in your tests, then the test cases may fail if the IDs have changed. The solution to this problem is to use XPath to find the relevant HTML elements. The ClickAndWait action will not work for AJAX calls, and use "waitForElement" instead.
