English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Context: Many studies consider the relation between individual aspects andbug-introduction, e.g., software testing and code review. Due to the design ofthe studies the results are usually only about correlations as interactions orinterventions are not considered.  Objective: Within this study, we want to narrow this gap and provide a broadempirical view on aspects of software development and their relation tobug-introducing changes.  Method: We consider the bugs, the type of work when the bug was introduced,aspects of the build process, code review, software tests, and any otherdiscussion related to the bug that we can identify. We use a qualitativeapproach that first describes variables of the development process and thengroups the variables based on their relations. From these groups, we can inducehow their (pair-wise) interactions affect bug-introducing changes.

An exploratory study of bug-introducing changes: what happens when bugs are introduced in open source software?