Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A question about the same two failed test cases in Nopol repair #1

Open
DehengYang opened this issue Dec 4, 2017 · 0 comments
Open

Comments

@DehengYang
Copy link

DehengYang commented Dec 4, 2017

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

  • org.jfree.data.time.junit.TimeSeriesTests::testCreateCopy3

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.

all cases number

failed case1

failed case 2

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant