Scribd
Upload
3 views

01_01_Automation Testing

Uploaded by

minhtandragon29
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
3 views

01_01_Automation Testing

Uploaded by

minhtandragon29
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

What is Automation Testing?

Manual Testing is performed by a human sitting in front of a computer


carefully executing the test steps.
Automation Testing means using an automation tool to execute your
test case suite.
The automation software can also enter test data into the System Under
Test, compare expected and actual results and generate detailed test
reports. Test Automation demands considerable investments of money
and resources.
Where is Automated Test in
SDLC?
Why Automated Test?

Manual Testing of all workflows, all fields, all negative scenarios is time and money consuming

It is difficult to test for multilingual sites manually

Automation does not require Human intervention. You can run automated test unattended (overnight)

Automation increases the speed of test execution

Automation helps increase Test Coverage

Manual Testing can become boring and hence error-prone.


Which Test Cases to Automate?

High Risk - Business Critical test cases

Test cases that are repeatedly executed

Test Cases that are very tedious or difficult to perform manually

Test Cases which are time-consuming


What is test cases not suitable for
automation
Test Cases that are
newly designed Test Cases for
and not executed which the
manually at least requirements are
once frequently
changing

Test cases which


are executed on an
ad-hoc basis.
Automated Testing Process:
Define the scope of Automation

The features that are important for the business


Scenarios which have a large amount of data
Common functionalities across applications
Technical feasibility
The extent to which business components are reused
The complexity of test cases
Planning, Design, and
Development

Automation tools selected

Framework design and its features

In-Scope and Out-of-scope items of


automation

Automation testbed preparation

Schedule and Timeline of scripting and


execution

Deliverables of Automation Testing


Framework for Automation

Maintaining consistency of Testing


Improves test structuring
Minimum usage of code
Less Maintenance of code
Improve re-usability
Non Technical testers can be involved in code
The training period of using the tool can be reduced
Involves Data wherever appropriate
Types of frameworks used in
automation software testing
Data Driven Keyword Driven
Automation Automation
Framework Framework

Hybrid Automation
Modular Framework
Automation
Framework
Benefits of Automation Testing

70% faster than the manual testing


Wider test coverage of application features
Reliable in results
Ensure Consistency
Saves Time and Cost
Improves accuracy
Human Intervention is not required while execution
Benefits of Automation Testing

Increases Efficiency
Better speed in executing tests
Re-usable test scripts
Test Frequently and thoroughly
More cycle of execution can be achieved through automation
Early time to market
Automation Testing Tools

Selenium QTP WATIR

Rational
mabl Functional
Tester
Selenium
It provides the provision to export recorded script in other languages like Java, Ruby, RSpec, Python, C#, etc

It can be used with frameworks like JUnit and TestNG

It can execute multiple tests at a time

Autocomplete for Selenium commands that are common

Walkthrough tests

Identifies the element using id, name, X-path, etc.

Store tests as Ruby Script, HTML, and any other format

It provides an option to assert the title for every page

It supports selenium user-extensions.js file

It allows to insert comments in the middle of the script for better understanding and debugging
mabl
Proprietary machine learning
models automatically identify
and surface application issues

Tests are automatically


repaired when UI changes

Automated regression insights


on every build
QTP (MicroFocus UFT)

It is easier to use for a non-technical person to adapt to and create working test cases

It fix defects faster by thoroughly documenting and replicating defects for developer

Collapse test creation and test documentation at a single site

Parameterization is easy than WinRunner

QTP supports .NET development environment

It has better object identification mechanism

It can enhance existing QTP scripts without "Application Under Test" is available, by using the active screen
Rational Functional Tester

It supports a wide range of protocols and applications like Java, HTML, NET, Windows, SAP, Visual Basic, etc.

It can record and replay the actions on demand

It integrates well with source control management tools such as Rational Clear Case and Rational Team Concert integration

It allows developers to create keyword associated script so that it can be re-used

Eclipse Java Developer Toolkit editor facilitates the team to code test scripts in Java with Eclipse

It supports custom controls through proxy SDK (Java/.Net)

It supports version control to enable parallel development of test scripts and concurrent usage by geographically distributed team
WATIR

It supports multiple browsers on different platforms

Rather than using proprietary vendor script, it uses a


fully-featured modern scripting language Ruby

It supports your web app regardless of what it is


developed in
References
• https://www.guru99.com/automation-testing.html#11

You might also like