Abstract: A system and a method for creating a defect identified during a test case run. A bug is detected during an execution of the test case on a functionality of a software. The bug is detected by comparing an actual output of the functionality with an expected output of the functionality. A setup, indicating actions performed on the software, associated with the bug is identified. Further, a video snippet is generated from a video recording of the test case being executed. The video snippet depicts an execution of the bug caused due to the setup. Furthermore, the setup is analysed using AI and ML techniques to determine an exact location of the bug. Further, a screen, from the video snippet, indicating the exact location of the bug is automatically highlighted. In addition, a defect comprising a recommendation to resolve the bug is created.

Abstract: Disclosed is a system and method for testing an application using multiple software test case execution channels is disclosed. The system may be configured to receive one or more test cases for testing of the application. The system may further be configured identify a primary test case execution channel and a secondary test case execution channel, corresponding to each of the one or more test cases, from a set of test case execution channel based on one or more classification parameters. The system may further be configured execute the one or more test cases using one of the primary test case execution channel and the secondary test case execution channel for testing the application. In one embodiment, the secondary test case execution channel is used on failure of the primary test case execution channel.

Abstract: Disclosed is a system and method for multi-channel testing of a software application is disclosed. The system may generate a set of test case definitions for testing a software application. The system may further allocate a sub-set of test case definitions, from the set of test cases definitions, to each test execution channel from the set of test execution channels based on a set of execution parameters specified by a user and the primary execution channel as well as the secondary execution channel associated with each test case definition. Furthermore, using the test case definitions associated with each test case execution channel, the system may enable testing of the software application at respective test execution channels and accordingly report the test execution results to the user.

Abstract: Disclosed is a system and method for real-time identification of anomalous behavior in a software program. The system is configured to generate a set of signatures files corresponding to a set of test cases. In one embodiment, each signature file is configured to maintain trace data generated after running the one or more test cases on the software program in a staging environment. Further, the system may capture real-time trace data from the software program, wherein the software program is deployed in a production environment. Further, the system may analyze the real-time trace data to identify a subset of signature files, from the set of signature files, applicable to the real-time trace data. Further, the system may compare the real-time trace data with the sub set of signature files to identify anomalous behavior in the software program.

Abstract: Disclosed is a system for determining one or more lines of code uniquely executed corresponding to a plurality of test cases executed on a computer program of an IT enabled application. The system creates a plurality of test cases (either manually or automatically). The system further enables a test case execution tool and a code coverage tool. The test case execution tool executes each of the plurality of test cases on the plurality of lines of code. On the other hand, the code coverage tool monitors the one or more lines of code, of the plurality of lines of code, executed for each test case. Subsequently, the system further determines Test Case To Code Mapping (TCTCM) indicating a subset, of the plurality of lines of code, executed at least once by the test case execution tool upon execution of one or more test cases of the plurality of test cases.