abhikrc

We know that by testing the patches. Automated Program Repair is an area of research which has done this.

The patches are tested against a test-suite. So, if there are tests, we welcome them, we definitely use them to validate the patches.

The short answer is that unit tests are not needed in AutoCodeRover. The technique proceeds by a sophisticated code search starting from the Github issue. tests are not needed. The code search helps in setting the context for LLM agents - which can help in the patch construction.

If tests are available, they can give additional help in setting code context. But tests are not needed, and most of Github issues are solved without tests.

All experimental numbers appear in the arxiv paper. Please let us know if you have more questions.

No it does not need an unit test to work. We responded to another similar question from another user.

The entire setup is available for inspection from

https://github.com/nus-apr/auto-code-rover

Please try it out and send emails to the contact emails in this webpage, if you have any questions.

The entire setup is available for inspection, please see

https://github.com/nus-apr/auto-code-rover

if you need example bugs we can provide that too. Some examples also appear in the arxiv paper, please see

https://arxiv.org/abs/2404.05427