This document discusses robotic process automation (RPA) and automation testing, providing an introduction and overview of each topic. It aims to clarify the differences and similarities between RPA and automation testing, as the two areas are often confused. While both involve automating processes, RPA is used to automate production processes by deploying software bots, whereas automation testing involves writing test scripts to validate application functionality. The document provides definitions and examples to explain the concepts and how each approach works.

1. This document is confidential and contains proprietary information, including trade secrets of CitiusTech. Neither the document nor any of the information
contained in it may be reproduced or disclosed to any unauthorized person under any circumstances without the express written permission of CitiusTech.
Demystifying Robotic Process Automation
(RPA) & Automation Testing
April 2020 | Authors: Prithu George, Hitangi Savla
CitiusTech Thought
Leadership

2. 2
Agenda
 Introduction to RPA
 Understanding Concepts and Terminology
 How does it Work?
 Similarities – RPA and Automation Testing
 RPA v/s Automation Testing
 Conclusion
 References

3. 3
 Is RPA a testing tool?
 Is Test Automation like RPA?
 Could Selenium be used for RPA? Does a Robot execute RPA?
 How can RPA be used in testing?
There has been a lot of confusion around RPA and Automation testing as both are interchangeably
used. While RPA and Automation testing are two different aspects of automation, both have certain
similarities and differences. Here’s our perspective to debunk all myths and highlights facts of RPA and
Automation Testing.
Introduction to RPA

4. 4
What is Automation Testing?
Automation testing is a code / script written in any language with / without using any tool to compare
the actual outcome with the expected behavior of the application or system and report the result.
Purpose
 To reduce the manual testing effort of executing repetitive and complex tests
 Increase coverage of testing
 Improve software quality
 Better accuracy and speed
 Find bugs early in the Software Development Life Cycle (SDLC)
Scope of Automation Testing
 From the time the product is being built till it’s live in production
 Automated testing can take place at different phases of the product under development
• Coding Phase: For Unit testing
• Testing Phase: To perform testing such as Functional, Regression, Smoke, Sanity, API, etc.
• Deployment: Build verification testing
Understanding Concepts and Terminology (1/2)

5. 5
What is RPA?
The automation of processes with the help of software tools having AI or Machine Learning
capabilities by deploying bots is Robotic Process Automation.
Bot: Is a software code when packaged and deployed on an environment, can run multiple times (at a
much higher rate than would be possible for a human).
Purpose
 Replace repetitive, monotonous tasks performed by humans with a virtual workforce
 Lower operational risk by eliminating human errors such as tiredness or lack of knowledge
 Better accuracy and speed
 Insights and Analytics
 Better control
Scope of RPA
 The RPA process requires development environment to develop the Bots, QA environment to test
the Bots and once it undergoes a thorough review and a sign off it is deployed live in production
environment.
 In short, the main goal of RPA is to automate the manual process in the production environment.
Understanding Concepts and Terminology (2/2)

6. 6
Automation Testing
Process
 Gather information of AUT (application under test) such as tech stack, external interactions
involved (e.g. databases), files, environment, test data required
 Perform feasibility analysis to select the Automation candidate
 Identify the tool
 Create framework, test planning, and test script
 Test script execution and management
 Review and reporting
Tools for Automation testing
 Traditional: UFT, Selenium, RFT, Test Complete, Watir, QTP, Ranorex, etc.
 New: TOSCA, Katalon Studio, Mabl, Testim.IO, etc.
How does it Work? (1/2)

7. 7
RPA
Process
 Understand the domain. Identify and document the processes that can be automated
 Identify business priorities based on focus areas, organization objective, and automation goal
 Conduct feasibility analysis to determine if the process can be automated or not
 After identification of processes, conduct complexity analysis for effort estimation
 Tool selection: Evaluate key benefits / outputs such as technology, interface, usability, scalability,
accessibility, enhanced security, maintenance, cost, quick deployment, external factors, etc.
 Define and maintain implementation plan
 Design and develop automation solution
 Test bots developed
 Deployment to production, support and maintenance
 Monitoring: Define KPIs and analyse returns derived from automation
Tools used to perform RPA
 Tricentis TOSCA, Automation Anywhere, UiPath, Blue Prism, Work fusion, etc.
How does it Work? (2/2)

8. 8
 Both RPA and Automation testing are used to reduce human effort
 Helps reduce manual errors and improves accuracy
 RPA tools can be used for Automation testing and Automation tools such as TOSCA can be used
for RPA
 Both are beneficial for end users – Automation testing helps end users by delivering a tested
product and RPA replaces mundane or time-consuming process
 Both can be executed as scheduled and can run 24/7
Similarities – RPA and Automation Testing

9. 9
 Purpose: Automation testing is done to validate the features of the product, whether it adheres
to its standards or end user’s expectations. RPA is used to mimic end user’s actions
 Test Data: Automation Testing uses test data and tries to break the product feature considering
negative flows, various environments, browsers, end points etc. RPA uses Prod-like test data to
simulate the same behavior as the end user and ensures all possible scenarios are considered in
the automation
 Environments: Automation testing works on Dev / QA / UAT environment. RPA works on
production environment
 Strategies: Automation Testing ensures Functional, Regression, Smoke, Sanity End-to-End,
Integration, etc. testing is carried on the process. In RPA, Unit testing and Workflow testing is
carried out to ensure the process is working as it would in production
 Ease of use: Automation testing requires notable effort and knowledge of tools, language, test
data management, external files, etc. RPA is easy to implement as it does not require coding skills
RPA v/s Automation Testing (1/2)

10. 10
Considerations: RPA tools for Automation Testing
 Tools selection: Identifying the best fit tools based on the workflows, applications,
functionality, etc.
 Framework Support: Support for the various automation frameworks like BDD, Keyword
driven, data driven, etc.
 Continuous Testing: Support to integrate the automation suite with the CICD tools available
 Parallel execution: Support to execute the automation on multiple browsers /multiple
environments simultaneously
 Reporting Mechanism: The capability to create customized detailed batch execution reports
in the automation framework
Comparison of RPA tools on test automation
RPA v/s Automation Testing (2/2)
Parameters/Tool Automation Anywhere UiPath TOSCA
BDD Framework - - Yes
CI/CD - Yes Yes
Parallel Execution Yes Yes Yes
Reporting Yes Yes Yes

11. 11
 In a nutshell both concepts – Automation testing and RPA – are used for automation.
 There is a thin line for the user to take a call on which concept to adopt as per the requirements
received, though RPA tools can be used for testing with their own benefits, but the ultimate
decision is based on the purpose whether it is to validate the product (Automation Testing) or to
automate the processes (RPA).
Conclusion

12. 12
 https://www.quora.com/Can-Selenium-be-used-for-robotic-process-automation
 https://cloudqa.io/robotic-process-automation-rpa-test-automation-myths-and-facts/
References

13. 13
Thank You
Authors:
Prithu George
Asst. Vice President
Hitangi Savla
Technical Specialist
thoughtleaders@citiustech.com
About CitiusTech
4,000+
Healthcare IT professionals worldwide
1,500+
Healthcare software engineering
400+
HL7 certified professionals
25%+
CAGR over last 5 years
110+
Healthcare customers
 Healthcare technology companies
 Hospitals, IDNs & medical groups
 Payers and health plans
 ACO, MCO, HIE, HIX, NHIN and RHIO
 Pharma & Life Sciences companies