-
Notifications
You must be signed in to change notification settings - Fork 115
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
Reactivate tests: disabled tests collection #525
Labels
Comments
Wittmaxi
pushed a commit
to Wittmaxi/eclipse.platform
that referenced
this issue
Jul 10, 2023
split function into private subfunctions
Wittmaxi
pushed a commit
to Wittmaxi/eclipse.platform
that referenced
this issue
Jul 10, 2023
split function into private subfunctions
HeikoKlare
pushed a commit
that referenced
this issue
Jul 11, 2023
split function into private subfunctions
Merged
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Jul 28, 2023
…rm#525 The test testPerformanceOneResource is working fine even though it is disabled. Contributes to eclipse-platform#525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Jul 28, 2023
Reactivation of working tests that were forgotten after the corresponding bug was fixed. Contributes to eclipse-platform#525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Jul 28, 2023
In this commit, the performance test from the Marker Test class is reactivated because it can be run quickly and successfully. Contributes to eclipse-platform#525
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Jul 31, 2023
Reactivation of working tests that were forgotten after the corresponding bug was fixed. Contributes to eclipse-platform#525
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Jul 31, 2023
Reactivation of working tests that were forgotten after the corresponding bug was fixed. Contributes to eclipse-platform#525
HeikoKlare
pushed a commit
that referenced
this issue
Jul 31, 2023
Reactivation of working tests that were forgotten after the corresponding bug was fixed. Contributes to #525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 3, 2023
This change reactivates all working disabled tests from project org.eclipse.debug.tests. The tests were forgotten after the corresponding bug was fixed. Contributes to eclipse-platform#525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 3, 2023
This change reactivates all working disabled tests from project org.eclipse.core.tests.net. The status of the corresponding but is CLOSED WONTFIX but the test runs successfully. Contributes to eclipse-platform#525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 3, 2023
This change reactivates all working disabled tests from project org.eclipse.team.tests.core. Contributes to eclipse-platform#525
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 3, 2023
Deleted useless test class Good.java because the test is trivial. Furthermore the package org.eclipse.tips.tests was also deleted because it is empty now. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 3, 2023
This change reactivates all working disabled tests from project org.eclipse.ua.tests. Bug 210024 has status CLOSED WONTFIX but still runs successfully. Bug 339274 has status RESOLVED FIXED. Contributes to eclipse-platform#525
akurtakov
pushed a commit
that referenced
this issue
Aug 3, 2023
Deleted useless test class Good.java because the test is trivial. Furthermore the package org.eclipse.tips.tests was also deleted because it is empty now. Contributes to #525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 7, 2023
This commit fixes the tests testLessThanOrEqualToExpression and testGreaterThanOrEqualToExpression of class CountExpression.java by adding additional functionality similar to the already existing. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 7, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuggin the code.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Aug 7, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 13, 2023
This commit reactivates and fixes the test testVerify() from FilterTest.java in org.eclipse.compare.tests. The test was outcommented in the past probably because Filter.validateResourceFilters(String) could not be performed anymore. Now validateResourceFilters(String) is performed on CompareResourceFilter. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 13, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 13, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 13, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 13, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
that referenced
this issue
Sep 13, 2023
This commit reactivates and fixes the test testVerify() from FilterTest.java in org.eclipse.compare.tests. The test was outcommented in the past probably because Filter.validateResourceFilters(String) could not be performed anymore. Now validateResourceFilters(String) is performed on CompareResourceFilter. Contributes to #525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 14, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 15, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 19, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
that referenced
this issue
Sep 19, 2023
In this commit the test testCheckReceiver() from the class CheckTests.java in org.eclipse.debug.tests is reactivated and fixed. It is about checking if a checkbox is properly toggled in the ui after changing its state. After fixing the issue the checked box can be clearly seen while debuging the code. Contributes to #525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 25, 2023
In this commit the two Tests setExtension and setExtension2 are reactivated and fixed. For this the class TipImage and especially its method setExtension have been changed. Now if setExtension is called, not only the instance variable fExtension is updated but also the instance variables fBase64Image or, if the URL constructor was used, fURL. These two instance variable are no final variables anymore, so they can be changed and tested. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 25, 2023
…-platform#525 In this commit the tests setExtension and setExtension2 are reactivated and changed. For this the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the field fExtension is updated but also the field fBase64Image. Mind that for this change the field fBase64Image can't be final. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 25, 2023
…-platform#525 In this commit the tests setExtension and setExtension2 are reactivated and changed. For this the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the field fExtension is updated but also the field fBase64Image. Mind that for this change the field fBase64Image can't be final. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 25, 2023
…-platform#525 In this commit the tests setExtension and setExtension2 are reactivated and changed. For this the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the field fExtension is updated but also the field fBase64Image. Mind that for this change the field fBase64Image can't be final. Contributes to eclipse-platform#525.
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Sep 27, 2023
…-platform#525 In this commit the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the extension is updated but also the base64image because the extension is a part of this image. Mind that for this change the field fBase64Image can't be final because it needs to be updated when the extension changes. setExtension is not used in the constructor anymore to set the fExtension field, rather it is directly set. Also the tests setExtension and setExtension2 are reactivated and updated to test the functionality of setExtension. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Nov 29, 2023
…-platform#525 In this commit the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the extension is updated but also the base64image because the extension is a part of this image. Mind that for this change the field fBase64Image can't be final because it needs to be updated when the extension changes. setExtension is not used in the constructor anymore to set the fExtension field, rather it is directly set. Also the tests setExtension and setExtension2 are reactivated and updated to test the functionality of setExtension. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Nov 29, 2023
…-platform#525 In this commit the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the extension is updated but also the base64image because the extension is a part of this image. Mind that for this change the field fBase64Image can't be final because it needs to be updated when the extension changes. setExtension is not used in the constructor anymore to set the fExtension field, rather it is directly set. Also the tests setExtension and setExtension2 are reactivated and updated to test the functionality of setExtension. Contributes to eclipse-platform#525.
HeikoKlare
pushed a commit
that referenced
this issue
Nov 30, 2023
In this commit the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the extension is updated but also the base64image because the extension is a part of this image. Mind that for this change the field fBase64Image can't be final because it needs to be updated when the extension changes. setExtension is not used in the constructor anymore to set the fExtension field, rather it is directly set. Also the tests setExtension and setExtension2 are reactivated and updated to test the functionality of setExtension. Contributes to #525.
This was referenced Dec 7, 2023
Closed
Michael5601
added a commit
to CodeLtDave/eclipse.platform
that referenced
this issue
Feb 12, 2024
…-platform#525 In this commit the method setExtension of TipImage.java is corrected to properly change the extension. Now if setExtension is called, not only the extension is updated but also the base64image because the extension is a part of this image. Mind that for this change the field fBase64Image can't be final because it needs to be updated when the extension changes. setExtension is not used in the constructor anymore to set the fExtension field, rather it is directly set. Also the tests setExtension and setExtension2 are reactivated and updated to test the functionality of setExtension. Contributes to eclipse-platform#525.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Situation
Several tests have been deactivated over the years for different reasons, such as temporary incompatibilities with a specific platform/OS, bugs in the code, indeterministic behavior of the test etc.
These disablements are done by adding some prefix to
test...
methods in JUnit 3, by removing or commenting out@Test
in JUnit 4 and 5, or by using@Ignore
or@Disabled
. In addition, several tests are only deactivated for specific platforms using early returns or assume statements within the test methods.Goal
Since in most cases there is no additional, unique documentation or tagging of these disablements, they are not easy to find. This issue is supposed to be an umbrella to document disabled tests (existing ones and potentially further ones).
The purpose of this issue is to collect the disabled tests to have a central overview and provide the chance to reactivate and, if necessary, fix them. It also serves as a "good first issue" (see eclipse-platform/eclipse.platform.text#212 (comment)) for interested new contributors, which can take any of the collected tests and try to fix them to learn about the Eclipse platform code while, at the same time, already having the chance to make valuable contributions to the project.
Process
I see the following ideas as good starting points for identifying disabled tests:
org.eclipse.core.tests.resources
@Test
annotation (JUnit 4 and 5)test
(JUnit 3), in particular those starting with_test
Platform
, such asOS_WIN32
and validate if they are used to disable tests for specific platformsisLinux()
etc. inResourceTest
subclasses and validate if they are used to disable tests for specific platformsassumeFalse
orassumeTrue
statements that make tests only run on specific platformsExamples
org.eclipse.core.tests.resources.regression.Bug_032076
skipTest
helper inorg.eclipse.core.tests.resources.usecase.SnapshotTest
Disabled in Maven
Some tests are disabled in Maven builds, such that integration builds do not reveal whether they fail or not.
org.eclipse.core.tests.net
is completely disabled. Tests run fine withing Eclipse on Windows, but Tycho execution fails, probably because of missing platform-dependent fragments (maybe have a look at how SWT deals with that).org.eclipse.team.tests.core.AllTeamUITests
andorg.eclipse.team.tests.ui.synchronize.AllTeamSynchronizeTests
are not executed as the test suite only executesorg.eclipse.team.tests.core.AllTeamTests
. Tests run fine within Eclipse on WIndows, but Tycho fails to execute some of theScopeTests
and theAllTeamSynchronizeTest
.The text was updated successfully, but these errors were encountered: