I just released the Master Class of "Learn Spring Security":
1. Introduction
This article is a quick, practical introduction to working with Selenium and writing tests with JUnit and TestNG.
2. Selenium Integration
In this section, we’ll start with a simple scenario – opening a browser window, navigating to a given URL and looking for some desired content on the page.
2.1. Maven Dependencies
In the pom.xml file, add the following dependency:
<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>3.0.1</version> </dependency>
The latest version can be found in the Maven Central Repository.
2.2. Selenium Example
First, create a new Java class file called SeleniumExample:
public class SeleniumExample { private WebDriver webDriver; private String url = "http://www.baeldung.com/"; // ... }
Given we’re using a Selenium 3.x version, we have to specify the path of an executable GeckoDriver file (based on your OS) using a system property called webdriver.firefox.marionette. The latest version of the GeckoDriver may be downloaded from Github Geckodriver Releases.
Let’s now initialize the WebDriver in the constructor and set the desired URL to navigate to. We’ll also maximize the browser window and set 10 seconds as time-out for WebDriver to wait for an element on the page to appear:
public SeleniumExample() { // for windows based environment, path for geckodriver may be given as System.setProperty ("webdriver.firefox.marionette", "C:\\selenium\\geckodriver.exe"); // for Unix based environment, path for geckodriver may be given as // System.setProperty("webdriver.firefox.marionette", "~/geckodriver"); webDriver = new FirefoxDriver(); webDriver.manage().window().maximize(); webDriver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); webDriver.get(url); }
Similarly, we’ll implement a simple API to close the browser and get the title of the page:
public void closeWindow() { webDriver.close(); } public String getTitle() { return webDriver.getTitle(); }
In order to navigate to the About section of baeldung.com, we need to create a closeOverlay() method that checks and closes the overlay on a homepage load. Thereafter, we navigate to the About Baeldung page using the getAboutBaeldungPage() method:
public void getAboutBaeldungPage() { closeOverlay(); clickAboutLink(); clickAboutUsLink(); } private void closeOverlay() { List<WebElement> webElementList = webDriver.findElements(By.tagName("a")); if (webElementList != null && !webElementList.isEmpty()) { webElementList.stream() .filter(webElement -> "Close" .equalsIgnoreCase(webElement.getAttribute("title"))) .filter(WebElement::isDisplayed) .findAny() .ifPresent(WebElement::click); } } private void clickAboutLink() { webDriver.findElement(By.partialLinkText("About")).click(); } private void clickAboutUsLink() { webDriver.findElement(By.partialLinkText("About Baeldung.")).click(); }
We can check if the required information is available on the displayed page:
public boolean isAuthorInformationAvailable() { return webDriver .findElement( By.xpath("//*[contains(text(), 'an engineer with a passion')]")) .isDisplayed(); }
Next, we are going to test this class with both JUnit and TestNG.
3. With JUnit
Let’s create a new test class as SeleniumWithJUnitLiveTest:
public class SeleniumWithJUnitLiveTest { private static SeleniumExample seleniumExample; private String expecteTilteAboutBaeldungPage = "About Baeldung | Baeldung"; // more code goes here ... }
We’re going to use the @BeforeClass annotation from org.junit.BeforeClass to do an initial setup. In this setUp() method we are going to initialize the SeleniumExample object:
@BeforeClass public static void setUp() { seleniumExample = new SeleniumExample(); }
In a similar way, when our test case finishes, we should close the newly opened browser. We’re going to do this with @AfterClass annotation – to clean up the settings when test case execution has finished:
@AfterClass public static void tearDown() { seleniumExample.closeWindow(); }
Please note the static modifier on our SeleniumExample member variable – because we need to use this variable in the setUp() and tearDown() static methods – @BeforeClass and @AfterClass can be invoked on static methods only.
Finally, we can create our full test:
@Test public void whenAboutBaeldungIsLoaded_thenAboutEugenIsMentionedOnPage() { seleniumExample.getAboutBaeldungPage(); String actualTitle = seleniumExample.getTitle(); assertNotNull(actualTitle); assertEquals(actualTitle, expecteTilteAboutBaeldungPage); assertTrue(seleniumExample.isAuthorInformationAvailable()); }
This test method asserts that the title of the web page is not null and is set as expected. Besides that, we check that the page contains the expected information.
When the test runs, it simply opens the URL in Firefox and subsequently closes it after the title of the web page and content have been verified.
4. With TestNG
Let’s now use TestNG to run our test case/suite.
Note that if you’re using Eclipse, the TestNG plugin may be downloaded and installed from the Eclipse Marketplace.
First, let’s create a new test class:
public class SeleniumWithTestNGLiveTest { private SeleniumExample seleniumExample; private String expecteTilteAboutBaeldungPage = "About Baeldung | Baeldung"; // more code goes here ... }
We’ll use a @BeforeSuite annotation from org.testng.annotations.BeforeSuite to instantiate our SeleniumExample class. The setUp() method will be launched just before the test suite is activated:
@BeforeSuite public void setUp() { seleniumExample = new SeleniumExample(); }
Similarly we’ll use the @AfterSuite annotation from org.testng.annotations.AfterSuite to close our opened browser once the test suite has completed:
@AfterSuite public void tearDown() { seleniumExample.closeWindow(); }
Finally, let’s implement our test:
@Test public void whenAboutBaeldungIsLoaded_thenAboutEugenIsMentionedOnPage() { seleniumExample.getAboutBaeldungPage(); String actualTitle = seleniumExample.getTitle(); assertNotNull(actualTitle); assertEquals(actualTitle, expecteTilteAboutBaeldungPage); assertTrue(seleniumExample.isAuthorInformationAvailable()); }
After a successful completion of the test suite, we find HTML and XML reports in the test-output folder of the project. These reports summarize the test results.
5. Conclusion
In this quick article, we’ve focused on a quick intro to writing Selenium 3 tests with both JUnit and TestNG.
As always, the source for the article is available over at GitHub.