Premium
Test activities in the continuous integration and delivery pipeline
Author(s) -
Mårtensson Torvald,
Ståhl Daniel,
Bosch Jan
Publication year - 2019
Publication title -
journal of software: evolution and process
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.371
H-Index - 29
eISSN - 2047-7481
pISSN - 2047-7473
DOI - 10.1002/smr.2153
Subject(s) - pipeline (software) , computer science , stakeholder , test (biology) , integration testing , unit testing , process management , software engineering , software , stakeholder engagement , identification (biology) , scale (ratio) , systems engineering , risk analysis (engineering) , engineering , operating system , business , management , paleontology , law , political science , economics , biology , botany , physics , quantum mechanics
Based on 25 interviews with participants from four case study companies that develop large‐scale software embedded systems, this paper presents the Test Activity Stakeholders (TAS) model. The TAS model shows how the continuous integration and delivery pipeline can be designed to include test activities that support four stakeholder interests: “Check changes,” “Secure stability,” “Measure progress,” and “Verify compliance.” The model is developed to show how each of the stakeholder interests are best supported by unit/component tests or system tests, by automated testing or manual testing and by tests executed in simulated environments or on real hardware. The TAS model may serve as a starting point for companies when evaluating and designing their continuous integration and delivery pipeline. The validation of the TAS model included twelve individuals from three case study companies. The validation showed that the TAS model is actionable and useful in practice, enabling the identification of stakeholders and showing where improvement efforts should be focused in order to support all stakeholder interests in the continuous integration and delivery pipeline.