Advanced Techniques in End-to-End Testing of Core Banking Solutions

Abstract

There has always been difficulty with integration testing, particularly when the system being tested is big and includes plenty of interfaces and subsystems. A strategy to designing End-to-End (E2E) integration testing, which includes tool support, test case creation, and test scenario specification, is presented in this work. For a lot of individuals these days, banking is essentially about using technology to do their financial chores. While many tasks still need a visit to a bank office, supporting mobile usage is quickly becoming the core goal of many bank initiatives. Large quantities of activity must be supported by the fundamental banking systems that handle financial transactions, and they must continue to be highly accessible. Many applications in the fields of medicine, civil engineering, marine engineering, military, and household use have resulted from this growth. While the demands and difficulties in each of these fields vary, data security is a common factor. In this paper, we share our experiences in modernizing and transforming banks and provide an overview of the approaches that will be used to implement these significant initiatives. From the perspective of the end user, test scenarios are given as thin threads, each of which represents a single function. It is possible to arrange thin threads in a hierarchical tree structure, where each branch represents a group of connected capabilities that are represented by a set of linked thin threads. Test engineers may do additional related jobs like risk analysis and assignment, regression testing, and ripple impact analysis, among others, by using thin-thread trees to construct test cases in a methodical manner. For the J2EE platform, a prototype tool has been created to facilitate E2E testing in a distributed setting.