Some of the UI tests fail on Indigo and Indigo SR1

reprogrammer commented 13 years ago

As part of issue #206, we patched the following plug-ins of Eclipse Indigo.

org.eclipse.jdt.core.manipulation
org.eclipse.jdt.ui
org.eclipse.ltk.core.refactoring
org.eclipse.ltk.ui.refactoring

Then, we ran all of CodingSpectator's automated tests in edu.illinois.codingspectator.monitor.tests and edu.illinois.codingspectator.ui.tests. Overall, CodingSpectator seems to work find on Indigo except that some of the tests in edu.illinois.codingspectator.ui.tests fail because CodingSpectator sometimes generates slightly different logs on Indigo.

The following tests fail on Indigo because the wording of a compilation error has changed in Indigo. Eclipse Indigo has replaced the the error message "... is never read locally" by "... is not used".

move.T28
pushdown.T04
pushdown.T05
pushdown.T07
pushdown.T08
rename.T17
rename.T23

And, test rename.T07 fails on Indigo because the input attribute of the rename refactoring has slightly changed in Indigo.

We are planning to fix this issue by adding expected logs for Indigo to edu.illinois.codingspectator.ui.tests whenever they are different than those for Helios. Then, we will update the UI tests to detect the version of Eclipse and check the actual log files against the right expected logs.

reprogrammer commented 12 years ago

Test pullup.T01 fails on Indigo because the status attribute is different in Indigo. And, pullup.T02 fails on Indigo because the actual refactoring-problems.log file does not exist.

reprogrammer commented 12 years ago

The UI tests exhibit similar behaviors on Indigo and Indigo SR1. The differences in Indigo SR1 with respect to Indigo are the following:

Test pushdown.T03 fails on Indigo SR1 because of unexpected changes of compilation problems.
Tests pullup.T01 and pullup.T02 pass on Indigo SR1.

vazexqi / CodingSpectator

Some of the UI tests fail on Indigo and Indigo SR1 #258