FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR IMPLEMENTING AUTOMATED TOOL FOR REGRESSION TESTING”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR IMPLEMENTING AUTOMATED TOOL FOR
REGRESSION TESTING
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of software testing. More particularly, the present disclosure relates to methods and systems for implementing an automated tool for regression testing.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Typically, when a software is developed, various levels of testing is performed to ensure that the software is running as per the requirements. When any change is made to such developed and already tested software, it is important to redo the testing process to ensure that the software still performs as per the requirements. This is known as regression testing. The changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components. A regression pack comprises a set of test cases executed for every new release or software. Traditionally, execution of the full regression test pack consumes more time and resource utilization.

[0004] Further, over the period of time various solutions have been developed to develop automated regression repository tools. However, there are certain challenges with existing solutions. In the existing solutions, a full regression test pack was executed resulting in more time and resource utilization. Also, existing solutions failed to identify regression test cases required for impacted systems or products for every new feature delivery during the Software development lifecycle (SDLC).
[0005] Thus, there exists an imperative need in the art to develop an automated regression repository tool, which the present disclosure aims to address.
OBJECTS OF THE INVENTION
[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide a system and a method for an automated regression repository tool.
[0008] It is another object of the present disclosure to provide a solution that identifies the exact impacted products, journeys and test cases, thereby reducing the overall regression test execution timeline and increasing test efficiency and resource utilization.
SUMMARY
[0009] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed

description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0010] An aspect of the present disclosure may relate to a method for implementing an automated tool for regression testing. The method comprises receiving, by a transceiver unit, one or more component names as a user input on a user interface, wherein, the one or more component names are stored in a database. Further, the method comprises identifying, by the identification unit, a set of external systems associated with each of the impacted API from the set of impacted APIs. Further, the method comprises identifying, by the identification unit, a set of products associated with each of the external system from the set of external systems. Further, the method comprises identifying, by the identification unit, set of journeys associated with each of the product from the set of products. Further, the method comprises identifying, by the identification unit, a set of regression test cases associated with the set of journeys. Further, the method comprises performing automatically, by a processing unit, an execution of the identified set of regression test cases.
[0011] In an exemplary aspect of the present disclosure, the identified set of external systems is integrated with the one or more component names.
[0012] In an exemplary aspect of the present disclosure, the database comprises a list of component names, a list of application programming interfaces (APIs), a list of external systems, a list of products, a list of journeys, a list of regression test cases, a data reflecting a relation between each of the component name from the list of component names and the list of APIs, a data reflecting a relation between each of the API from the list of APIs and the list of external systems, a data reflecting a relation between each of the external system from the list of external

systems and the list of products, a data reflecting a relation between the list of products and the list of journeys, and a data reflecting a relation between the list of journeys and the list of regression test cases.
5 [0013] In an exemplary aspect of the present disclosure, the list of component
names comprises the one or more component names.
[0014] In an exemplary aspect of the present disclosure, the identifying the set of
impacted APIs based on the received one or more component names is based on
10 the data reflecting the relation between each of the component name from the
list of component names and the list of APIs, as stored in the database.
[0015] In an exemplary aspect of the present disclosure, the identifying the set of
external systems associated with each of the impacted API from the set of
15 impacted APIs, is based on the data reflecting the relation between each of the
API from the list of APIs and the list of external systems, as stored in the database.
[0016] In an exemplary aspect of the present disclosure, the identifying the set of
products associated with each of the external system from the set of external
20 systems, is based on the data reflecting the relation between each of the external
system from the list of external systems and the list of products, as stored in the database.
[0017] In an exemplary aspect of the present disclosure, the identifying the set of
25 journeys associated with each of the product from the set of products, is based on
the data reflecting the relation between the list of products and the list of journeys, as stored in the database.
5

[0018] In an exemplary aspect of the present disclosure, the identifying the set of regression test cases associated with the set of journeys, is based on the data reflecting the relation between the list of journeys and the list of regression test cases, stored in the database. 5
[0019] Another aspect of the present disclosure may relate to a system for implementing an automated tool for regression testing. The system comprises a transceiver unit, the transceiver unit is configured to receive, one or more component names, as a user input on a user interface, wherein, the one or more
10 component names are stored in a database. Further, the system comprises an
identification unit, connected at least to the transceiver unit, the identification unit configured to: identify, a set of impacted application programming interfaces (APIs) based on the received one or more component names; identify, a set of impacted external systems associated with each of the impacted API from the set
15 of impacted APIs; identify, a set of products associated with each of the external
system from the set of external systems; identify, a set of journeys associated with each of the product from the set of products; identify, a set of regression test cases associated with the set of journeys. Further, the system comprises a processing unit, connected at least to the identification unit, the processing unit is configured
20 to perform automatically, an execution of the identified regression test cases.
[0020] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for implementing an
automated tool for regression testing, the instructions include executable code
25 which, when executed by one or more units of a system, causes: a transceiver unit
of a system to receive, one or more component names, as a user input on a user interface, wherein, the one or more component names are stored in a database; an identification unit of the system to: identify, a set of impacted application
6

programming interfaces (APIs) based on the received one or more component
names; identify, a set of impacted external systems associated with each of the
impacted API from the set of impacted APIs; identify, a set of products associated
with each of the external system from the set of external systems; identify, a set
5 of journeys associated with each of the product from the set of products; identify,
a set of regression test cases associated with the set of journeys. Further, the instructions include executable code, which when executed cause a processing unit of the system causes a processing unit to perform automatically, an execution of the identified regression test cases. 10
BRIEF DESCRIPTION OF DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the
15 disclosed methods and systems in which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each
20 component. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0022] FIG.1 illustrates an exemplary block diagram of a computing device upon
25 which the features of the present disclosure may be implemented in accordance
with exemplary implementation of the present disclosure.
7

[0023] FIG.2 illustrates an exemplary block diagram of a system for implementing an automated tool for regression testing, in accordance with exemplary implementations of the present disclosure.
5 [0024] FIG.3 illustrates an exemplary method flow diagram indicating the process
for implementing an automated tool for regression testing, in accordance with exemplary implementations of the present disclosure.
[0025] FIG.4 illustrates an exemplary sequence flow diagram indicating the
10 process for automated regression repository tool, in accordance with exemplary
implementations of the present disclosure.
[0026] The foregoing shall be more apparent from the following more detailed description of the disclosure. 15
DETAILED DESCRIPTION
[0027] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of
20 embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of
25 the problems discussed above. Some of the problems discussed above might not
be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
8

[0028] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure.
Rather, the ensuing description of the exemplary embodiments will provide those
5 skilled in the art with an enabling description for implementing an exemplary
embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
10 [0029] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the
15 scope of the disclosure. The functionality of specific units as disclosed in the
disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
20
[0030] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or
25 limitations on the described embodiments. The use of these terms is solely for
convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other
9

equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0031] Specific details are given in the following description to provide a thorough
5 understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the embodiments in unnecessary detail. In other instances, well-known
10 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the embodiments.
[0032] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
15 diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
20
[0033] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
25 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in
10

either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
5 [0034] As used herein, an “electronic device”, or “portable electronic device”, or
“user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical and computing device. The user
device is capable of receiving and/or transmitting one or parameters, performing
function/s, communicating with other user devices and transmitting data to the
10 other user devices. The user equipment may have a processor, a display, a
memory, a battery and an input-means such as a hard keypad and/or a soft
keypad. The user equipment may be capable of operating on any radio access
technology including but not limited to IP-enabled communication, Zig Bee,
Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-
15 Fi direct, etc. For instance, the user equipment may include, but not limited to, a
mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR)
devices, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, mainframe computer, or any other device as may be obvious to
a person skilled in the art for implementation of the features of the present
20 disclosure. Also, the user device may contain at least one input means configured
to receive an input from unit(s) which are required to implement the features of
the present disclosure.
[0035] Further, the user device may also comprise a “processor” or “processing
25 unit” includes processing unit, wherein processor refers to any logic circuitry for
processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a
11

DSP core, a controller, a microcontroller, Application Specific Integrated Circuits,
Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
The processor may perform signal coding data processing, input/output
processing, and/or any other functionality that enables the working of the system
5 according to the present disclosure. More specifically, the processor is a hardware
processor.
[0036] As discussed in the background section, the current known solutions for
automated regression have several shortcomings such as the execution of full
10 regression test pack that consumes more time and resource utilization.
[0037] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by identifying the exact impacted
products, journeys and test cases, and further automating the execution of such
15 test cases, thereby reducing the overall regression test execution timeline and
increasing test efficiency and resource utilization.
[0038] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
20
[0039] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (or referred to herein as a computing device [100]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing
25 device [100] may be in communication with a communication network (such as a
5th generation network) and may implement a method for implementing automated tool for regression testing utilising the system. In another implementation, the computing device [100] in communication with the
12

communication network, itself implements the method for implementing
automated tool for regression testing using one or more units configured within
the computing device [100], wherein a person skilled in the art would appreciate
that said one or more units are capable of implementing the features as disclosed
5 in the present disclosure.
[0040] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware
10 processor [104] may be, for example, a general-purpose microprocessor. The
computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main memory [106] also may be used for storing temporary variables or other
15 intermediate information during execution of the instructions to be executed by
the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only
20 memory (ROM) [108] or other static storage device coupled to the bus [102] for
storing static information and instructions for the processor [104].
[0041] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and
25 instructions. The computing device [100] may be coupled via the bus [102] to a
display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric
13

and other keys, touch screen input means, etc. may be coupled to the bus [102]
for communicating information and command selections to the processor [104].
Another type of user input device may be a cursor controller [116], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
5 information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
10 [0042] The computing device [100] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
15 computing device [100] in response to the processor [104] executing one or more
sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to
20 perform the process steps described herein. In alternative implementations of the
present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0043] The computing device [100] also may include a communication interface
25 [118] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
14

a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] may be a
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
5 implementation, the communication interface [118] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0044] The computing device [100] can send messages and receive data, including
10 program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128],
the ISP [126], the local network [122], the host [124] and the communication
interface [118]. The received code may be executed by the processor [104] as it is
15 received, and/or stored in the storage device [110], or other non-volatile storage
for later execution.
[0045] FIG.2 illustrates an exemplary block diagram of a system for implementing an automated tool for regression testing, in accordance with exemplary
20 implementations of the present disclosure. The system [200] comprises at least
one transceiver unit [202], at least one identification unit [204], at least one processing unit [206] and at least one storage unit [208]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown,
25 however, the system [200] may comprise multiple such units or the system [200]
may comprise any such numbers of said units, as required to implement the features of the present disclosure. The system [200] may be a part of a server or a network entity.
15

[0046] The system [200] is configured for implementing an automated tool for regression testing, with the help of the interconnection between the components/units of the system [200]. 5
[0047] As referred herein, the transceiver unit [202] comprises a transmitter module and a receiver module. The transceiver unit [202] is a device that combines the functionalities of both transmitting and receiving data.
10 [0048] At first, the transceiver unit [202] receives one or more component names,
as a user input on a user interface, wherein, the one or more component names are stored in a database. The one or more component names could be the names of the individual software components or modules that are being updated or impacted by a new feature. For example, the component names could include
15 “user authentication module” or “payment processing service”.
[0049] In one implementation, the database comprises a list of component names, a list of application programming interfaces (APIs), a list of external systems, a list of products, a list of journeys, a list of regression test cases, a data
20 reflecting a relation between each of the component name from the list of
component names and the list of APIs, a data reflecting a relation between each of the API from the list of APIs and the list of external systems, a data reflecting a relation between each of the external system from the list of external systems and the list of products, a data reflecting a relation between the list of products and
25 the list of journeys, and a data reflecting a relation between the list of journeys
and the list of regression test cases.
16

[0050] A list of component names refers to a series of names of the individual
software components or modules that are being updated or impacted by a new
feature delivery. For example, for an authentication module, impacted API can be
a User Authentication API and for a database connector, impacted API can be
5 Database Connection API.
[0051] A list of APIs refers to a series of names of APIs which are connected with
the individual components or modules provided by the user. The list of APIs may
include names of impacted APIs that are in connection with the components or
10 modules.
[0052] A list of external systems refers to a group of external systems linked to
one or more impacted APIs and impacted by it. For example, in case of a Weather
API: An API that provides weather data, the weather data provider's servers or
15 database is an external system associated with the weather API.
[0053] A list of products refers to a series of names of distinct products (e.g.,
software products) or applications associated with each of the external systems.
Each product represents a standalone entity that serves a specific purpose or
20 caters to a particular set of functionalities or features.
[0054] A list of journeys refers to a series of names of user journeys or scenarios that depict different paths or interactions users may take or experience while using the software products mentioned in the list of products. 25
[0055] A list of regression test cases refers to a comprehensive set of test cases designed to ensure that new updates, changes, or enhancements to the software products do not adversely affect existing functionalities or introduce new defects.
17

[0056] Further, the identification unit [204] is connected at least to the transceiver
unit [202]. The identification unit [204] is configured to identify, a set of impacted
APIs based on the received one or more component names. The term “API” as
5 used herein may correspond to mechanisms that enable two software
components to communicate with each other using a set of definitions and
protocols. Impact refers to a dependent or adverse effect by the respective
components. A set of Impacted APIs refers to a group of those APIs that depend
on the functionality provided by the identified components. They are affected
10 because any changes, updates, or issues with these components could potentially
affect the behavior or functionality of these APIs. Identifying these impacted APIs helps in understanding the scope of changes, or in troubleshooting when there are updates or issues with specific components.
15 [0057] It is to be noted that, the identification of the set of impacted APIs based
on the received one or more component names is based on the data reflecting the relation between each of the component name from the list of component names and the list of APIs, as stored in the database. The list of component names comprises the one or more component names. It is to be noted that at the time of
20 deployment of new feature, data reflecting the relation between component
name(s) and APIs is stored into the database and such data is later used for further reference.
[0058] A table representing an example of data reflecting a relation between each
25 of the component name from the list of component names and the list of APIs, is
given below.
[0059] The following examples are provided for illustrative purposes only and are not intended to limit the scope of the claims or the invention in any way.
18

Names of Components Application Programming Interfaces (APIs) Relation between component names and the APIs
Authentication module API 1 API 2 API 1 and API 2 are associated with the impacted component such as the authentication module. Hence the API 1 and API 2 are considered as impacted APIs from the list of APIs for the corresponding authentication module component.
Database connector
Data
processing
module API 3 Database connector and Data processing module are associated with the API 3. Hence the API 3 is impacted due to its connection with the database connector and data processing module.
Reporting module API 4 The reporting module is associated with the API 4. Hence the API 4 is impacted due to its connection with the reporting module.
Customer Maintenance Create Customer APIs such as create customer, update customer, and delete customer are associated with component such as customer maintenance, hence such APIs are considered as impacted APIs.
19

Update Customer The impacted APIs encapsulate the specific functionalities within the component that enable the creation, updating, and deletion of customer records. Each of the impacted APIs corresponds to a distinct operation that interacts with the customer maintenance component.

Delete Customer

Service Maintenance Create Service The service maintenance encompasses the management of service-related functionalities within a system. The APIs: create service, update service, and delete service are direct interfaces through which users or other modules interact with the service maintenance functionality. Hence, such APIs are associated with the service maintenance and considered as impacted APIs.

Update Service

Delete Service

Product Maintenance Create Product APIs such as create product, update product, and delete product are essential interfaces through which users or other modules interact with the product maintenance functionality. Hence such APIs are associated with the product maintenance and considered as impacted APIs.

Update Product

Delete Product

TABLE 1
[0060] Referring to the aforementioned table, the list of APIs may contain, for example, four APIs such as API 1, API 2, API 3, and API 4. The list of component
20

names may include an authentication module, a database connector, a data
processing module, and a reporting module. It is to be noted that when the
component name authentication module is provided by the user as an input, then
API 1 and API 2 may be considered as impacted APIs from the list of APIs. Similarly,
5 when the component name reporting module is provided by the user as an input,
then the API 4 may be considered as an impacted API. For example, APIs such as
create customer, update customer, and delete customer are associated with
impacted component such as customer maintenance. Hence, the APIs such as
create customer, update customer, and delete customer are considered as
10 impacted APIs due to their association with impacted component such as
customer maintenance.
[0061] In another example, APIs such as create product, update product, and delete product are associated with impacted component such as product
15 maintenance, hence the create product, update product, and delete product are
considered as impacted APIs. In yet another example, APIs such as create service, update service, and delete service are associated with impacted component such as service maintenance. Hence the create service, update service, and delete service are considered as impacted APIs.
20
[0062] The identification unit [204] is further configured to identify impacted operations and interfaces within such API and parameter level changes in the identified API.
25 [0063] Further, the identification unit [204] is configured to identify, a set of
impacted external systems associated with each of the impacted API from the set of impacted APIs. The identification of the set of external systems which are associated with each of the impacted API from the set of impacted APIs, is based
21

on the data reflecting the relation between each of the API from the list of APIs and the list of external systems, as stored in the database. The set of impacted external systems refers to a group or collection of external systems that interact with a main system or application via impacted APIs. 5
[0064] The identification unit [204] may identify internal changes within the impacted product, systems, and impacted components of offered release of new feature. The goal of the identification of the set of external systems is to identify integration impact of the change. 10
[0065] A table representing an example of a data reflecting a relation between each of the API from the list of APIs and the list of external systems, is given below.

Application Programming Interfaces (APIs) External systems Relation between external systems and the APIs
API 1 System 1 (e.g., banking system) If the system 1 experiences impacts on its components and operations due to its linkage with impacted API 1, then the system 1 is considered as impacted system 1 for the corresponding API 1.
API 2 System 2 (e.g., weather data provider server) The system 2 gets affected by the API 2.
API 3 System 3 The system 3 gets affected by the API 3 due to its linkage with impacted API 3.
22

API 4 System 4
Customer
Relationship
Management
(CRM)
Create Billing system
Customer
Middleware
Update
Customer

If the system 4 gets impacted due to its associated with the API 4, hence the system 4 is considered as impacted system 4.
When a new customer is created using
the create customer API, relevant
customer information is typically
synchronized with the CRM system. The create customer API triggers the creation of a billing account in the billing system. Middleware systems may facilitate the communication and synchronization between the CRM, billing system, and other operational systems. Hence the create customer API is associated with the CRM, billing system and middleware. Enables real-time updates of customer information for personalized service through the update customer API. Changes in customer details via the update customer API may trigger updates in billing information stored in the billing system. Middleware systems facilitate the seamless propagation of updated customer information across all integrated systems. This way the update customer API is associated with the CRM, billing system and middleware.

23

Delete Customer When a customer profile is deleted using the delete customer API, it Archives or deactivates customer profiles while retaining historical data within the CRM. Removes billing accounts and manages outstanding payments or refunds from the billing system via the delete customer API. Middleware Ensures coordinated deletion of customer records across all integrated systems. Thus, the delete customer API is associated with the CRM, billing system and middleware.
Create Service Self-care Channel system, Mediation System, Charging System Self-care channel, mediation system, and charging system are associated with the create service, update service and delete service APIs which perform the addition of new service, real-time adjustments to service parameters, and removal of services respectively.
Update Service

Delete Service

Create Product Point of Sale (POS), Voucher Management, Enterprise resource planning (ERP) Point of Sale (POS), voucher management, and ERP are associated with the create product, update product and delete product APIs.
Update Product

Delete Product

TABLE 2
24

[0066] Referring to the aforementioned table, if the system 1 faces impact on its
components and operations due to its association with impacted API 1, then the
system 1 is considered as impacted system 1 for the corresponding API 1. Similarly,
the systems 2,3, and 4 are associated with the API 2, API 3, and API 4 respectively
5 and are considered as impacted systems (2, 3, and 4) for the corresponding APIs
(API 2, 3, and 4). For example, APIs such as create customer, update customer, and Delete Customer are associated with each of the said systems such as CRM, billing system, and Middleware. Hence systems such as CRM, billing system, and middleware are considered as impacted systems. In another example, APIs such
10 as create service, update service, and delete service are associated with each of
the said systems such as selfcare channel, mediation system, and charging system. Hence systems such as selfcare channel, mediation system, and charging system are considered as impacted systems. In yet another example, APIs such as create product, update product, and delete product are associated with each of the said
15 systems such as POS, voucher management, and Enterprise resource planning
(ERP). Hence systems such as POS, voucher management, and Enterprise resource planning (ERP) are considered as impacted systems.
[0067] Further, the identification unit [204] is configured to identify, a set of
20 products associated with each of the external system from the set of external
systems. The identification of the set of products associated with each of the
external system from the set of external systems, is based on the data reflecting
the relation between each of the external system from the list of external systems
and the list of products, as stored in the database. The identified set of external
25 systems is integrated with the one or more component names. The set of products
refers to a group or category of products offered by the external system(s).
25

[0068] A table representing an example of a data reflecting a relation between each of the external system from the list of external systems and the list of products, is given below.

External Systems List of Products Relation between external systems and the list of Products
System 1 (e.g., banking system) Product 1 (e.g., mobile banking app) If product 1 (e.g., mobile banking app) gets impacted due to its linkage with impacted system 1 (e.g., banking system), then product 1 is considered as impacted product 1 for the corresponding system 1.
System 2 (e.g., weather data provider server) Product 2 (e.g., weather forecast mobile app) Similarly, the product 2 gets affected by the system 2.
System 3 Product 3 Similarly, the product 3 gets affected by the system 3.
System 4 Product 4 If the product 4 gets impacted due to its linkage with the system 4, then the product 4 is
26

considered as impacted product 4.
Customer Relationship Management (CRM), Billing system, Middleware Broadband
Airfibre
Multiprotocol Label Switching (MPLS) The CRM, billing system, and middleware are associated with products such as Broadband, Airfibre and MPLS. Hence these products are considered impacted products.
Self-care Channel, Mediation System, Charging System
The Self-care Channel, Mediation System, and Charging System are associated with products such as Broadband, Airfibre and MPLS. Hence these products are considered impacted products.
Point of Sale (POS), Voucher Management, Enterprise resource planning (ERP)
The POS, Voucher Management, and ERP are associated with the products such as Broadband, Airfibre and MPLS. Hence these products are considered impacted products.
27

TABLE 3
[0069] Referring to the aforementioned table, if the product 1 (e.g., mobile
banking app) gets impacted due to its linkage with impacted system 1 (e.g.,
banking system), then product 1 is considered as impacted product 1 for the
5 corresponding system 1. Similarly, the product 2 (e.g., weather forecast mobile
app) gets affected by the system 2 (e.g., weather data provider server). The
product 3 gets affected by the corresponding system 3 and is considered as the
impacted product 3. If the product 4 gets impacted due to its linkage with the
system 4, then the product 4 is considered as impacted product 4 for the
10 corresponding system 4.
[0070] For example, systems such as the CRM, billing system, and middleware are associated with products such as Broadband, Airfibre and MPLS. Hence these products are considered impacted products when CRM, billing system, and
15 middleware are impacted. In another example, systems such as self-care channel,
mediation system, and charging system are associated with products such as Broadband, Airfibre and MPLS. Hence these products are considered impacted products when self-care channel, mediation system, and charging system are impacted. In yet another example, systems such as POS, voucher management,
20 and ERP are associated with the products such as Broadband, Airfibre and MPLS.
Hence these products are considered impacted products when POS, voucher management, and ERP systems are impacted.
[0071] Further, the identification unit [204] is configured to identify, a set of journeys associated with each of the products from the set of products. In one
25 implementation, the identification of the set of journeys associated with each of
the product from the set of products, is based on the data reflecting the relation between the list of products and the list of journeys, as stored in the database. The set of journeys of each product is identified to know the collateral impact of
28

services or impacted consumers. In this context, journeys likely refer to specific
workflows, processes, or user journeys related to the product(s). Each journey
represents a sequence of steps or interactions that users or processes follow to
achieve a particular goal or outcome. The set of journeys refers to a list of journeys
5 associated with the product(s). Managing the set of journeys involves defining,
optimizing, and ensuring the smooth operation of these workflows to enhance user experience and operational efficiency.
[0072] A table representing an example of a data reflecting a relation between the
10 list of products and the list of journeys, is given below.

List of Products List of Journeys Relation between a list of products and Journeys
Product 1 (e.g., mobile banking app) Journey 1 (e.g., checking account balance and transferring funds)
Journey 2 (e.g., checking weather updates)
Journey 3 Journey 4 If Journey 1 (e.g., checking account balance and transferring funds) is impacted due to its linkage with impacted product 1 then Journey 1 is considered as associated Journey 1 for the corresponding product 1.
Product 2 (e.g., weather forecast mobile app)
Similarly, Journey 2 (e.g., checking weather updates) gets affected by the impacted product 2 (e.g., weather forecast mobile app).
Product 3
The Journey 3 gets affected by the product 3.
Product 4
If Journey 4 gets impacted due to its linkage with product 4, then Journey 4
29

is considered as associated Journey 4 for the corresponding product 4.
Broadband Provisioning Journey Provisioning journey is a journey associated with the provisioning of a broadband plan.
Airfibre Modification Journey Modification journey is a journey associated with modifying an Airfibre plan.
MPLS Termination Journey Termination journey is a journey associated with deletion of a customer/ plan that is associated with the MPLS product.
TABLE 4
[0073] Referring to the aforementioned table, If Journey 1 (e.g., checking account
balance and transferring funds) is impacted due to its linkage with impacted
5 product 1 (e.g., mobile banking app) then Journey 1 is considered as associated
Journey 1 for the corresponding product 1. Similarly, Journey 2 (e.g., checking
weather updates) gets affected by the impacted product 2 (e.g., weather forecast
mobile app). The journey 3 gets affected by the product 3. If the journey 4 gets
impacted due to its linkage with the product 4, then the journey 4 is considered as
10 associated journey 4 for the corresponding product 4.
[0074] For example, provisioning journey is a journey associated with the
provisioning of a broadband plan. Modification journey is a journey associated
with modifying an Airfibre plan. Termination journey is a journey associated with
15 deletion of a customer/ plan that is associated with the MPLS product. Hence
provisioning journey, modification journey, and termination journey are
30

considered as associated (or impacted journeys) with products such as broadband, Airfibre, and MPLS.
[0075] Further, the identification unit [204] is configured to identify, a set of
5 regression test cases associated with the set of journeys. In one implementation,
the identification of the set of regression test cases associated with the set of
journeys, is based on the data reflecting the relation between the list of journeys
and the list of regression test cases, stored in the database. The set of regression
test cases denotes a collection or group of regression test cases within a testing
10 framework. Regression tests are designed to verify that recent code changes have
not adversely affected existing functionality.
[0076] A table representing an example of a data reflecting a relation between the list of journeys and the list of regression test cases, is given below. 15

Journeys List of Regression test cases Relation between a list of Journeys and Regression test cases
Journey 1 (e.g., checking account balance and transferring funds) Test case 1 If that test case 1 is related to Journey 1 then the test case 1 is considered as associated with Journey 1.
Journey 2 (e.g., checking Test case 2 If test case 2 is related to Journey 2 then the test case 2 is considered as associated with Journey 2.
31

weather updates)
Journey 3 Test case 3 If test case 3 is related to Journey 3 then the test case 3 is considered as associated with Journey 3.
Journey 4 Test case 4 If test case 4 is related to Journey 4 then test case 4 is considered as associated with Journey 4.
Provisioning Journey Test case 1 (e.g.,
Broadband with 30 megabits per second (mbps)), Test case 4 (Broadband with 100 mbps and Over-the-Top (OTT) Services) The test cases 1 and 4 are associated with the provisioning journey.
Modification Journey Test case 2 (e.g., Change Broadband speed from 30 mbps to The test case 2 is associated with the modification journey.
32

100 mbps and addition of OTT service)
Termination Journey Test case 3 (e.g.,
Terminate customer in our systems and provide final settlement) The test case 3 is associated with the termination journey.
TABLE 5
[0077] Referring to the aforementioned table, if test case 1 is related to Journey
1 then test case 1 is considered as associated with Journey 1. If test case 2 is
5 related to Journey 2 then test case 2 is considered as associated with Journey 2. If
test case 3 is related to Journey 3 then test case 3 is considered as associated with
Journey 3. If test case 4 is related to Journey 4 then test case 4 is considered as
associated with Journey 4. For example, the test cases 1 and 4 are associated with
the provisioning journey due to the provisioning of a broadband plan. The test
10 case 2 is associated with the modification journey due to modification in the
broadband plan. The test case 3 is associated with the termination journey due to the termination of the customer services.
[0078] The processing unit [206] is connected at least to the identification unit
15 [204] and configured to perform automatically, an execution of the identified
regression test cases. The processing unit [206] triggers an event to Developer and
33

operations (DevOps) team/system to execute such identified regression test
cases. Thus, the automated tool for regression testing provides an automation of
the identification of regression test packs and execution of such regression test
cases, thereby reducing the overall regression test execution timeline and
5 increasing test efficiency and resource utilization.
[0079] Referring to FIG. 3, an exemplary method flow diagram [300], for
implementing an automated tool for regression testing, in accordance with
exemplary implementations of the present disclosure is shown. In an
10 implementation the method [300] is performed by the system [200].
[0080] Also, as shown in FIG. 3, the method [300] starts at step [302].
[0081] At step [304], the method [300] as disclosed by the present disclosure
15 comprises receiving, by a transceiver unit [202], one or more component names
as a user input on a user interface, wherein, the one or more component names are stored in a database.
[0082] The one or more component names could be the names of the individual
20 software components or modules that are being updated or impacted by the new
feature. For example, the component names could include “user authentication module” or “payment processing service”.
[0083] For instance, say, the user input includes the component name
25 “authentication module”.
[0084] In one implementation, the database comprises a list of component names, a list of application programming interfaces (APIs), a list of external
34

systems, a list of products, a list of journeys, a list of regression test cases, a data
reflecting a relation between each of the component name from the list of
component names and the list of APIs, a data reflecting a relation between each
of the API from the list of APIs and the list of external systems, a data reflecting a
5 relation between each of the external system from the list of external systems and
the list of products, a data reflecting a relation between the list of products and the list of journeys, and a data reflecting a relation between the list of journeys and the list of regression test cases.
10 [0085] It is to be noted that the list of component names comprises the one or
more component names. The database is used to read pre-configurations and store the output.
[0086] At step [306], the method [300] as disclosed by the present disclosure
15 comprises identifying, by an identification unit [204], a set of impacted application
programming interfaces (APIs) based on the received one or more component names.
[0087] The method comprises identifying the set of impacted APIs based on the
20 received one or more component names that is based on the data reflecting the
relation between each of the component name from the list of component names and the list of APIs, as stored in the database. The list of component names comprises the one or more component names.
25 [0088] Continuing the above example, as the input received in the previous step
was the component name(s) such as “authentication module” and the set of impacted APIs are determined in this step will be API1 and API2 based on the data reflecting the relation between each of the component name from the list of
35

component names and the list of APIs as shown in Table 1 above. In another example, if the input received in the previous step is “customer maintenance”, the APIs such as create customer, update customer, and delete customer are considered as impacted APIs. 5
[0089] The identification unit [204] may further identify impacted operations and interfaces within such API and parameter level changes in the identified API.
[0090] At step [308], the method comprises identifying, by the identification unit
10 [204], a set of external systems associated with each of the impacted API from the
set of impacted APIs. The identified set of external systems is integrated with the one or more component names.
[0091] The method further comprises identifying the set of external systems
15 associated with each of the impacted API from the set of impacted APIs, is based
on the data reflecting the relation between each of the API from the list of APIs and the list of external systems, as stored in the database.
[0092] The identification unit [204] may also identify internal changes within the
20 impacted product, systems, and impacted components of offered release of new
feature. The goal of the identification of the set of external systems is to identify integration impact of the change.
[0093] Continuing the above example, as the set of impacted APIs determined in
25 the previous step was API1 and API2, the set of external systems determined in
this step will be system 1 (banking system) and system 2 (weather data provider server) based on the data reflecting the relation between each of the API from the list of APIs and the list of external systems as shown in Table 2 above.
36

[0094] In another example, impacted APIs such as create customer, update
customer, and delete customer are determined in the previous step and such
impacted APIs are associated with each of the systems such as CRM, Billing system,
5 and Middleware. Hence systems such as CRM, billing system, and middleware are
considered as impacted systems.
[0095] At step [310], the method comprises identifying, by the identification unit
[204], a set of products associated with each of the external system from the set
10 of external systems.
[0096] The method comprises identifying the set of products associated with each
of the external system from the set of external systems, is based on the data
reflecting the relation between each of the external system from the list of
15 external systems and the list of products, as stored in the database.
[0097] Continuing the above example, as the set of external systems determined in the previous step was System 1 (banking system) and System 2 (weather data provider server), the set of products determined in this step will be product 1
20 (mobile banking app) and product 2 (weather forecast mobile app) based on the
data reflecting the relation between each of the external system from the list of external systems and the list of products as shown in Table 3 above. In another example, systems determined in the previous step was as the CRM, billing system, and middleware and the set of products determined in this step include products
25 such as Broadband, Airfibre and MPLS. Hence these products are considered
impacted products.
37

[0098] At step [312], the method comprises identifying, by the identification unit [204], a set of journeys associated with each of the product from the set of products.
5 [0099] The method comprises identifying the set of journeys associated with each
of the product from the set of products, is based on the data reflecting the relation between the list of products and the list of journeys, as stored in the database.
[0100] Continuing the above example, as the set of products determined in the
10 previous step was product 1 (mobile banking app) and product 2 (weather forecast
mobile app), the set of journeys determined in this step will be journey 1 (e.g., checking account balance and transferring funds) and journey 2 (e.g., checking weather updates) based on the data reflecting the relation between the list of products and the list of journeys as shown in Table 4 above.
15
[0101] In another example, the set of products determined in the previous step was broadband, Airfiber, and MPLS and the set of journeys determined in this step includes provisioning journey, modification journey, and termination journey. Provisioning journey is a journey associated with the provisioning of a broadband
20 plan. Modification journey is a journey associated with modifying an Airfiber plan.
Termination journey is a journey associated with deletion of a customer/ plan that is associated with the MPLS product. Hence provisioning journey, modification journey, and termination journey are considered as associated (or impacted journeys) with products such as broadband, Airfiber, and MPLS.
25
[0102] At step [314], the method comprises identifying, by the identification unit [204], a set of regression test cases associated with the set of journeys.
38

[0103] In one implementation, the identifying the set of regression test cases associated with the set of journeys, is based on the data reflecting the relation between the list of journeys and the list of regression test cases, stored in the database. 5
[0104] It is to be noted that regression testing a type of testing in a software development cycle that runs after every change to ensure that the change introduces no unintended breaks.
10 [0105] Continuing the above example, as the set of journeys determined in the
previous step was journey 1 (e.g., checking account balance and transferring funds) and journey 2 (e.g., checking weather updates), the set of regression test cases determined in this step will be test case 1 and test case 2 based on the data reflecting the relation between the list of journeys and the list of regression test
15 cases as shown in Table 5 above.
[0106] In another example, as the set of journeys determined in the previous step
was provisioning journey, modification journey, and termination journey and the
test cases determined in this step are test cases 1, 2, 3 and 4. The test cases 1 and
20 4 are associated with the provisioning journey due to the provisioning of a
broadband plan. The test case 2 is associated with the modification journey due to modification in the broadband plan. The test case 3 is associated with the termination journey due to the termination of the customer services.
25 [0107] At step [316], the method comprises performing automatically, by a
processing unit [206], an execution of the identified set of regression test cases. Continuing the above example, as the set of regression test cases determined in
39

the previous step were test case 1 and test case 2, these test cases may be automatically executed by the processing unit [206].
[0108] In another example, since the test cases determined in the previous step
5 were test cases 1, 2, 3 and 4, these test cases are automatically executed in this
step.
[0109] The processing unit [206] triggers an event to DevOps (Developer and
operations) system to execute such identified regression test cases. This may
10 include sending a notification to the DevOps team to execute the set of regression
test cases identified in the previous step.
[0110] Thereafter, the method terminates at step [318].
15 [0111] FIG.4 illustrates an exemplary sequence flow diagram [400] indicating the
process for automated regression repository tool, in accordance with exemplary implementations of the present disclosure. Referring to FIG.4, the process starts at step 402, where a system [200] provides a release for feature validation. The release can be a single feature or a bundle of multiple features. At step 404, a
20 transceiver unit [202] of the system [200] can accept single or multiple component
names as input to this process. It is to be noted that names of components may be received as input from a design and deployment team of any particular application or system.
25 [0112] At step 406, based on the component name(s), one or more impacted
Application Programming Interfaces (APIs) get identified by an identification unit [204] of the system [200], where a given API can be consumed in multiple products, journeys and use cases. The impacted APIs can be found based on impacted operations and interfaces within an API and parameter-level changes.
40

[0113] Once the impacted API is identified, a set of consuming systems along with
the impacted products, journeys associated with impacted products and
regression test cases are identified at steps 408, and 410 respectively. At step 408,
5 the identification unit [204] of the system identifies external systems integrated
with impacted components of the offered release. At step 410, the identification unit [204] identifies the impacted services, impacted products and journeys associated with the products.
10 [0114] Thereafter, at step [412], a trigger is sent to the processing unit [206] of
the system [200] to execute the identified regression test cases. In an implementation, the identified regression test cases are executed automatically.
[0115] Yet another aspect of the present disclosure may relate to a non-transitory
15 computer readable storage medium storing instructions for implementing an
automated tool for regression testing, the instructions include executable code
which, when executed by one or more units of a system [200], causes: a
transceiver unit [202] of the system [200] to receive, one or more component
names, as a user input on a user interface, wherein, the one or more component
20 names are stored in a database; an identification unit [204] of the system [200],
connected at least to the transceiver unit [202], to: identify, a set of impacted
application programming interfaces (APIs) based on the received one or more
component names; identify, a set of impacted external systems associated with
each of the impacted API from the set of impacted APIs; identify, a set of products
25 associated with each of the external system from the set of external systems;
identify, a set of journeys associated with each of the product from the set of products; identify, a set of regression test cases associated with the set of journeys; and a processing unit [206] of the system, connected at least to the
41

identification unit [204], to perform automatically, an execution of the identified regression test cases.
[0116] As is evident from the above, the present disclosure provides a technically
5 advanced solution for automated regression repository tool. The present
disclosure identifies the exact impacted products, journeys and test cases, thereby reducing the overall regression test execution timeline and increasing test efficiency and resource utilization.
10 [0117] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is
15 to be understood that the foregoing descriptive matter to be implemented is
illustrative and non-limiting.
42

We Claim:
1. A method for implementing an automated tool for regression testing, the
method comprising:
- receiving, by a transceiver unit [202], one or more component names as a user input on a user interface, wherein, the one or more component names are stored in a database;
- identifying, by an identification unit [204], a set of impacted application programming interfaces (APIs) based on the received one or more component names;
- identifying, by the identification unit [204], a set of external systems associated with each of the impacted API from the set of impacted APIs;
- identifying, by the identification unit [204], a set of products associated with each of the external system from the set of external systems;
- identifying, by the identification unit [204], a set of journeys associated with each of the product from the set of products;
- identifying, by the identification unit [204], a set of regression test cases associated with the set of journeys; and
- performing automatically, by a processing unit [206], an execution of the identified set of regression test cases.

2. The method as claimed in claim 1, wherein, the identified set of external systems is integrated with the one or more component names.
3. The method as claimed in claim 1, wherein the database comprises:
- a list of component names, a list of application programming interfaces
(APIs), a list of external systems, a list of products, a list of journeys, a
list of regression test cases, a data reflecting a relation between each

of the component name from the list of component names and the list of APIs, a data reflecting a relation between each of the API from the list of APIs and the list of external systems, a data reflecting a relation between each of the external system from the list of external systems and the list of products, a data reflecting a relation between the list of products and the list of journeys, and a data reflecting a relation between the list of journeys and the list of regression test cases.
4. The method as claimed in claim 3, wherein the list of component names comprises the one or more component names.
5. The method as claimed in claim 3, wherein, the identfying the set of impacted APIs based on the received one or more component names is based on the data refectng the relaton between each of the component name from the list of component names and the list of APIs, as stored in the database.
6. The method as claimed in claim 3, wherein, the identfying the set of external systems associated with each of the impacted API from the set of impacted APIs, is based on the data refectng the relaton between each of the API from the list of APIs and the list of external systems, as stored in the database.
7. The method as claimed in claim 3, wherein, the identfying the set of products associated with each of the external system from the set of external systems, is based on the data refectng the relaton between each of the external system from the list of external systems and the list of products, as stored in the database.

8. The method as claimed in claim 3, wherein, the identfying the set of journeys associated with each of the product from the set of products, is based on the data refectng the relaton between the list of products and the list of journeys, as stored in the database.
9. The method as claimed in claim 3, wherein, the identfying the set of regression test cases associated with the set of journeys, is based on the data refectng the relaton between the list of journeys and the list of regression test cases, stored in the database.
10. A system [200] for implementing an automated tool for regression testing, the system [200] comprising:
- a transceiver unit [202] configured to:
o receive, one or more component names, as a user input on a user interface, wherein, the one or more component names are stored in a database;
- an identification unit [204], connected at least to the transceiver unit
[202], the identification unit [204] configured to:
o identify, a set of impacted application programming interfaces
(APIs) based on the received one or more component names; o identify, a set of impacted external systems associated with
each of the impacted API from the set of impacted APIs; o identify, a set of products associated with each of the external
system from the set of external systems; o identify, a set of journeys associated with each of the product
from the set of products; o identify, a set of regression test cases associated with the set of
journeys; and

- a processing unit [206], connected at least to the identification unit [204], the processing unit [206] configured to perform automatically, an execution of the identified regression test cases.
11. The system [200] as claimed in claim 10, wherein the identified set of external systems is integrated with the one or more components.
12. The system [200] as claimed in claim 10, wherein the database comprises:
a list of component names, a list of application programming interfaces (APIs), a list of external systems, a list of products, a list of journeys, a list of regression test cases, a data reflecting a relation between each of the component name from the list of component names and the list of APIs, a data reflecting a relation between each of the API from the list of APIs and the list of external systems, a data reflecting a relation between each of the external system from the list of external systems and the list of products, a data reflecting a relation between the list of products and the list of journeys, and a data reflecting a relation between the list of journeys and the list of regression test cases.
13. The system [200] as claimed in claim 12, wherein the list of component names comprises the one or more component names.
14. The system [200] as claimed in claim 12, wherein, the identfying the set of impacted APIs based on the received one or more component names is based on the data refectng the relaton between each of the component name from the list of component names and the list of APIs, as stored in the database.

15. The system [200] as claimed in claim 12, wherein, the identfying the set
of external systems associated with each of the impacted API from the
set of impacted APIs, is based on the data refectng the relaton between
each of the API from the list of APIs and the list of external systems, as
stored in the database.
16. The system [200] as claimed in claim 12, wherein, the identfying the set of products associated with each of the external system from the set of external systems, is based on the data refectng the relaton between each of the external system from the list of external systems and the list of products, as stored in the database.
17. The system [200] as claimed in claim 12, wherein, the identfying the set of journeys associated with each of the product from the set of products, is based on the data refectng the relaton between the list of products and the list of journeys, as stored in the database.
18. The system [200] as claimed in claim 12, wherein, the identfying the set of regression test cases associated with the set of journeys, is based on the data refectng the relaton between the list of journeys and the list of regression test cases, stored in the database.