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

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

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