An experimental evaluation of data flow and mutation testing
Software—Practice & Experience
Empirical Studies of a Safe Regression Test Selection Technique
IEEE Transactions on Software Engineering
A comparative study of coarse- and fine-grained safe regression test-selection techniques
ACM Transactions on Software Engineering and Methodology (TOSEM)
An empirical study of regression test selection techniques
ACM Transactions on Software Engineering and Methodology (TOSEM)
Test Case Prioritization: A Family of Empirical Studies
IEEE Transactions on Software Engineering
A Critical Analysis of Empirical Research in Software Testing
ESEM '07 Proceedings of the First International Symposium on Empirical Software Engineering and Measurement
An evaluation of quality checklist proposals: a participant-observer case study
EASE'09 Proceedings of the 13th international conference on Evaluation and Assessment in Software Engineering
An experimental evaluation of weak-branch criterion for class testing
Journal of Systems and Software
Hi-index | 0.00 |
Abstract Background: One aspect of undertaking a systematic literature review is to perform a quality evaluation of primary studies. Most quality checklists adopted from medicine, psychology and social studies assume that the experimental unit in an experiment is a human being. However, in empirical studies in software engineering the experimental unit may be a technology, an application or an algorithm. Aim: This paper presents a checklist we are developing to evaluate the quality of empirical technology-centred testing studies. Discussion points: The checklist was developed by considering entities used in technology-centred testing studies and the validation problems associated with them. The planned validation process includes face validation, usability and reliability assessment and external validation. As yet the external validation has not been performed. Conclusions: The checklists appear to be usable and after some experience applying them they appear to give consistent results. However, their validation is as yet incomplete. The method of developing and evaluating the checklist may be of use to other researchers requiring a means of assessing the quality of technology-centred software engineering studies.