Abstract: A method for facilitating the management of a test process is proposed. For this purpose, the different test scenarios included in the process and their execution dependencies are represented by means of a customized UML activity diagram (300a). An execution weight is also associated with each test scenario (for example, defined by the man-hours required for its execution). In this way, it is possible to identify critical test scenarios (315g), which may impair the execution of the whole test process when they fail (because many other test scenarios depend on their successful completion). The order of execution of the test scenarios is then arranged into a test plan, so as to minimize the time required to reach the critical test scenarios. Preferably, the same process is repeated whenever any runtime condition changes (such when a test scenario fails).

Abstract: A method for facilitating the management of a test process is proposed. For this purpose, the different test scenarios included in the process and their execution dependencies are represented by means of a customized UML activity diagram (300a). An execution weight is also associated with each test scenario (for example, defined by the man-hours required for its execution). In this way, it is possible to identify critical test scenarios (315g), which may impair the execution of the whole test process when they fail (because many other test scenarios depend on their successful completion). The order of execution of the test scenarios is then arranged into a test plan, so as to minimize the time required to reach the critical test scenarios. Preferably, the same process is repeated whenever any runtime condition changes (such when a test scenario fails).