Author of the publication

Could I have a stack trace to examine the dependency conflict issue?

, , , , , , , and . ICSE, page 572-583. IEEE / ACM, (2019)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

 

Other publications of authors with the same name

Expressing and checking intended changes via software change contracts., , , and . ISSTA, page 1-11. ACM, (2013)relifix: Automated Repair of Software Regressions., and . ICSE (1), page 471-482. IEEE Computer Society, (2015)ReAssert: a tool for repairing broken unit tests., , , , , , , , and . ICSE, page 1010-1012. ACM, (2011)Could I have a stack trace to examine the dependency conflict issue?, , , , , , , and . ICSE, page 572-583. IEEE / ACM, (2019)The State and Future of Genetic Improvement., , , , , , , , , and 2 other author(s). ACM SIGSOFT Software Engineering Notes, 44 (3): 25-29 (2019)Anti-patterns in search-based program repair., , , and . SIGSOFT FSE, page 727-738. ACM, (2016)Software Change Contracts., , , and . ACM Trans. Softw. Eng. Methodol., 24 (3): 18:1-18:43 (2015)Codeflaws: a programming competition benchmark for evaluating automated program repair tools., , , , and . ICSE (Companion Volume), page 180-182. IEEE Computer Society, (2017)Partitioning Patches into Test-equivalence Classes for Scaling Program Repair., , , and . CoRR, (2017)A feasibility study of using automated program repair for introductory programming assignments., , , , and . ESEC/SIGSOFT FSE, page 740-751. ACM, (2017)