SCUTMA: Selecting Components for Unit Testing in Mobile Applications

Context The source code of a mobile application has several components (i.e., code units) and they have a cost (e.g., test creation and execution) and benefit (e.g., find bug) value for performing unit testing. Problem Choosing in which components unit tests should be done, in order to increase the benefit (effectiveness) and decrease the cost of this activity. Proposal This study presents an approach that supports the selection of components for unit test creation in Android mobile applications. The SCUTMA approach allows the selection of components with respect to the following criteria, which can be combined: Cost of future maintenance, propensity to defects, frequency of call, risk of failure, market vulnerability and business value. Results Two empirical studies were performed to evaluate SCUTMA. The first study aimed at analyzing the correlation between the metrics that represent the criteria described above, where the result showed the possibility of using the metrics Cost of Future Maintenance (CFM), Code Smell (CS), Frequency of Calls (FC), Fault Risk (FR), Market Vulnerability (MV) and Business Value (BV) combined in a solution for component selection. The second study aimed to evaluate the effectiveness of using the SCUTMA approach. The result indicates that SCUTMA selected more components with error (58.33%) than the selection performed by specialists (40%). Conclusions The SCUTMA approach is effective in selecting components for creating unit tests in Android mobile applications.