2022
DOI: 10.1016/j.csi.2021.103588
|View full text |Cite
|
Sign up to set email alerts
|

On the effects of continuous delivery on code quality: A case study in industry

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
1
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(2 citation statements)
references
References 25 publications
0
1
0
Order By: Relevance
“…Especially shorter delivery cycles undermine the quality and security, and accumulate the 'technical debt', which needs to be addressed eventually, and sometimes never done. The adoption of continuous delivery has been found in industrial case studies to negatively affect the quality of the source code, increase the number of security vulnerabilities, introduce code smells and duplicated codes, to be able to improve customer satisfaction-focused metrics, such as delivery rates [31]. The challenges exemplified here make software quality improvement a good candidate for gamification interventions, since gamification can contribute positively by creating a motivational dimension for higher quality software.…”
Section: 2mentioning
confidence: 94%
“…Especially shorter delivery cycles undermine the quality and security, and accumulate the 'technical debt', which needs to be addressed eventually, and sometimes never done. The adoption of continuous delivery has been found in industrial case studies to negatively affect the quality of the source code, increase the number of security vulnerabilities, introduce code smells and duplicated codes, to be able to improve customer satisfaction-focused metrics, such as delivery rates [31]. The challenges exemplified here make software quality improvement a good candidate for gamification interventions, since gamification can contribute positively by creating a motivational dimension for higher quality software.…”
Section: 2mentioning
confidence: 94%
“…White box testers have access to the system's source code and are therefore familiar with its architecture. The tester begins by analyzing the source code, then uses the knowledge from the source code to generate a variety of test cases, and finally, particular code routes are utilized in order to achieve a desired amount of code coverage [29]. It is guaranteed by the test cases that each of the program's independent pathways has been followed at least once.…”
Section: A Types Of Testingmentioning
confidence: 99%