Test Path Prioritization from UML Activity Diagram Using a Hybridized Approach

Introduction

Software testing (Kit, 1995; Mathur, 2008) is a critical segment of product development which realizes a high reliability product alongside controlling the quality framework. The principle objective of testing is to develop the trust of the end user in the accuracy of the system. Testing can be viewed as the procedure of distinguishing the contrast between the expected and actual results. It is found that software testing is a time consuming and costly errand. It devours right around half of the software framework resources. Exhaustive testing is unlikely to be carried out since there are no limits on how much we can test. Thus, to limit the process of testing, the concept of testing criteria was laid down. Satisfying the testing criteria puts an end to testing process. With the escalation in complexity and size of software systems, greater time and manpower were consumed for testing. Rich knowledge and experience in the domain of software testing served as a perquisite for software testers carrying out manual testing. Manual testing is so labor-intensive and error-prone that it becomes obligatory to automate the testing techniques. A varied number of testing techniques have been proposed in the literature. They are as follows.