Easy Way To Move From Manual Testing To Automation

In today’s world all industries are moving from manual work to automation to reduce time along with maintaining high quality standards.

IT industry will also be affected by this transition from manual to automation.

Major hindrance for IT industry to move from manual to automation is lack of skilled resource. Important part of manual work in IT industry is done by software tester.

A software tester job is to Analyzing the Requirements from the client, Participating in preparing Test Plans, Preparing Test Scenarios,test cases, Defect Tracking

As all major IT industry are working on Agile methodology which focuses mainly on delivering project to clients with minimal time spent on Test Planning. As a result Test Case Execution is the major time consuming process in Test Life Cycle.

Test Case execution can be automated but it required skilled resource to prepare automation script.

To achieve transition from manual testing to automation testing we have prepared Dynamic Automation Testing Framework which can be implemented on any Web Application.

Any person with relevant experience in testing field can write automation script for project.

Here is the demo project which was implemented using Dynamic Automation Testing Framework:

Steps to run automation script

• Requirements

S/W: Install JRE 7 or higher

OS: Windows, Mac or Linux

Browsers: Chrome, Mozilla or Internet Explorer

• File Path

Download zip file from below location

https://drive.google.com/file/d/0B66nTsXabvYYV1dGeEgzX0pHTVk/view?usp=sharing

Extract downloaded folder.It should contain below 5 files.

• Object Repository file

Open OR.txt file. It contains element locator and its Key which we will be using in Test Steps sheet. In the OR.txt file we can specify the browser in which you want to run the script. For e.g. to run script in Mozilla replace ‘Chrome’ with ‘Mozilla’. To run in Internet Explorer replace ‘Chrome’ with ‘IE’. Mention site URL for key siteURL as shown below. Place element locator with appropriate keyword. For e.g. user name text box is mentioned as txtbx_username, passenger  drop down in mentioned as dd_passengercount.

• DataEngine.xls file

Open DataEngine.xls file. It contains three sheets as below.

Test Cases, Test Steps and Settings

• Test Cases:

Test Case Module: Specify name of test case to executed

Description: Proper description should be specified so the it will describe the test scenario to be executed

Run Mode: Only those test cases having Run Mode as Yes will be executed. Test Cases with Run mode as No will be skipped

Result: Result of Pass/Fail test cases will be stored in Result Column. If any of the Test Step fails the whole Test Case will be considered as Fail

Comment: Mention comment if any specific condition or special care to be taken for the Test Case

• Test Steps:

Test Case Module: It should be same as specified in Test Case sheet.

TS_ID: It should be sequential and unique to identify test steps

Description: Proper description should be entered so that user can understand executed test steps

Page Name: Mention appropriate page name to retrieve corresponding object of the page

For. e.g If user selects Login_Page then in the Page Object column object of only Login page will be displayed

Page Object: Page object are Keys for the elements on the page. It will be same as that specified in OR.txt file. Based on this Key framework is able to find the element on which action needs to be performed.

Action Keyword: Operation to be performed on the page element is specified in Action Keyword column. For e.g. for Enter user name test step we have specified input action.

Data Set: For action which needs data to be entered by user are specified in Data Set column.

Run: Only those Test Steps for which user have specified ‘Yes’ in Run column will be executed. All other Test Steps will be skipped.

Result: After execution of Test Steps result will be stored in Result Column

Comment: If any error is encountered during execution of Test Steps then detailed description of it will be mentioned in comment column. If test steps passes then  description of executed test steps is displayed in comment column

• Settings

Page Name: Page Name in Test Steps

Login_Page Objects: Module/Page wise grouping of element locators

Action Keywords: List of action that can be performed on page elements.

• HTML Report

After test execution HTML report will be generated showing each and every test steps and its result.HTML report contains chart showing number of test cases and test steps pass/fail. Screen shot of failed test steps will be captured in html report which can be used for review. Screen will help to find out cause of test step failure. From the chart we can know overall percentage of how many test steps passed.

• Test Report Email

Email will be send after end of Test Execution which will include excel and HTML file having test result.