A computer-implemented method of increasing software testing efficiency during regression testing, comprising: compiling, with an electronic processor, a list of relevant processes, wherein the list of relevant processes is defined by which processes (101A-101 E) call an artifact (102A-102G) that has been changed; assigning, with the electronic processor, a criticality attribute to each relevant process; classifying, with the electronic processor, a test effort required for each relevant process; determining dependencies between the relevant processes; specifying a global criticality level, the global criticality level specifying levels of ensured correctness for each relevant process according to the assigned criticality attribute, wherein the higher the level of ensured correctness is, the more the corresponding relevant process needs to be tested; determining, by a user specification, a minimum call rate for each changed artifact, wherein the minimum call rate is a minimum number of times each changed artifact is called by the processes that use it during a test process; compiling, with the electronic processor, a minimum test scope that satisfies the global criticality level, wherein said minimum test scope is based: - at least in part on the dependencies; and - at least in part on the minimum call rate for each changed artifact; wherein compiling the minimum test scope includes determining which processes or process steps need to be tested in order to ensure that the global criticality level is achieved; providing for review, via a user interface executed on the electronic processor, parameters related to the minimum test scope, the parameters comprising the test effort or the test time associated with the compiled minimum test scope; providing, via the user interface executed on the electronic processor, a set of re-planning tools configured to receive input modifying parameters, the input modifying parameters comprising the level of ensured correctness for the relevant processes, and recompiling the minimum test scope; and transferring the compiled minimum test scope to a test management tool. compiling, with an electronic processor, a list of relevant processes, wherein the list of relevant processes is defined by which processes (101A-101 E) call an artifact (102A-102G) that has been changed; assigning, with the electronic processor, a criticality attribute to each relevant process; classifying, with the electronic processor, a test effort required for each relevant process; determining dependencies between the relevant processes; specifying a global criticality level, the global criticality level specifying levels of ensured correctness for each relevant process according to the assigned criticality attribute, wherein the higher the level of ensured correctness is, the more the corresponding relevant process needs to be tested; determining, by a user specification, a minimum call rate for each changed artifact, wherein the minimum call rate is a minimum number of times each changed artifact is called by the processes that use it during a test process; compiling, with the electronic processor, a minimum test scope that satisfies the global criticality level, wherein said minimum test scope is based: - at least in part on the dependencies; and - at least in part on the minimum call rate for each changed artifact; - at least in part on the dependencies; and - at least in part on the minimum call rate for each changed artifact; wherein compiling the minimum test scope includes determining which processes or process steps need to be tested in order to ensure that the global criticality level is achieved; providing for review, via a user interface executed on the electronic processor, parameters related to the minimum test scope, the parameters comprising the test effort or the test time associated with the compiled minimum test scope; providing, via the user interface executed on the electronic processor, a set of re-planning tools configured to receive input modifying parameters, the input modifying parameters comprising the level of ensured correctness for the relevant processes, and recompiling the minimum test scope; and transferring the compiled minimum test scope to a test management tool.