Book Image

RPA Solution Architect's Handbook

By : Sachin Sahgal
Book Image

RPA Solution Architect's Handbook

By: Sachin Sahgal

Overview of this book

RPA solution architects play an important role in the automation journey and initiatives within the organization. However, the implementation process is quite complex and daunting at times. RPA Solution Architect’s Handbook is a playbook for solution architects looking to build well-designed and scalable RPA solutions. You’ll begin by understanding the different roles, responsibilities, and interactions between cross-functional teams. Then, you’ll learn about the pillars of a good design: stability, maintainability, scalability, and resilience, helping you develop a process design document, solution design document, SIT/UAT scripts, and wireframes. You’ll also learn how to design reusable components for faster, cheaper, and better RPA implementation, and design and develop best practices for module decoupling, handling garbage collection, and exception handling. At the end of the book, you’ll explore the concepts of privacy, security, reporting automated processes, analytics, and taking preventive action to keep the bots healthy. By the end of this book, you’ll be well equipped to undertake a complete RPA process from design to implementation efficiently.
Table of Contents (25 chapters)
1
Part 1:Role of a Solution Architect
5
Part 2:Being Techno/Functional
11
Part 3: Tool Agnostic Approach
17
Part 4:Best Practices
22
Epilogue

Integration testing

So, we are ready to test, and this will be our first integration test to find out how our team and SA did in their commitment to a better, faster, and cheaper bot. Let’s find out by arranging a series of steps that will help to perform this very important test and streamline it. As the name suggests, integration testing involves connecting all the modules and code snippets to make them work in tandem and get the desired outcome. It is very important to perform this type of testing from time to time so that we don’t leave any loose threads. The best practices to perform integration testing are as follows:

  • Test data: Data is the most important factor in testing, and good-quality data is what we need to perform these tests. When we talk about good quality data, we mean production-grade data and nothing that is cooked or man-made. This data should be of sufficient size so that you can perform a few iterations of this test. It is always advisable...