Imagine a robot automatically fixing your Travis build failure. Instead of understanding the Travis log, and fixing the error, you would merge a pull request stating "Fixing build failure #1234". This talk shows that this is possible. It starts with an overview of academic research on automatic repair, and then follows up by stating the vision of automatic repair in continuous integration. Can this be done for real? I’ll present you Repairnator, a robot who automatically fixes build failures, and the scientific and engineering challenges behind such a robot.
Human-competitive Patches in Automatic Program Repair with Repairnator
Objective of the presentation:
The objective of the presentation is to spread a cool new idea coming from research, automatic bug fixing, and let them the community know about the corresponding new Eclipse project Repairnator https://projects.eclipse.org/proposals/repairnator
Attendee pre-requisites - If none, enter "N/A":
Automated Testing, Continuous Integration