The benefit of exploratory testing and ad hoc testing by tester’s experience is that crucial bugs are found quickly. Regression testing and test case prioritization are important processes of software testing when software functions have been changed. We propose a test path prioritization method to generate a sequence of test paths that would match the testers’ interests and focuses on the target area of interest or on the changed area. We generate test paths form the activity diagrams and survey the test path prioritization from testers. We define node and edge weight to the symbols of activity diagrams by applying Time management, Pareto, Buffett, Binary, and Bipolar method. Then we propose a test path score equation to prioritize test paths. We also propose evaluation methods i.e., the difference and the similarity of test path prioritization to testers’ interests. Our proposed method had the least average of the difference and the most average of the similarity compare with the tester’s prioritization of test paths. The Bipolar method was the most suitable for assigning weights to match test path rank by the tester. Our proposed method also has given the affected path by changing area higher priority than the other test path.

Effort reduction in software testing is important to reduce the total cost of the software development project. UML activity diagram is used by the tester for test path generation. It is hard to select the appropriate test path generation technique to diminish the effort of software testing. In the experiment, we compared the efficiency of 12 commonly-used test path generation techniques with both simple activity diagrams and the constructed complex activity diagrams. The experimental results summarized in four aspects. (1) The most appropriate test path generation technique for path testing generates the number of paths equivalent to the target number of all possible paths. (2) The suitable test path generation technique for the concurrency test scenario. (3) The techniques that can generate test paths covering basis path coverage in the case that testing all possible paths for the large or complex object-oriented method is laborious. (4) To compare the efficiency of test path generation algorithms, the percentage test path deviation to the target number of all possible paths is calculated for the constructed complex activity diagrams. We also recommended suitable test path generation methods for each manner of the UML activity diagram.Povzetek: Avtorji so analizirali uspešnost dvanajst metod za iskanje poti preverjanja programske opreme z enostavnimi in kompleksnimi diagrami aktivnosti.