You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to express my great attitudes to the author of this tool "defects4j-repair-runner", because it is really well-designed and highly effective in running the defects4j programs with automated repair tools.
And I want to share my doubts here. When I run the Nopol on the Chart 3 with this tool command:
python defects4j-g5k-node.py -tool Nopol -project Chart -id 3
I found that the number of failed test cases are 2. However, when I run defects4j test in Chart 3, there is only one failed test case, the output is:
Failing tests: 1
To figure out this, I add some print() to Nopol to get the failed test cases information. I found that:
The two failed test cases are all "org.jfree.data.time.junit.TimeSeriesTests#testCreateCopy3". In other words. this only failed test case are run twice in the fault localization.
So why was this only failed test case run twice in one repair? As if it is run twice rather than once, the executed number of failed test cases will change to 2, which will directly lead to the change in the statements' suspiciousness. That is why I think it is important to figure this out.
Thank you!
The text was updated successfully, but these errors were encountered:
I would like to express my great attitudes to the author of this tool "defects4j-repair-runner", because it is really well-designed and highly effective in running the defects4j programs with automated repair tools.
And I want to share my doubts here. When I run the Nopol on the Chart 3 with this tool command:
python defects4j-g5k-node.py -tool Nopol -project Chart -id 3
I found that the number of failed test cases are 2. However, when I run defects4j test in Chart 3, there is only one failed test case, the output is:
Failing tests: 1
To figure out this, I add some print() to Nopol to get the failed test cases information. I found that:
The two failed test cases are all "org.jfree.data.time.junit.TimeSeriesTests#testCreateCopy3". In other words. this only failed test case are run twice in the fault localization.
So why was this only failed test case run twice in one repair? As if it is run twice rather than once, the executed number of failed test cases will change to 2, which will directly lead to the change in the statements' suspiciousness. That is why I think it is important to figure this out.
Thank you!
The text was updated successfully, but these errors were encountered: