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

Code review that detects and locates defects and other quality issues playsan important role in software quality control. One type of issue that mayimpact the quality of software is code smells. Yet, little is known about theextent to which code smells are identified during modern code review. Toinvestigate the concept behind code smells identified in modern code review andwhat actions reviewers suggest and developers take in response to theidentified smells, we conducted a study of code smells in code reviews byanalyzing reviews from four large open source projects from the OpenStack (Novaand Neutron) and Qt (Qt Base and Qt Creator) communities. We manually checked atotal of 25,415 code review comments obtained by keywords search and randomselection, and identified 1,539 smell-related reviews. Our analysis found that1) code smells were not commonly identified in code reviews, 2) smells wereusually caused by violation of coding conventions, 3) reviewers usuallyprovided constructive feedback, including fixing (refactoring) recommendationsto help developers remove smells, 4) developers generally followed thoserecommendations and actioned the changes, 5) once identified by reviewers, itusually takes developers less than one week to fix the smells, and 6) the mainreason why developers chose to ignore the identified smells is not worth fixingthe smell. Our results suggest that: 1) developers should closely follow codingconventions in their projects to avoid introducing code smells, 2) review-baseddetection of code smells is perceived to be a trustworthy approach bydevelopers, mainly because reviews are context-sensitive (as reviewers are moreaware of the context of the code given that they are part of the project'sdevelopment team), and 3) program context needs to be fully considered in orderto make a decision of whether to fix the identified code smell immediately.

Code Smells Detection via Modern Code Review: A Study of the OpenStack and Qt Communities