Can we trust tests to automate dependency updates? A case study of Java Projects
Authors:
- Joseph HejderupJHJoseph Hejderup
- Georgios GousiosGGGeorgios Gousios
Open Access
- 1 January 2022
- journal article
- research article
- Published by Elsevier in Journal of Systems and Software
- Vol. 183
Abstract
No abstract availableKeywords
All Related Versions
Funding Information
- Horizon 2020 Framework Programme
- H2020 (825328)
- Nederlandse Organisatie voor Wetenschappelijk Onderzoek (628.008.001)
This publication has 16 references indexed in Scilit:
- Semantic versioning and impact of breaking changes in the Maven repositoryJournal of Systems and Software, 2017
- Do developers update their library dependencies?Empirical Software Engineering, 2017
- In defense of soundinessCommunications of the ACM, 2015
- Combining concept lattice with call graph for impact analysisAdvances in Engineering Software, 2012
- A survey of code‐based change impact analysis techniquesSoftware Testing, Verification and Reliability, 2012
- Regression testing minimization, selection and prioritization: a surveySoftware Testing, Verification and Reliability, 2012
- EvoSuite2011
- Change impact graphs: Determining the impact of prior codechangesInformation and Software Technology, 2009
- A Comparative Study of Industrial Static Analysis ToolsElectronic Notes in Theoretical Computer Science, 2008
- The program dependence graph and its use in optimizationACM Transactions on Programming Languages and Systems, 1987