The Factors Driving Testing in Devops Setting- a Systematic Literature Survey

The Factors Driving Testing in Devops Setting- a Systematic Literature Survey

ISSN (Print) : 0974-6846 Indian Journal of Science and Technology, Vol 9(48), DOI: 10.17485/ijst/2016/v9i48/103784, December 2016 ISSN (Online) : 0974-5645 The Factors Driving Testing in DevOps Setting- A Systematic Literature Survey Jayasri Angara1*, Srinivas Prasad2 and Gutta Sridevi1 1K. L. University, Vijayawada - 522502, Andhra Pradesh, India; [email protected], [email protected] 2GMR Institution of Technology (A), Rajam - 532127, Andhra Pradesh, India; [email protected] Abstract Objectives: Software testing is no more “Essential” requirement but it is “Critical” for the software application or product survival. It has become mental discipline and the tone of an organization mindset especially in the context of emerging DevOps practice. A few limitations of agile methodology from operational and business readiness perspective are addressed in DevOps. DevOps got emerged out of continuous software delivery which captures the market opportunities and reduces identifythe feedback key technical, time. However, cultural the and new managerial DevOps processesfactors of aretesting influencing in DevOps profoundly setting. Methods/Statistical on QA and Testing functions. Analysis : TheWe conductedpresent study extensive is to understand literature surveydifferent on academicmotivational and factors industry driving reports testing in the in contextDevOps ofEnvironment DevOps testing. and attemptsFinally we to screened 29 most relevant articles out of 295 found among 5 major journal databases. Further we extended manual survey including whitepapers and industry reports. Findings: It is evident that most of the articles connected to DevOps testing this domain. We observed that DevOps in testing is closely associated with automation of test cases. In its advanced stage, got published after year 2011 and surged after 2014. This phenomenon shows the nascence of the research progress in it is attributed to auto generation of test cases through model driven frameworks. This has been stressed in more than 50% articles.of review DevOps articles. demands More than alternative 50% of articles metrics connected for better tocollaboration cloud, virtualization, and communication simulation betweentechniques various of DevOps stakeholders Testing. The factors like agility, scale, metric driven process, reduction of complexity and cost appeared in more than 16 review most of the review articles. Application/Improvements: of the system. DevOps testing is face of organization culture and human resource mindset. This has been stressed in multiple synonyms but we de-risked this threat by manuallyThis verifying research each is and constrained every result. from Further couple we of extendedbiases (authority manual surveyand publication). using this searchResearch string. valued opinions of the other researchers. The search string used (DevOps Testing) may have Keywords: Agile Testing, Continuous Integration, Continuous Testing, DevOps Testing 1. Introduction to wait till the release date when operations team integrates it. Operations team has challenges in integrating/deploy- The evolution of software development lifecycle waterfall( ing continuous release cycles. On top it, operations team methodology to V-Model to agile of contemporary times) face challenges due to manual deployments, inconsistent has brought change in the way testing is performed. environments (Development vs. Production), complex Traditionally in waterfall lifecycle model, test execution is infrastructure issues, etc. Business teams are having chal- done after coding. Of late, the importance of lean, time to lenges in going early live. The key objective of the agile market led to introduction of agile process. Though agile which is shorter time to market is not fully realized1. In process is producing working functionality at the end of the recent times, industry is adopting DevOps practice to every sprint (cycle), completed functionality would have overcome this challenge. DevOps is a cross-disciplinary *Author for correspondence The Factors Driving Testing in DevOps Setting- A Systematic Literature Survey practice, promotes set of processes and methods to enhance 2.2 Data Collection Process communication and collaboration between business, devel- The key term search process6,7 has been adapted to opment, testing and operations teams. The critical objective databases of IEEE Xplore, ACM Digital Library, Science is to establish cultural change and collaboration between all Direct, Springer, Wiley InterScience. We used search stakeholders of delivery pipeline2. Among all stakeholders terms- “DevOps” And “Testing”. The search string applied of software system, the role of testing becoming critical in to Full Text and Metadata. The search process was done the context of DevOps. DevOps allow continuous releases during the month of July 2016. We excluded book chap- (continuous testing) without compromising quality and ters, standards, courses, editorials, prefaces, tutorials, speed. Hence it necessitates the study of testing adoption workshops, other than English language articles and in DevOps environment which helps in defining new test poster sessions. Total number of hits was 295 as showed strategies, frameworks, metrics, etc. in Table 1. The objective of this paper is to identify key technical, However, after our initial review, 46 articles were cultural and managerial factors of testing in DevOps set- excluded as they are completely non-relevant to survey ting. The present study addresses critical research question. theme. Finally total articles considered for review are What are the different motivational factors driving testing 249. The following in Figure 1, represents the distri- in DevOps Environment? It has been answered conduct- bution of 249 articles between 5 databases. Out of 249 ing literature survey on academic and industry reports. articles, 175 are having close relationship to DevOps Section 2 describes research approach. Section 3 details and 74 are not appropriately relevant to the theme. our findings of the systematic literature study. Section Out of 175 articles, 49 are journal articles and 126 are 4 presents discussion and threats to validity. Section 5 conference proceedings. The distribution of articles summarizes our contribution. across various software lifecycle phases is as follows 2. The Research Approach which is showed in Figure 2 (2% of articles are related to Requirements Planning, 10% of articles are related 2.1 Research Overview Architecture and Design, 25% of articles related to Development, 18% of articles related to Testing, 24% We resorted to non-experimental methods like content analysis in the form of observation and analysis of exist- Table 1. Database Search Results ing data sets to identify critical factors driving testing in Data Bases (Journals and DevOps ecosystem. These are presented in the Section No of Hits Conferences) 3. Content analysis method gives wide perspective of IEEE Xplore 211 research direction in systematic way3. Among five types of texts available in content analysis method (written Sciencedirect 34 text, oral text, iconic text, audio-visual text, hypertexts), ACM Digital Library 23 this study focuses on written and hypertexts available in SpringerLink 12 books, journal papers and web sources. It is the study of Wiley InterScience 15 mute evidence of texts4. We developed codebook with Total 295 categories and sub categories classified in a staggered approach. We made sure reliability of the coding standards and mapping process with proper checks and balances. This codebook is used for analysis, interpretations and deriving key drivers of DevOps testing. Review protocols are defined and guidelines are adhered as per Cochrane Handbook for Systematic Reviews5. Codebook has been divided into 6 categories article description (year, name of journal or conference, name of the title, volume no, DOI), author key words, SDLC Phase associated to, relevancy with testing phase, key terms associated with testing and abstract6. Figure 1. Article distribution per database. 2 Vol 9 (48) | December 2016 | www.indjst.org Indian Journal of Science and Technology Jayasri Angara, Srinivas Prasad and Gutta Sridevi of articles related to Deployment, 8% of articles related 2.4 Extended Manual Literature Survey to Monitoring, 1% of articles related to Configuration Review Management, 1% of articles related to Migration, 10% of articles related to Project Management). In Figure 3 This section presents the outcome of extended manual presents the article distribution over years from 2011- literature survey. The critical factors of DevOps culture, 2016*. 2016* representation is partial figure which is roles and responsibilities and trends are presented in till the month of July 2016. this section. DevOps Testing is a mental discipline and 8 The goal of this survey is to identify key drivers of Organizational Mindset . Collaborative Development, technical, cultural and managerial factors impacting test- Continuous Testing, Continuous Release and Deployment, ing function in DevOps setting. It addresses the following Continuous Monitoring and Continuous Customer research question “What are the different motivational Feedback, Continuous Improvement, Continuous 9–11 factors driving testing in DevOps Environment?”. Adoption are associated with DevOps . DevOps pro- motes shared resources, optimization of processes and 12 2.3 Systematic Review Findings reduces the waste . DevOps demands alternative met- rics. They should

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    8 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us