Metamorphic relation prioritization for effective regression testing. (17th February 2022)

• Record Type: Journal Article
• Authors: Srinivasan, Madhusudan; Kanewala, Upulee
• Is Part Of: Software testing, verification & reliability. Volume 32:Number 3(2022)
• Page Start: n/a
• Page End: n/a
• Publication Date: 2022-02-17
• Subjects: metamorphic testing -- metamorphic relations -- MR prioritization; Computer software -- Testing -- Periodicals; Computer software -- Verification -- Periodicals; Computer software -- Reliability -- Periodicals; 005.14
• DOI: 10.1002/stvr.1807
• Languages: English
• ISSNs: 0960-0833

Abstract

Summary: Metamorphic testing (MT) is widely used for testing programs that face the oracle problem. It uses a set of metamorphic relations (MRs), which are relations among multiple inputs and their corresponding outputs to determine whether the program under test is faulty. Typically, MRs vary in their ability to detect faults in the program under test, and some MRs tend to detect the same set of faults. In this paper, we propose approaches to prioritize MRs to improve the efficiency and effectiveness of MT for regression testing. We present two MR prioritization approaches: (i) fault‐based and (ii) coverage‐based. To evaluate these MR prioritization approaches, we conduct experiments on three complex open‐source software systems. Our results show that the MR prioritization approaches developed by us significantly outperform the current practice of executing the source and follow‐up test cases of the MRs in an ad‐hoc manner in terms of fault detection effectiveness. Further, fault‐based MR prioritization leads to reducing the number of source and follow‐up test cases that needs to be executed as well as reducing the average time taken to detect a fault, which would result in saving time and cost during the testing process. Abstract : We present two MR prioritization approaches: (1) fault‐based and (2) coverage‐based. Our results show that the MR prioritization approaches developed by us significantly outperform the current practice of executing the MRs randomly. Further, fault‐based MR prioritization leads to reducing the number of source and follow‐up test cases that needs to be executed as well as reducing the average time taken to detect a fault, which would result in saving time and cost during the testing process.