Targeted Testing for Modular Software Applications

A non-transitory computer-readable medium having stored thereon program instructions that, when executed by at least one processor, cause a computing platform to:

• identify, for a software application comprising source code files arranged into a plurality of modules, a set of source code files that have changed since a prior reference time;
• based on an evaluation of the identified set of source code files, make a determination to initiate a targeted test cycle involving execution of less than a full group of module-level tests specified within a predefined test plan for the software application rather than a full test cycle involving execution of the full group of module-level tests specified within the predefined test plan for the software application;
• and
• in response to the determination to initiate the targeted test cycle:
• (i) identify a targeted group of module-level tests to be executed during the targeted test cycle by, for each of at least a subset of the identified set of the source code files, (a) identifying a module to which the source code file belongs, (b) using a module-level test map for the software application to identify a sub-group of one or more module-level tests that correspond to the identified module, and (c) adding the identified sub-group of one or more module-level tests to the targeted group of module-level tests;
• and
• (ii) execute the targeted group of module-level tests.

A method carried out by a computing platform, the method comprising:

• identifying, for a software application comprising source code files arranged into a plurality of modules, a set of source code files that have changed since a prior reference time;
• based on an evaluation of the identified set of source code files, making a determination to initiate a targeted test cycle involving execution of less than a full group of module-level tests specified within a predefined test plan for the software application rather than a full test cycle involving execution of the full group of module-level tests specified within the predefined test plan for the software application;
• and
• in response to the determination to initiate the targeted test cycle:
• (i) identifying a targeted group of module-level tests to be executed during the targeted test cycle by, for each of at least a subset of the identified set of the source code files, (a) identifying a module to which the source code file belongs, (b) using a module-level test map for the software application to identify a sub-group of one or more module-level tests that correspond to the identified module, and (c) adding the identified sub-group of one or more module-level tests to the targeted group of module-level tests;
• and
• (ii) executing the targeted group of module-level tests.