[go: up one dir, main page]

0% found this document useful (0 votes)
188 views21 pages

Automation Feasibility Analysis: Vinoth Rathinam Tutorials

The document discusses the key steps in automation feasibility analysis and test automation process. It covers determining if an application can be automated, selecting appropriate tools, evaluating frameworks, building a proof of concept, creating test plans, developing and executing test scripts, and analyzing results. Cross browser testing is also summarized as testing an application across different browsers to ensure consistent functionality.

Uploaded by

vinothrwins
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
188 views21 pages

Automation Feasibility Analysis: Vinoth Rathinam Tutorials

The document discusses the key steps in automation feasibility analysis and test automation process. It covers determining if an application can be automated, selecting appropriate tools, evaluating frameworks, building a proof of concept, creating test plans, developing and executing test scripts, and analyzing results. Cross browser testing is also summarized as testing an application across different browsers to ensure consistent functionality.

Uploaded by

vinothrwins
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

Automation

Feasibility
Analysis
Develop Test
Script , Appropriate
Execute and Tool
Analyze Selection
Results
Automation
Testing
Process

Creation of Vinoth Rathinam Tutorials Evaluable the


Test Plan Suitable
Framework

Build Proof of
Concept(POC)
Vinoth Rathinam Tutorials
1. Automation Feasibility Analysis
• First step is to check if the application can be automated or not. Not
all applications can be automated due to its limitations.
• The inputs from this phase will be more helpful for estimations.

• Type of application – Window, Web , Java , Mainframe etc.


• Application which can be and which cant be automation points needs
to be considered.

Vinoth Rathinam Tutorials


2. Appropriate Tool Selection 
• Which tools can be used for Automation? Eg: Selenium, UFT , Ranorex
etc.
• It depends on the technology in which the application is built, its
features and usage.
• It also depends on the Tool cost, Team size, Effort, ROI(Return of
Investment) and project scope.

Vinoth Rathinam Tutorials


3. Evaluate the Suitable Framework 
• Upon selecting the tool, the next activity is to select a suitable
framework. There are various kinds of frameworks and each
framework has its own significance

Vinoth Rathinam Tutorials


4. Build Proof of Concept
• Proof of Concept (POC) is developed with an end-to-end scenario to
evaluate if the tool can support the automation of the application.
• It is performed with an end-to-end scenario, which ensures that the
major functionalities can be automated.
• This phase will be more helpful to find the tool and framework
drawbacks.
• If the POC is successful, then we have to start the Automation for the
all automatable test cases.
• This phase is the deciding factor for Automation.

Vinoth Rathinam Tutorials


5. Test Plan
Detailed test plan will be created which contains details as mentioned below:
• Objective
• Scope
• Test Strategy
• Hardware and software requirements
• Environments requirement
• Test Schedule
• Risk Factors and Assumptions
• Features to be test and not tested
• Resources Roles and Responsibility
• Deliverables
• Exit Criteria (Sign-Off)
• Approval from client/ Stack holders.
Note: It varies from project to project. Mentioned here are list of important checklist.
Vinoth Rathinam Tutorials
6. Develop Test Script, Execute, and
Analyze
1. Develop Test Script
• Start creating test script based on your requirement.
• Development must be based on Screen wise rather than flow wise. So that we can try to
create as many reusable methods or functions or components.
• All the coding standards needs to be followed while developing test scripts
• The sign off purely depends on the automation deliverable. We make sure proper
reporting statements are added. It will be also helpful in case of failure of test script to
find the root cause.
• After completing all the reusable components or functions, design the end to end
scenario based on the requirements.
• Internal team review and external review needs to be done. To avoid reworks in future.
• Documenting the best practice and lesson learnt or technical issue faced during
development phase. It will be helpful to avoid same issue next time.

Vinoth Rathinam Tutorials


6. Develop Test Script, Execute, and
Analyze
2. Execute and Analyze Test Script
• Make sure data setup is ready to start the execution phase
• Execute all the test scripts in the required environments
• Deliverables such as Excel report, Screenshot, HTML report etc needs to be
generated as per the requirement
• In case of failure compulsory screen shot with log needs to be reported in the
reports.
• Must execute the test cases as batch wise. It will be more helpful to find the
unstable script or page. Based on the analysis we can update the scripts
• If defect are found during execution, raise the defect to the respective team
• After all the test scripts passed, share the reports to the Review team and get
Sign-Off.
Vinoth Rathinam Tutorials
What is Cross Browser Testing?

• Cross Browser Testing is a type of functional test to check that your


web application works as expected in different browsers.

Vinoth Rathinam Tutorials


Why do we need Cross Browser
Testing?
•  The web application will work as expected in all popular browsers so that more
people can access it and use it.
Reason Cross Browser Issues
1. Font size mismatch in different browsers.
2. JavaScript implementation can be different.
3. CSS,HTML validation difference can be there.
4. Some browser still not supporting HTML5.
5. Page alignment and div size.
6. Image orientation.
7. Browser incompatibility with OS. Etc.

Vinoth Rathinam Tutorials


Test Design & Execution
Automation across Lifecycle

NextGen Automation

5th GENERATION

Advanced Automation

4th GENERATION

Non Conventional Automation

Conventional Automation
3rd GENERATION

2nd GENERATION
1st GENERATION • Script-less Automation

• Data driven frameworks


• Key words driven frameworks
• Record & Playback
• Use & Reuse of Functions

Vinoth Rathinam Tutorials


What a Test Automation Framework is ?

It is a structured combination of :

Various Assumptions for Testing

Testing Concepts

Testing Practices
Utility of Test Automation Framework
Provides an Outline of overall Test Structure

Ensures Consistency of Testing

Minimizes the Amount of Code for Development - thereby


Less Maintenance

Maximizes Reusability

Reduces Exposure of Non-Technical Testers to Code

Enables Test Automation using Data


Benefits - Automation Framework Combined with Systematic Approaches

Significant Reduction in Testing Cycle Time

Comprehensive Coverage against Requirements

Use of a "Common Standard" across the


Organization / Product Team / Project Team
Generation of Reusable Test Scripts ( Utility Functions)

Systematic Maintenance of Automation Scripts

Data Pooling
How Many Types of
Automation Frameworks are there ?

Generally there are 4 Types :

Data Driven Automation Framework

Keyword Driven Automation Framework

Modular Automation Framework

Hybrid Automation Framework


Data Driven Automation Framework

Advantages :

Repeated use of Test Scripts with Different Inputs and


Response Data coming out of Predefined Dataset

Easy to implement in IBM - RFT with the help of Datapools

Helps in Reducing Coding for Large Test Cases

Ease of Testing of Time-Consuming & Complex Test Cases


Keyword Driven Automation Framework

Attributes :

As the Name suggests, it enables Keyword Driven Testing


or Table Driven Testing

Data & Keyword Tables being Independent of the


Automation Tool

Enables Documentation of the Functionality of the


Application under Test (AUT) in A Tabular Format
Modular Automation Framework

Types of Modular Frameworks :

Test Script Modularity Framework:

Enables creation of Small, Independent Scripts representing


Modules & Functions of the Application under Test (AUT)

Test Library Architecture Framework:

Enables creation of Library Files representing Modules &


Functions of the Application under Test (AUT)
Hybrid Automation Framework

Attributes :

It is the Most Popularly Implemented Framework

It is a Combination of the Three Types of Frameworks


described before

It has an Ability of Evolving Itself Over a Passage of Time


and Over Many Projects
Framework Architecture
Run Manager.xls2
<Batch Run Configurations>

<Test case details>

Allocator1
<Batch Execution Controller>

<Test case details>


Support Libraries4
<Generic reusable functions>

Test Scripts2
<One Script per Testcase>
Driver Script3
<Keyword processor
with in-built error handling>

Customized
Test
Business Flow3
Results6
<Keyword Driven>
<HTML, Excel>

Data driving Reporting


Library Library

Business Keywords3
<Building blocks of test cases>

Core Utility Test Data5


Library Library <Data Driven>
Business Component
Components Groups

Vinoth Rathinam Tutorials


Framework Overview

2.
Business
Flow
1. 3. Test
Business Data
Keywords

7.
Customized
Test Results

6. Allocator 4. Support
& Run Libraries
Manager
5. Test
Scripts

Vinoth Rathinam Tutorials

You might also like