Learn Test Automation Framework Creation Using Selenium


Folks we have written a tutorial for aspiring test automation engineers who wants to learn Webdriver and looking for Test Automation Framework creation knowledge. The project contains a bunch of chapters right from "writing your first Selenium test" to "how to implement Page Object Pattern". 
We have hosted the sample framework in Github and is for illustration purpose. 
It will demo the implementation of Java with WebDriver (aka Selenium 2) and how to write automated tests. The chapters are created in a evolving manner where the first chapter tests are very simple enough (how a beginner would write) and then slowly they have been evolved (how a professional would write).
Who's the Target Audience: To work, interact and make the best out of the project a person is required to have a basic knowledge of Java, Selenium API, TestNG and GIT. Just to clear this tutorial is not meant to teach you Java. This is more to teach and enable you to how to write automated tests in Java using Selenium and TestNG.
Application Under Test: We are using Cleartrip website (http://www.cleartrip.com) for demonstration of automation. This website was obvious choice as it is rich with controls like Textbox, Drop down, Calendar control, Ajax wait etc. The Scenarios considered are mostly the day to day business use case where in we have used ticket booking business scenario and it's different flavours. You need to have one of the IDE either Eclipse or IntelliJ to import the test and read through it. Once you are done with cloning the project , you need to import the project. Your preferred IDE might throw some error if path to JDK is not set properly. I expect the users to solve those problems on their own but in case they are not able to then do write to me on my email id.
How to Start: In the src folder of the project we have a README package which houses the read me for the chapters. This is a good point to start. I would suggest the users to read the chapters first and then browse through the Scenarios package to see the implementations. You can skip the starting chapters if your familiarity level with Selenium/Java is on the higher side. One good way to practice would be create a sample java class file and start experimenting by starting to write the test on the similar lines.
Support: In case of any help needed, do write us at tosukeshk@gmail.com or nishuverma@gmail.com
Feedback: We have also added an Issues tab in GIT where you can report issue or problem you are stuck with. We are very much happy to get your feedbacks. Off late Cleartrip has been revamping the site and we have noticed that there are some changes in the HTML as well. So you might see some tests failing, don't panic either you can fix it and submit the changes or drop us an email (we will fix and let you know).
Help us make it better and spread the word to the folks who are interested in learning Selenium.

Comments

Post a Comment

Your comments will be reviewed and then published !

Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »