Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
E4/Compatibility/Testing
This is now a historical document. The org.eclipse.ui.tests code is run as part of the Eclipse SDK build.
This page describes how to run the 3.x API tests with a workbench that's backed by e4's compatibility layer.
Setup
- Download a recent e4 SDK here.
- Add this CVS repository location to your workspace setup:
:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse - Checkout the
org.eclipse.e4.ui.relengmodule from the/cvsroot/eclipse'se4/relengdirectory. - Right-click on the
e4.ui.compatibility.psffile and select 'Import project set...'. When you are prompted for a password, just enteranonymousas your user name and leave the password as blank. - Repeat the procedure for
e4.ui.psf,e4.ui.css.psf, ande4.ui.tests.compatibility.psf. You will have errors.
Running the tests
- Select a test from the
org.eclipse.ui.testsbundle, such asorg.eclipse.ui.tests.api.IWorkbenchPageTestfor example. - If there are compiler errors indicating incorrect imports, try using 'Organize Imports' to get rid of them or to have them point to the e4 variant of the internal.
- Right-click on the file > Run As > JUnit Plug-in Test.
- This will fail. Open the launch configuration dialog.
- Select the launch configuration that was just generated and go to the 'Main' tab.
- Change the target product to
org.eclipse.e4.ide.application.product. - Try running the test again. It should work now.