yuntong

3 ms·

1. 1.▲
   by yuntong 2y ago

   The developer written testcases are provided in SWE-bench-lite so those could be used to check the generated patches. The auto-generated patches are to reduce the effort of resolving issues. In practice, they should be reviewed and verified
2. 2.▲
   by yuntong 2y ago

   The previous comment was to describe the experiment settings. AutoCodeRover currently generates patches. Auto-generating high quality tests can be a parallel effort and another direction to explore. These efforts can eventually be used tog
3. 3.▲
   by yuntong 2y ago

   Thank you for your interest. There are some interesting examples in the SWE-bench-lite benchmark which are resolved by AutoCodeRover: - From sympy: https://github.com/sympy/sympy/issues/13643 . AutoCodeRover&#
4. 4.▲
   by yuntong 2y ago

   The problem statement of each issue is included in each result folder as `problem_statement.txt` (such as: https://github.com/nus-apr/auto-code-rover/blob/main/results... ). The developer patch for each i
5. 5.▲
   by yuntong 2y ago

   AutoCodeRover does not require or assume a unit test to generate patches. The results discussed in Section 6.1 of the ArXiv paper are generated without any unit test. The unit tests are used by SWE-bench, when evaluating the correctness of