Salient-class location: help developers understand code change in code review

  title={Salient-class location: help developers understand code change in code review},
  author={Yuan Huang and Nan Jia and Xiangping Chen and Kai Hong and Zibin Zheng},
  booktitle={ESEC/SIGSOFT FSE},
Code review involves a significant amount of human effort to understand the code change, because the information required to inspect code changes may distribute across multiple files that reviewers are not familiar with. Code changes are often organized as commits for review. In this paper, we found that most of the commits contain a salient class, which is saliently modified and causes the modification of the rest classes in a commit. Our user studies confirmed that identifying the salient… CONTINUE READING

Tables and Topics from this paper.


Publications citing this paper.

Recommending Differentiated Code to Support Smart Contract Update

  • 2019 IEEE/ACM 27th International Conference on Program Comprehension (ICPC)
  • 2019