Skip to main content

Structure of test automation project

Have you come across situation when you did not know where you should keep the test class, page object or any supporting class. I am going to share some of the practices I follow when working on test automation project. Given that I work with java and maven, it solves the problem of the directory structure. Maven project may have many directory but these are the ones I use most -

src/main/java - any non test class, i.e - page object etc
src/main/resources - resources like - properties file, text file etc used by main classes
src/test/java - the test classes
src/test/resources - resources like - properties file, text file etc used by test classes.
target - this directory is created automatically building a maven project and

Let’s focus on src/main/java - this is a directory which contains all of non test code. I usually end up having following structure on src/main/java -

src/main/java
com.google
core
dataobjects
groups
model
navigation
pageobject
util

Hence it looks as -

Screenshot from 2016-07-27 10:16:07.png
Package core contains SelTestCase class which takes care of setup and teardown. Given that I use STF, I don’t have to set up browser myself and setup method is mere access to application URL, test environment etc

Screenshot from 2016-07-27 10:21:45.png

Package dataobjects contains the test data objects used by the test classes -

Screenshot from 2016-07-27 10:32:41.png

Package groups contains TestNG test group. It is set of classes with String constants so that I can easily change the group name by modifying the String constants.

Package model contains the API definition which are used by either test classes or page objects -

Screenshot from 2016-07-27 10:34:56.png

Package navigation contains the Navigation APIs for navigating through application pages. Hence navigation steps don’t have to be repeated in test classes or page objects -

Screenshot from 2016-07-27 10:40:02.png

Package pageobject does not need any introduction :-). I further divide pageobject package into application areas for which page objects are to be created -

Screenshot from 2016-07-27 10:45:12.png

I further divide /resources package into application environment related entities. I set up environment parameter in testng.xml file and depending on the environment corresponding data set is picked up for test run -

Screenshot from 2016-07-27 10:49:45.png

The test package contains the test classes. Like the page object, I created various packages to contain test classes of application area -

Screenshot from 2016-07-27 10:54:30.png

At times I also create util package containing utility classes. Though I would not recommend this approach as util package tends to become dumping ground of unrelated classes. A better approach would be to create dedicated packages for those classes.

This brings us end to this post. What do you think of this package structure? How does your test structure look like?

Popular posts from this blog

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

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

Selenium Tutorial: Pattern Mathing using Selenium

I must confess I have never been admirer of Regular Expression but then there are times you can not escape from it, especially while working on a website which has dynamic contents appeared in static text and you want to validate it. like - "Validate that this text appears and there is 123 here and 456 here" And the test condition is 123 and 456 could be any three digits but number if digits should not be more than three. In a crude way we can at least test this - Assert.assertTrue(selenium.getText("elementLocator").contains("Validate that this text appears and there is")); but what if text goes wrong after "and there is"... what if more than 3 digits appear in text. This is where pattern matching/regular expression comes for our rescue and we can use matches method of String class to achieve same. So the assertion would be - String text = selenium.getText("elementLocator"); Assert.assertTrue(text.matches("Validate