Abstract
The guarantee of software quality is very important. Thus, before a software is released to the end users, the flaws in the software should be detected by using high quality test cases. Currently, gauging the quality of test cases is carried out without any particular model and the criteria for good test cases is still unclear. Therefore, this study studies the literature using Systematic Literature Review (SLR) technique to identify the criteria of good test cases. The SLR considered papers between 2010 and 2018 in IEEE Xplore, ACM Digital Library, and Science Direct databases. Through the searching, it was found 310 papers are related. After filtering using exclusion and insertion criteria, 14 papers were considered for analysis. As a result, the test managed to identify 30 quality factors from the selected articles. These quality factors were additionally inspected, arranged and finished to be incorporated as the quality factors of test cases evaluation metrics.
Highlights
The most important phase for detecting software defects in producing high-quality software is software testing phase [1]
This study studies the literature using Systematic Literature Review (SLR) technique to identify the criteria of good test cases
Testers could focus on two things in improving the quality of software testing and productivity; identifying the most effective quality metrics and measuring the test case quality [2]
Summary
The most important phase for detecting software defects in producing high-quality software is software testing phase [1]. Various reasons have been identified leading to software failures, including misled understanding (among team members) upon different contexts, immature experience in designing test case, and immature understanding [8]–[10]. Testers could focus on two things in improving the quality of software testing and productivity; identifying the most effective quality metrics and measuring the test case quality [2] Both the quality and testing metrics are important [12]. It aims to gather maximum number of flaws [5]–[7], [14]. In conjunction to that, [2] recommends that designers and developers should plan for early detection and prevention from flaws It could help reducing the possibilities of flaws in the developed software. It has to be effectively designed [17]
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Turkish Journal of Computer and Mathematics Education (TURCOMAT)
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
