Fault pr Fault prone components identification and optimal test case generation using ocl specificationne components identification and optimal test case generation using ocl specification

Abstract

The most important quality aspect of a software system is how well it fulfills the needs of its users or the requirements of its customers. The demand for complicated software has been expanding at an exponential rate in recent years, as has the number of components in a system. However, due to a lack of time, a scarcity of allied resources and the high cost of the testing period, extensive testing on every component of the software is not achievable. In practice, a small number of system components might cause numerous problems to be reported at later stages of software development, leading to a huge loss of money, human effort, and quality for the system. Therefore, it is vital to devote a significant amount of time and effort to identifying and testing those components that are most prone to failure at the earliest. newlineSpecification-based testing is one of the most well-known software engineering principles. Apart from the application of formal specifications in precise and abstract system representation, this research effort has demonstrated additional benefits such as systematically prioritizing tests and automatically deriving test input data. To address this issue, the aim of this research is to examine the overlap between fault-prone component-based testing and specification-based testing, as well as the benefits that these two disciplines potentially provide. This can be achieved by initiating fault-proneness-based testing at the specification level so that errors can be identified and fixed early in the Software Development Life Cycle (SDLC). The reason behind is that errors discovered later in the software development life cycle cost more to correct than those discovered earlier. newlineThe primary goal of fault-proneness prediction is to identify fault-prone components as early as possible in the SDLC in order to reduce development effort in terms of design, coding, testing, inspection, and debugging, among other aspects. newline