Creating a shared understanding of testing culture on a social coding site

Pham, Raphael; Singer, Leif; Liskin, Olga; Filho, Fernando Figueira; Schneider, Kurt

doi:10.1109/icse.2013.6606557

Cited by 96 publications

(122 citation statements)

References 14 publications

Supporting

Mentioning

119

Contrasting

Order By: Relevance

“…According to integrators, quality emerges from attention to detail; code style, documentation, commit formatting and adherence to project conventions all help to build confidence in the contribution. The issue of quality evaluation has been repeatedly mentioned in works on patch submission [7], [19], lightweight code review [12], [13] and testing [15]; in this sense, our work reinforces earlier findings. In addition, we document in detail what factors integrators examine in contributions when doing quality assessments.…”

Section: A Qualitysupporting

confidence: 90%

“…75% of our respondents run tests automatically through continuous integration services. Pham et al examined how testing works on GitHub [15]; our work confirms many of their findings (e.g. use of testing as a quality signal, manual examination when continuous integration fails) and complements it with more quantitative data about test diffusion on GitHub projects.…”

Section: B Testingsupporting

confidence: 78%

“…RQ1: How do integrators use pull-based development in their projects? 1) Overall use: To understand why and how projects use the pull-based development model, we asked integrators a multiple choice question that included the union of potential uses of pull requests that have been reported in the literature [1], [16], [15]. Respondents also had the opportunity to report other uses not in our list.…”

Section: Resultsmentioning

confidence: 99%

“…In turn, this calls for a more indepth, qualitative study to help us understand how integrators evaluate contributions. Initial qualitative evidence on how integrators assess contributions has been reported by Pham et al [15], but the focus of this work was the evaluation of testing practices rather than the pull-based development model.…”

Section: Background and Related Workmentioning

confidence: 99%

“…Integrators in our study actually mentioned the opposite: it is maintaining the community momentum and motivating contributors to do more work that is not easy. Through transparency [16] and lowered barriers to participation [15], [1], the pull-based model can act as glue for communities build around projects, if integrators are keen enough on fostering their project's communities by helping newcomers cope with tools and project processes, prioritizing the examination of community contributions and, in the extreme case, not rejecting unwanted contributions.…”

Section: E Community Buildingmentioning

confidence: 99%

See 4 more Smart Citations

Work Practices and Challenges in Pull-Based Development: The Integrator's Perspective

Gousios

Zaidman

Storey

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

270

348

View full text Add to dashboard Cite

Abstract-In the pull-based development model, the integrator has the crucial role of managing and integrating contributions. This work focuses on the role of the integrator and investigates working habits and challenges alike. We set up an exploratory qualitative study involving a large-scale survey involving 749 integrators, to which we add quantitative data from the integrator's project. Our results provide insights into the factors they consider in their decision making process to accept or reject a contribution. Our key findings are that integrators struggle to maintain the quality of their projects and have difficulties with prioritizing contributions that are to be merged.

show abstract

Section: A Qualitysupporting

confidence: 90%

Section: B Testingsupporting

confidence: 78%

Section: Resultsmentioning

confidence: 99%

Section: Background and Related Workmentioning

confidence: 99%

Section: E Community Buildingmentioning

confidence: 99%

See 3 more Smart Citations

Work Practices and Challenges in Pull-Based Development: The Integrator's Perspective

Gousios

Zaidman

Storey

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

270

348

View full text Add to dashboard Cite

show abstract

Watch out for this commit! A study of influential software changes

Kim

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

One single code change can significantly influence a wide range of software systems and their users. For example, (a) adding a new feature can spread defects in several modules, while (b) changing an API method can improve the performance of all client programs. Unfortunately, developers often may not clearly know whether code changes are influential at commit time. This paper investigates influential software changes and proposes an approach to identify them immediately when they are applied. Our goals are to (a) identify existing influential changes (ICs) in software projects, (b) understand their characteristics, and (c) build a classification model of ICs to help developers find and address them early. We first conduct a post‐mortem analysis to discover existing influential changes by using intuitions (eg, changes referred by other changes). Then, we re‐categorize all identified changes through an open‐card sorting process. Subsequently, we conduct a survey with about 100 developers to finalize a taxonomy. Finally, from our ground truth, we extract features, including metrics such as the complexity of changes and file centrality in co‐change graphs to build machine learning classifiers. The experiment results show that our classification model with random samples achieves 86.8% precision, 74% recall, and 80.4% F‐measure, respectively.

show abstract

Perceptions of open‐source software developers on collaborations: An interview and survey study

Constantino

Souza

Zhou

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

With the emergence of social coding platforms, collaboration has become a key and dynamic aspect to the success of software projects. In such platforms, developers have to collaborate and deal with issues of collaboration in open‐source software development. Although collaboration is challenging, collaborative development produces better software systems than any developer could produce alone. Several approaches have investigated collaboration challenges, for instance, by proposing or evaluating models and tools to support collaborative work. Despite the undeniable importance of the existing efforts in this direction, there are few works on collaboration from perspectives of developers. In this work, we aim to investigate the perceptions of open‐source software developers on collaborations, such as motivations, techniques, and tools to support global, productive, and collaborative development. Following an ad hoc literature review, an exploratory interview study with 12 open‐source software developers from GitHub, our novel approach for this problem also relies on an extensive survey with 121 developers to confirm or refute the interview results. We found different collaborative contributions, such as managing change requests. Besides, we observed that most collaborators prefer to collaborate with the core team instead of their peers. We also found that most collaboration happens in software development (60%) and maintenance (47%) tasks. Furthermore, despite personal preferences to work independently, developers still consider collaborating with others in specific task categories, for instance, software development. Finally, developers also expressed the importance of the social coding platforms, such as GitHub, to support maintainers, and contributors in making decisions and developing tasks of the projects. Therefore, these findings may help project leaders optimize the collaborations among developers and reduce entry barriers. Moreover, these findings may support the project collaborators in understanding the collaboration process and engaging others in the project.

show abstract

Creating a shared understanding of testing culture on a social coding site

Cited by 96 publications

References 14 publications

Work Practices and Challenges in Pull-Based Development: The Integrator's Perspective

Work Practices and Challenges in Pull-Based Development: The Integrator's Perspective

Watch out for this commit! A study of influential software changes

Perceptions of open‐source software developers on collaborations: An interview and survey study

Contact Info

Product

Resources

About