Detecting semantic conflicts with unit tests
Authors:
- Léuson Da SilvaLSLéuson Da Silva
- Paulo BorbaPBPaulo Borba
- Toni MacielTMToni Maciel
- Wardah MahmoodWMWardah Mahmood
- Thorsten BergerTBThorsten Berger
- João MoisakisJMJoão Moisakis
- Aldiberg GomesAGAldiberg Gomes
- Vinícius LeiteVLVinícius Leite
Open Access
- 24 April 2024
- journal article
- research article
- Published by Elsevier in Journal of Systems and Software
- Vol. 214
Abstract
No abstract availableKeywords
All Related Versions
This publication has 20 references indexed in Scilit:
- Can we trust tests to automate dependency updates? A case study of Java ProjectsJournal of Systems and Software, 2022
- Understanding predictive factors for merge conflictsInformation and Software Technology, 2020
- Predicting Merge Conflicts in Collaborative Software Development2019
- Understanding semi-structured merge conflict characteristics in open-source Java projectsEmpirical Software Engineering, 2017
- 1600 faults in 100 projects: automatically finding faults while achieving high coverage with EvoSuiteEmpirical Software Engineering, 2013
- Whole Test Suite GenerationIEEE Transactions on Software Engineering, 2012
- Palantir: Early Detection of Development Conflicts Arising from Parallel Code ChangesIEEE Transactions on Software Engineering, 2011
- A state-of-the-art survey on software mergingIEEE Transactions on Software Engineering, 2002
- Supporting articulation work using software configuration management systemsComputer Supported Cooperative Work (CSCW), 1996
- PIE: a dynamic failure-based techniqueIEEE Transactions on Software Engineering, 1992