Strategy for continuous testing in iDevOps

Zimmerer, Peter

doi:10.1145/3183440.3183465

Cited by 10 publications

(4 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The test design techniques, analysis tools, and test frameworks that works parallel with tests are good examples of test analytics in DevOps. 10. Microservices and containers: This approach aims to produce well bounded and attractive architecture of microservices that provides the facility to build and deploy as an independent unit.…”

Section: Test Accelerationmentioning

confidence: 99%

“…According to him, the three key aspects on which DevOps testing depends are organization scope, existing test approaches, and team coordination. Similarly, Zimmere 10 characterized the continuous testing in DevOps (iDevOps) into two phases: (i) strategies for test automation and (ii) continuous testing from start till end. Cruzes et al 11 discussed five major concerns of testers while working in DevOps environment, that is, coordination, automation, role and responsibilities, monitoring, test types, and infrastructures.…”

Section: Study Background and Motivationmentioning

confidence: 99%

See 1 more Smart Citation

Selection of DevOps best test practices: A hybrid approach using ISM and fuzzy TOPSIS analysis

Rafi

Akbar

Mahmood

et al. 2022

J Software Evolu Process

View full text Add to dashboard Cite

Testing is a complex phase in DevOps process due to need of an automated process that provides feedback at different strategies of continuous development and operations pipeline. Software organization face several challenges during the testing phase due to lack of understanding on testing best practices for the DevOps paradigm. The objective of this study is to prioritize DevOps best testing practices, which can facilitate the selection of testing practices during DevOps process. To perform this research, we have extended the work done by Hornbeek, using the 15 DevOps testing practices discussed in his study. First, we categorize the test practices against culture, automation, lean, measurement, and sharing (CALMS) pillars of DevOps adoption principles. Next, a questionnaire‐based survey was conducted to collect feedback from industry practitioners on the DevOps test practices and their categorization against CALMS criteria. Finally, we applied Interpretive Structure Modeling (ISM) to find the interrelationship between CALMS criteria, and fuzzy TOPSIS was used to prioritize the DevOps test practices that will assist practitioners to better manage the testing activities during DevOps process.

show abstract

Section: Test Accelerationmentioning

confidence: 99%

Section: Study Background and Motivationmentioning

confidence: 99%

Selection of DevOps best test practices: A hybrid approach using ISM and fuzzy TOPSIS analysis

Rafi

Akbar

Mahmood

et al. 2022

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…− Some continuous approaches were excluded from the list of studies. As an example, for [17], the focus has been primarily on development, whereas [146] focused on continuous testing and their relevance to the inclusion criteria is weak. Nevertheless, these types of approaches have motivated us to review and introduce continuous software architecture evaluation to the software architecture community.…”

Section: Category Representative Contributionsmentioning

confidence: 99%

Evaluation of Software Architectures under Uncertainty

Sobhy

Bahsoon

Minku

et al. 2021

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Context: Evaluating software architectures in uncertain environments raises new challenges, which require continuous approaches. We define continuous evaluation as multiple evaluations of the software architecture that begins at the early stages of the development and is periodically and repeatedly performed throughout the lifetime of the software system. Numerous approaches have been developed for continuous evaluation; to handle dynamics and uncertainties at run-time, over the past years, these approaches are still very few, limited, and lack maturity. Objective: This review surveys efforts on architecture evaluation and provides a unified terminology and perspective on the subject. Method: We conducted a systematic literature review to identify and analyse architecture evaluation approaches for uncertainty including continuous and non-continuous, covering work published between 1990–2020. We examined each approach and provided a classification framework for this field. We present an analysis of the results and provide insights regarding open challenges. Major results and conclusions: The survey reveals that most of the existing architecture evaluation approaches typically lack an explicit linkage between design-time and run-time. Additionally, there is a general lack of systematic approaches on how continuous architecture evaluation can be realised or conducted. To remedy this lack, we present a set of necessary requirements for continuous evaluation and describe some examples.

show abstract

“…On the other hand, in the academic field, various literature review studies have been carried out where: (i) it is pointed out that the concept of DevOps is not completely defined [20]; (ii) the definitions, practices and benefits of DevOps are categorized [21]; (iii) the relevant aspects are determined [22], [23]; (iv) the factors that interrupt its adoption are identified [24]; (v) the influence on the product is presented [7]; and, (vi) in [2], a strong need to respond quickly to the market is reported and that DevOps helps to address this problem. Since software testing is a critical factor for the adoption of DevOps [25], it should be reviewed how it is being applied in the reported cases. For this reason, this paper consolidates and classifies the literature on applied software testing in a DevOps context.…”

Section: Introductionmentioning

confidence: 99%

https://ispranproceedings.elpub.ru/jour/article/view/1612

Pando¹,

Dávila²

2023

Proceedings of ISP RAS

View full text Add to dashboard Cite

DevOps is a philosophy and framework that allows software development and operations teams to work in a coordinated manner, with the purpose of developing and releasing software quickly and cheaply. However, the effectiveness and benefits of DevOps depend on several factors, as reported in the literature. In particular, several studies have been published on software test automation, which is a cornerstone for the continuous integration phase in DevOps, which needs to be identified and classified. This study consolidates and classifies the existing literature on automated tests in the DevOps context. For the study, a systematic mapping study was performed to identify and classify papers on automated testing in DevOps based on 8 research questions. In the query of 6 relevant databases, 3,312 were obtained; and then, after the selection process, 299 papers were selected as primary studies. Researchers maintain a continuing and growing interest in software testing in the DevOps context. Most of the research (71.2%) is carried out in the industry and is done on web applications and SOA. The most reported types of tests are unit and integration tests.

show abstract

Strategy for continuous testing in iDevOps

Cited by 10 publications

References 1 publication

Selection of DevOps best test practices: A hybrid approach using ISM and fuzzy TOPSIS analysis

Selection of DevOps best test practices: A hybrid approach using ISM and fuzzy TOPSIS analysis

Evaluation of Software Architectures under Uncertainty

https://ispranproceedings.elpub.ru/jour/article/view/1612

Contact Info

Product

Resources

About