Decomposing Composite Changes for Code Review and Regression Test Selection in Evolving Software

No abstract is available for this paper.

• Publication year

  2019

• Venue

  Journal of Computational Science and Technology

• Publication date

  2019-03-01

• Fields of study

  Computer Science

• Identifiers
  DOI 10.1007/s11390-019-1917-9
• External record

  Open on Semantic Scholar

• Source metadata

  Semantic Scholar

• No claims are published for this paper.

• No concepts are published for this paper.

• Interactively Decomposing Composite Changes to Support Code Review and Regression Testing

  2017cited by this paper
• Untangling fine-grained code changes

  2015cited by this paper
• The impact of tangled code changes on defect prediction models

  2015cited by this paper
• Partitioning Composite Code Changes to Facilitate Code Review

  2015influential reference
• Practical regression test selection with dynamic file dependencies

  2015cited by this paper
• Helping Developers Help Themselves: Automatic Decomposition of Code Review Changesets

  2015influential reference
• Interactive Code Review for Systematic Changes

  2015influential reference
• The impact of tangled code changes

  2013influential reference
• Expectations, outcomes, and challenges of modern code review

  2013cited by this paper
• Automated Behavioral Testing of Refactoring Engines

  2012cited by this paper
• How do software engineers understand code changes?: an exploratory study in industry

  2012influential reference
• How We Refactor, and How We Know It

  2012cited by this paper
• Contemporary Peer Review in Action: Lessons from Open Source Development

  2012cited by this paper
• RTED: A Robust Algorithm for the Tree Edit Distance

  2011cited by this paper
• Proactive detection of collaboration conflicts

  2011cited by this paper
• EvoSuite: automatic test suite generation for object-oriented software

  2011cited by this paper
• Making program refactoring safer

  2010cited by this paper
• Change Distilling:Tree Differencing for Fine-Grained Source Code Change Extraction

  2007cited by this paper
• Randoop: feedback-directed random testing for Java

  2007cited by this paper
• An O(n^3)-Time Algorithm for Tree Edit Distance

  2006cited by this paper
• An optimal decomposition algorithm for tree edit distance

  2006cited by this paper
• Mining version histories to guide software changes

  2005cited by this paper
• Crisp: a debugging tool for Java programs

  2005influential reference
• Clone detection in source code by frequent itemset techniques

  2004cited by this paper
• The Role of Inspection in Software Quality Assurance

  2003cited by this paper
• CCFinder: A Multilinguistic Token-Based Code Clone Detection System for Large Scale Source Code

  2002cited by this paper
• DMS®: Program Transformations for Practical Scalable Software Evolution

  2002cited by this paper
• Language-specific make technology for the Java programming language

  2002influential reference
• An Overview of AspectJ

  2001cited by this paper
• Regression test selection for Java software

  2001cited by this paper
• Identifying similar code with program dependence graphs

  2001influential reference
• System-dependence-graph-based slicing of programs with arbitrary interprocedural control flow

  1999cited by this paper
• Yesterday, my program worked. Today, it does not. Why?

  1999cited by this paper
• Qualitative Methods in Empirical Studies of Software Engineering

  1999cited by this paper
• Clone detection using abstract syntax trees

  1998cited by this paper
• Decomposing legacy programs: a first step towards migrating to client-server platforms

  1998cited by this paper
• Extracting Reusable Funtions by Flow Graph-Based Program Slicing

  1997cited by this paper
• A safe, efficient regression test selection technique

  1997cited by this paper
• Understanding function behaviors through program slicing

  1996cited by this paper
• Aspect-oriented programming

  1996cited by this paper
• The cost of selective recompilation and environment processing

  1994cited by this paper
• Interprocedural optimization

  1993cited by this paper
• A cost model to compare regression test strategies

  1991cited by this paper
• Using Program Slicing in Software Maintenance

  1991cited by this paper
• Insights into regression testing (software testing)

  1989cited by this paper
• Simple Fast Algorithms for the Editing Distance Between Trees and Related Problems

  1989cited by this paper
• Smart recompilation

  1986cited by this paper
• AnO(ND) difference algorithm and its variations

  1986cited by this paper
• Smart recompilation

  1985cited by this paper
• Binary codes capable of correcting deletions, insertions, and reversals

  1965cited by this paper
• RETROSPECTIVE: Interprocedural Slicing Using Dependence Graphs

  year unknowncited by this paper

• A Survey of Code Review Benchmarks and Evaluation Practices in Pre-LLM and LLM Era

  2026cites this paper
• A fine-grained taxonomy of code review feedback in TypeScript projects

  2025cites this paper
• LLM-Driven Collaborative Model for Untangling Commits via Explicit and Implicit Dependency Reasoning

  2025cites this paper
• Detecting and Untangling Composite Commits via Attributed Graph Modeling

  2025cites this paper
• A Roadmap on Modern Code Review: Challenges and Opportunities

  2024cites this paper
• Method level static source code analysis on behavioral change impact analysis in software regression testing

  2024cites this paper
• Towards Efficient Fine-Tuning of Language Models With Organizational Data for Automated Software Review

  2024influential citation
• Modern Code Reviews—Survey of Literature and Practice

  2023cites this paper
• State of Practical Applicability of Regression Testing Research: A Live Systematic Literature Review

  2023cites this paper
• A Systematic Literature Review and Taxonomy of Modern Code Review

  2021influential citation
• An exploratory study on confusion in code reviews

  2020cites this paper
• Test Case Prioritization Using Clustering Approach for Object Oriented Software

  2019cites this paper