When and what to automate in software testing? A multi-vocal literature review

Garousi, Vahid; Mäntylä, Martti

doi:10.1016/j.infsof.2016.04.015

Cited by 141 publications

(122 citation statements)

References 30 publications

Supporting

Mentioning

120

Contrasting

Unclassified

Order By: Relevance

“…Based on the SM and SLR guidelines [2,4,5], to find relevant studies, we searched the following three major online search academic article search engines: (1) IEEE Xplore, (2) ACM Digital Library, and (3) Google Scholar. In addition to the formal published literature, the authors actually wanted to include the grey literature too, and to conduct a multi-vocal literature review (MLR), e.g., [14,15]. But they were not able to find a minimum number of reasonable blog entries, or other grey sources on this subject.…”

Section: Study Identificationmentioning

confidence: 99%

Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review

Garousi

Petersen

Özkan

2016

Information and Software Technology

Self Cite

192

182

View full text Add to dashboard Cite

Section: Study Identificationmentioning

confidence: 99%

Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review

Garousi

Petersen

Özkan

2016

Information and Software Technology

Self Cite

192

182

View full text Add to dashboard Cite

“…We continued with further pages of results only if needed, e.g., when at least one result in the n th page was still relevant (for example, if at least one paper focused on software testing education). Similar heuristics have been reported in several other existing review studies, guidelines and experience papers [66][67][68][69][70]. At the end of our initial search and title filtering, our candidate pool had 307 papers (as shown in our SLM process in Figure 3).…”

Section: The Search Process: Selecting the Source Engines And Search mentioning

confidence: 97%

Software-testing education: A systematic literature mapping

Garousi

Rainer

Lauvås

et al. 2020

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

Context: With the rising complexity and scale of software systems, there is an ever-increasing demand for sophisticated and cost-effective software testing. To meet such a demand, there is a need for a highly-skilled software testing work-force (test engineers) in the industry. To address that need, many university educators worldwide have included software-testing education in their software engineering (SE) or computer science (CS) programs. Many papers have been published in the last three decades (as early as 1992) to share experience from such undertakings.Objective: Our objective in this paper is to summarize the body of experience and knowledge in the area of software-testing education to benefit the readers (both educators and researchers) in designing and delivering software testing courses in university settings, and to also conduct further education research in this area. Method: To address the above need, we conducted a systematic literature mapping (SLM) to synthesize what the community of educators have published on this topic. After compiling a candidate pool of 307 papers, and applying a set of inclusion/exclusion criteria, our final pool included 204 papers published between 1992 and 2019.Results: The topic of software-testing education is becoming more active, as we can see by the increasing number of papers. Many pedagogical approaches (how to best teach testing), course-ware, and specific tools for testing education have been proposed. Many challenges in testing education and insights on how to overcome those challenges have been proposed.Conclusion: This paper provides educators and researchers with a classification of existing studies within software-testing education. We further synthesize challenges and insights reported when teaching software testing. The paper also provides a reference ("index") to the vast body of knowledge and experience on teaching software testing. Our mapping study aims to help educators and researchers to identify the best practices in this area to effectively plan and deliver their software testing courses, or to conduct further education-research in this important area.

show abstract

“…SLR cannot always provide an established discipline of knowledge as it ignores a large amount of information produced by software engineering practitioners [34,35,37 ]. Hence, MLR is attracting more attention to SE [34,38]. We believe that conducting MLR in the area of security orchestration will be more useful compared to SLR as there is a large body of non-peer reviewed literature reported by practitioners.…”

Section: Fig 1 Overview Of An Organization Decision Against Alerts Wmentioning

confidence: 99%

A Multi-Vocal Review of Security Orchestration

2019

View full text Add to dashboard Cite

Organizations use diverse types of security solutions to prevent cyber-attacks. Multiple vendors provide security solutions developed using heterogeneous technologies and paradigms. Hence, it is a challenging rather impossible to easily make security solutions to work an integrated fashion. Security orchestration aims at smoothly integrating multivendor security tools that can effectively and efficiently interoperate to support security staff of a Security Operation Centre (SOC). Given the increasing role and importance of security orchestration, there has been an increasing amount of literature on different aspects of security orchestration solutions. However, there has been no effort to systematically review and analyze the reported solutions. We report a Multivocal Literature Review that has systematically selected and reviewed both academic and grey (blogs, web pages, white papers) literature on different aspects of security orchestration published from January 2007 until July 2017. The review has enabled us to provide a working definition of security orchestration and classify the main functionalities of security orchestration into three main areas -unification, orchestration, and automation. We have also identified the core components of a security orchestration platform and categorized the drivers of security orchestration based on technical and socio-technical aspects. We also provide a taxonomy of security orchestration based on the execution environment, automation strategy, deployment type, mode of task and resource type. This review has helped us to reveal several areas of further research and development in security orchestration. CCS ConceptsGeneral and reference → Survey and overviews; Security and privacy; Software engineering Additional Key Words and PhraseSecurity orchestration, security automation, multivocal literature review, intelligent security assistant.

show abstract

When and what to automate in software testing? A multi-vocal literature review

Cited by 141 publications

References 30 publications

Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review

Challenges and best practices in industry-academia collaborations in software engineering: A systematic literature review

Software-testing education: A systematic literature mapping

A Multi-Vocal Review of Security Orchestration

Contact Info

Product

Resources

About