System and method for implementing a test optimization module

Abstract

Various methods, apparatuses / systems, and media for implementing a test optimization module are provided. A processor utilizes a static analysis technique which analyzes an application's byte code to determine what files and line-numbers have been changed in a source code based on comparing successive versions of the application. The processor creates a change dependency graph (CDG) based on a change scope and analyzed bytecode, traverses the CDG to generate a list of test cases among a plurality of test cases, accessed from a test repository, that are directly and / or indirectly related to the modification to the source code, and automatically executes only the test cases selected from the generated list to test the latest version of the application.

Description

TECHNICAL FIELD[0001]This disclosure generally relates to software testing, and, more particularly, to methods and apparatuses for implementing a test optimization module for drastically reducing test execution time when a modification is made to a source code.BACKGROUND[0002]As software application becomes increasingly more complex, testing such software application also becomes more complex as a large number of unique combinations of paths and modules may be tested for each program. Conventional tools exist for software application testing. However, as the number of tests covering an application code increases the time to verify the correctness of the code increases as well because the conventional tools execute the entire suite of tests every time a change is made (even for the smallest change) to a source code of the software application, thereby significantly increasing software application testing time, leading to a delay in getting useful feedback for developers, and wasting ...

AI Technical Summary

Benefits of technology

[0003]The present disclosure, through one or more of its various aspects, embodiments, and / or specific features or sub-components, provides, among other features, various systems, servers, devices, methods, media, programs, and platforms for implementing a test optimization module which may implement a static analysis technique by, instead of executing ail tests each time there is a code change, determining a code slice affected by the change and executing only the tests that are directly and / or indirectly related to the change, thereby significantly reducing software testing time, reducing utilization of computer resources and reducing utilization of memory spaces thereby maintaining optimum memory spaces for other computer processing algorithms, but the disclosure is not limited thereto. The various aspects, embodiments, features, and / or sub-components may also provide optimized processes of implementing a test optimization module in which a stateless engine (i.e., processor or a CPU) implemented therein may not need persistent stores, in-memory caches, and extensive synchronizations, thereby reducing utilization of computer resources and reducing utilization of memory spaces so that sufficient numbers of memory spaces may be available for other computer processing algorithms, but the disclosure is not limited thereto.

[0017]According to another aspect of the present disclosure, when executed, the instructions may further cause the processor to perform the following: loading test cases from folders with .java notation from the repository; statically analyzing the byte code for each main and test class prior to executing the second version of the application; generating a structure of the change in a form of connected nodes that represent the changes direct and transient dependencies; and creating links between nodes that are affected by the modification to the source code.

Problems solved by technology

As software application becomes increasingly more complex, testing such software application also becomes more complex as a large number of unique combinations of paths and modules may be tested for each program.

However, as the number of tests covering an application code increases the time to verify the correctness of the code increases as well because the conventional tools execute the entire suite of tests every time a change is made (even for the smallest change) to a source code of the software application, thereby significantly increasing software application testing time, leading to a delay in getting useful feedback for developers, and wasting computer resources on build servers.

Conventional system, that does not implement a TOM of the instant disclosure, may not be able to execute testing of a software application in an efficient manner.

Conventional tools may execute the entire suite of tests every time a change is made (even for the smallest change) to a source code of the software application, thereby significantly increasing software application testing time, leading to a delay in getting useful feedback for developers, and wasting computer resources on build servers.

According to exemplary embodiments, a change risk may refer to the probability that a change to a software may lead to a loss caused by the software failure.

Additionally, the illustrations are merely representational and may not be drawn to scale.

Images