Skip to main content

5 minutes guides to using Selenium Tests Framework

The best way to learn to write tests using STF is is to use sample STF project, but in a gist – 

• Each test class should extend SeleniumTestPlan Class. SeleniumTestPlan class sets context of test i.e. browser environment etc 

/**
 * Tests valid and invalid login use cases for Test Link
 *
*/
public class TestLinkLoginTest extends SeleniumTestPlan


• Each page object should extend PageObject class. Refer Page Object Description for more on this. PageObject class provides methods for interaction with page like – launching URL, selecting frame, waiting for element availability etc 

/**
 * Defines service for TestLink login page
 * 
*/
public class TestLinkLoginPage extends PageObject {

page object would contain the page element of page. i.e. – Textbox, Dropdown etc – 

    private static LinkElement seleniumTrainingLink = new LinkElement("Selenium Training LinkElement", By.linkText("Free Selenium Training"));
    private static TextFieldElement loginTextBox = new TextFieldElement("Login Text Box", By.id("login"));

If you want to launch application URL then you should create page object for a page with Boolean parameter true else you can just create page object without any parameter. In the former case you can use appURL defined in testng.xml to launch application or have your own mechanism of launching URL. You can see it's example in sample project

page object would encapsulate page operations in page object methods. i.e. - 


/**
     * Logging in with valid credentials direct user to home page
     *
     * @param user
     * @return
     * @throws Exception
*/
public AdminHomePage loginAsValidUser(User user) throws Exception {
        loginTextBox.clear();
        loginTextBox.sendKeys(user.getUserID());
        passwordTextBox.clear();
        passwordTextBox.sendKeys(user.getPassword());
        loginButton.submit();
        return new AdminHomePage();
}

• For data driven tests define you test data object. Following example defines User object – 

/**
 * User account for TestLink
 */
public class User {

    private String userID;
    private String password;

    public String getUserID() {
        return userID;
    }

   public String getPassword() {
        return password;
    }

    public void setUserID(String userID) {
        this.userID = userID;
    }

    public void setPassword(String password) {
        this.password = password;
    }
}

Now define your test data in a CSV. CSV file would contain Test method details and test data details. i.e. 

TestEntity.TestCaseId,TestEntity.TestMethod,TestEntity.TestTitle,User.UserID,User.Password
testcaseid1,loginAsInvalidUser,loginAsInvalidUser,wronguserid,wrongpassword
testcaseid2,loginAsValidUser,loginAsValidUser,admin,admin

Herein loginAsInvalidUser and loginAsValidUser are two test methods and each test method is run for one set of test data. 
To run same test method with different data set, define corresponding data sets for method in csv file – 

TestEntity.TestCaseId,TestEntity.TestMethod,TestEntity.TestTitle,User.UserID,User.Password
testcaseid1,loginAsInvalidUser,loginAsInvalidUser,wronguserid1,wrongpassword1
testcaseid2,loginAsInvalidUser,loginAsInvalidUser,wronguserid2,wrongpassword2

Define the data provider method and consumer in your class – 

@DataProvider(name = "loginData", parallel = true)
    public static Iterator<Object[]> getUserInfo(Method m,
                                                 ITestContext testContext) throws Exception {
      // Some magic here 
    }

/**
     * Logs in to TestLink as valid user
     *
     * @param testObject
     * @param user
     * @throws Exception
     */
    @Test(groups = {"loginTestSuccess"}, dataProvider = "loginData",
            description = "Logs in to TestLink as admin")
    public void loginTestSuccess(TestEntity testEntity, final User user)
            throws Exception {

        new TestLinkLoginPage(true)
                .loginAsValidUser(user)
                .verifyDocumentationDropDown();
    }


And not just this, there are many more features described in sample test project of STF. 
Enough of "Gyan"? Want install Selenium Tests Framework and try sample project which uses STF? 

Popular posts from this blog

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea