Tomas Varsavsky

Jul 27

Selenium page models

Brittle Selenium test suites are a common problem for projects with a significant number of acceptance tests. In the past, Selenese made it really hard to write well factored Selenium tests. The best one could do was write Selenium tests in JSPs and use JSP includes to avoid repetition of command chains (e.g. include Login.jsp).

Selenium RC gives us the ability to leverage the richness of the language to write well factored tests. One pattern that can help here is Page Models. These are essentially an abstraction of the pages in the application using classes. Taking Google as a sample application, we could write simple page models for the home and search results pages.

public class GoogleHomePage {

private final Selenium selenium;

public static GoogleHomePage open(Selenium selenium) {
		selenium.open("/");
		return new GoogleHomePage(selenium);
	}

public GoogleHomePage(Selenium selenium) {
		this.selenium = selenium;
		assertEquals("Google", selenium.getTitle());
	}

public void setSearchTerm(String searchTerm) {
		selenium.type("q", searchTerm);
	}

public String getSearchTerm() {
		return selenium.getValue("name=q");
	}

public GoogleSearchResultsPage performSearch() {
		selenium.click("btnG");
		selenium.waitForPageToLoad("5000");
		return new GoogleSearchResultsPage(selenium);
	}
}

public class GoogleSearchResultsPage {

private final Selenium selenium;

public GoogleSearchResultsPage(Selenium selenium) {
		this.selenium = selenium;
		assertTrue(selenium.getTitle().contains("Google Search"));
	}

public String getSearchResultNumber(int i) {
		return selenium.getText("//div[@id='res']/div/div[" + i + "]");
	}

public String getSearchTerm() {
		return selenium.getValue("name=q");
	}

public GoogleHomePage gotoHomePage() {
		selenium.click("logo");
		selenium.waitForPageToLoad("5000");
		return new GoogleHomePage(selenium);
	}
}

The page models provide access to page elements and are linked through navigation actions. We can use the page models to write tests that are more intentional and don’t interact with Selenium directly.

public class GoogleSearchTest {

private Selenium selenium;

private GoogleHomePage homePage;

@Before
	public void setUp() {
		selenium = new DefaultSelenium("localhost", 4444, "*iexplore", "http://www.google.com.au");
		selenium.start();
		homePage = GoogleHomePage.open(selenium);
	}

@After
	public void tearDown() {
		selenium.stop();
	}

@Test
	public void testSearchTermInSearchResultsPageShouldBeMaintainedAfterSearch() {
		homePage.setSearchTerm("this is a search term");
		GoogleSearchResultsPage resultsPage = homePage.performSearch();
		assertEquals("this is a search term", resultsPage.getSearchTerm());
	}

@Test
	public void testSearchTermInHomePageShoulBeClearedAfterNavigationFromSearchResultsPage() {
		homePage.setSearchTerm("this is a search term");
		GoogleSearchResultsPage resultsPage = homePage.performSearch();
		homePage = resultsPage.gotoHomePage();
		assertEquals("", homePage.getSearchTerm());
	}

@Test
	public void testSearchResultsShouldContainMyBlogAsFirstResult() {
		homePage.setSearchTerm("tomas varsavsky blog");
		GoogleSearchResultsPage resultsPage = homePage.performSearch();
		assertTrue(resultsPage.getSearchResultNumber(1).contains("tomasvarsavsky.com"));
	}
}

For more than one test class we would probably go a bit further and move the setUp and tearDown methods to a common parent or utility class. We could even make the page models reference the Selenium object directly rather than passing it around all the time.

With this approach the application and page models can be changed freely without having an impact on individual tests.

Selenium page models

Leave a Reply

Links

Categories

Archives

Worth A Look

Recent Posts

Recent Comments

About