Successful Methods in Test Automation

Content …Why Automation ?

Manual vs. Automated

Automation Methodologies – Best Method

Why QTP? – Advantages of QTP

Architecture Setup

Test Automation Architecture

Parallel Run – Manual vs. Automation

Prerequisite - Resource selection

Designing – Coding – Testing

Setup Requirements for Automation Runs

Maintenance/Support

Why Automation ? - Benefits

Benefits to Automation include increased software quality, improved time to market, repeatable test procedures, and reduced testing costs.

REDUCED TESTING TIME

IMPROVED TESTING PRODUCTIVITY

IMPROVED PRODUCT QUALITY

REDUCED QA COSTS

CONSISTENT TEST PROCEDURES

CAN SCHEDULE TEST RUNS

Manual vs. Automated

Manual Execution

• More No. of resources required• Slow,takes time to retest incase

of testing in multiple environments• There is a chance of overlook

Automation • Less No. of resources required• Fast, Accurate and Reliable• Improves testing productivity• Easy to Learn & Maintain

Automation MethodologiesAutomation MethodologiesMethodologies that have been found to be effective for automating functional or system testing for most business applications are broadly categorized as:

1.The "Functional Decomposition" Method: (Mostly followed for Desktop applications)

To reduce all test cases to their most fundamental tasks, and write User-Defined Functions, Business Function Scripts, and "Sub-routine" or "Utility“ Scripts which perform these tasks independently of one another

2. The "Key-Word Driven" or "Test Plan Driven" Method: (Mostly followed for Web based applications)

In this method, the entire process is data-driven, including functionality. This method uses the actual Test Case document developed by the tester using a spreadsheet containing special "Key-Words". 

Why QTP ?

Allows even novice testers to be productive in minutes. Create a test script by simply pressing a Record button and using an application to perform a typical business process. Each step in the business process is automated documented with a plain-English sentence and screen shot. Can easily modify, remove, or rearrange test steps. By capturing, verifying and replaying user interactions automatically, Identifies defects and helps ensure that business processes deliver the expected results and remain reliable throughout the lifecycle. Available for browser-based and Java-based applications and ERP/CRM solutions.

Why QTP ? Contd…

Report displays all aspects of the test run:

:: a high-level results overview,

:: an expandable Tree View of the test script

Specifying exactly ::

Where application failures occurred

The test data used

Application screen shots for every step that highlight any discrepancies

Detailed explanations of each checkpoint pass and failure

Can share reports across an entire QA and development team

Why QTP ? Contd…Supports functional testing of all popular environments, including ::Windows, Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft,terminal emulators

Architecture Setup

It takes at least 3 – 6 months to setup an architecture, which includes the following phases.

1.Installation: This includes hardware, software and network setup.

2. Analysis: This includes better understanding/definition of the base system covering all the Functional Area to be automated.

3. Pilot Project: This covers the scripting of the base functional area based on the analysis/defined architecture.After Completion of pilot,a Parallel Run (Manual Vs. Automation) is required.

4. Architecture Acceptance: This includes the Test Run of the pilot project on the defined architecture to continue further automation of functional areas over the base project.

Test Automation Architecture

ControlSpreadsheet

Test run report

QTP

ActionsActionsActions

Framework

Test Environments

Parallel Run – Manual vs. Automation

Parallel Execution:After the completion of Pilot Project, a parallel run can be done between Manual and Automation for at least 2 Releases to see the results

11 22 33 …… 5050 nn

Manual - 300 People Hours

Automation - 30 Machine Hours

Prerequisite - Resource selection

Following skills are required for the Automation Scripting/Projects.

Testers having exposure to coding

Good Analytical skills

Good Logic / Aptitude

Better understanding of SDLC and Testing Life Cycle

Problem Identification / Solving skills

Developers having testing knowledge

Attitude to learn

Exposure to other Automation Tools like Win Runner, Rational etc…

Designing – Coding – Testing

Functional Area Analysis/Requirement gathering/ Logical Designing

Deployment/ Functional Maintenance/ AreaPR/CR Requests Scripting

Testing / UAT / Bug Fixes

Setup Requirements for Automation Runs

Following are the base requirements for run Setup:

Dedicated machines for test runs

Stable Test Environment

Dedicated resources having exposure to QTP and Datasheets

Resources having Automated Functional Area knowledge

Latest Merged Automated test scripts

Quality Centre Setup – For Scheduling Automation Runs

Defect Tracking tool to log PR s / CR s

Updated test cases of the respective Functional areas

Maintenance/Support Following points should be taken into consideration for proper maintenance and support :

Dedicated Maintenance / Support Team

Tracking of all the changes in the coming releases

Team should respond to the PR’s on Priority

Team should update the script for all the PR’s / CR’s as per the coming release

Separate QTP setup for maintenance / support team

Version Control for test scripts, datasheets & library files

Merging of updated scripts should be in accordance with the standards

Thank You !