Anti-pattern Mutations and Fault-proneness

2014 ◽  
Author(s):  
Fehmi Jaafar ◽  
Foutse Khomh ◽  
Yann-Gael Gueheneuc ◽  
Mohammad Zulkernine
Keyword(s):  
Fault Proneness

scholarly journals Are Multi-Language Design Smells Fault-Prone? An Empirical Study

2021 ◽  
Vol 30 (3) ◽  
pp. 1-56
Author(s):  
Mouna Abidi ◽  
Md Saidur Rahman ◽  
Moses Openja ◽  
Foutse Khomh
Keyword(s):  
Programming Languages ◽  
Language Design ◽  
Functional Requirements ◽  
Code Smells ◽  
Design And Implementation ◽  
Design Smells ◽  
The Cost ◽  
The Impact ◽  
Fault Proneness

Nowadays, modern applications are developed using components written in different programming languages and technologies. The cost benefits of reuse and the advantages of each programming language are two main incentives behind the proliferation of such systems. However, as the number of languages increases, so do the challenges related to the development and maintenance of these systems. In such situations, developers may introduce design smells (i.e., anti-patterns and code smells) which are symptoms of poor design and implementation choices. Design smells are defined as poor design and coding choices that can negatively impact the quality of a software program despite satisfying functional requirements. Studies on mono-language systems suggest that the presence of design smells may indicate a higher risk of future bugs and affects code comprehension, thus making systems harder to maintain. However, the impact of multi-language design smells on software quality such as fault-proneness is yet to be investigated. In this article, we present an approach to detect multi-language design smells in the context of JNI systems. We then investigate the prevalence of those design smells and their impacts on fault-proneness. Specifically, we detect 15 design smells in 98 releases of 9 open-source JNI projects. Our results show that the design smells are prevalent in the selected projects and persist throughout the releases of the systems. We observe that, in the analyzed systems, 33.95% of the files involving communications between Java and C/C++ contain occurrences of multi-language design smells. Some kinds of smells are more prevalent than others, e.g., Unused Parameters , Too Much Scattering , and Unused Method Declaration . Our results suggest that files with multi-language design smells can often be more associated with bugs than files without these smells, and that specific smells are more correlated to fault-proneness than others. From analyzing fault-inducing commit messages, we also extracted activities that are more likely to introduce bugs in smelly files. We believe that our findings are important for practitioners as it can help them prioritize design smells during the maintenance of multi-language systems.

Optimized Test Case Generation for Object Oriented Systems Using Weka Open Source Software

2021 ◽  
pp. 596-618
Author(s):  
Rajvir Singh ◽  
Anita Singhrova ◽  
Rajesh Bhatia
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Effective Means ◽  
Object Oriented ◽  
Test Case Generation ◽  
Test Case ◽  
Test Cases ◽  
Time Saving ◽  
Class Level ◽  
Fault Proneness

Detection of fault proneness classes helps software testers to generate effective class level test cases. In this article, a novel technique is presented for an optimized test case generation for ant-1.7 open source software. Class level object oriented (OO) metrics are considered as effective means to find fault proneness classes. The open source software ant-1.7 is considered for the evaluation of proposed techniques as a case study. The proposed mathematical model is the first of its kind generated using Weka open source software to select effective OO metrics. Effective and ineffective OO metrics are identified using feature selection techniques for generating test cases to cover fault proneness classes. In this methodology, only effective metrics are considered for assigning weights to test paths. The results indicate that the proposed methodology is effective and efficient as the average fault exposition potential of generated test cases is 90.16% and test cases execution time saving is 45.11%.

Sign in / Sign up

Export Citation Format

Share Document