Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/Compatibility/Testing"
< E4 | Compatibility
(→Setup) |
|||
| Line 5: | Line 5: | ||
#Checkout the <code>org.eclipse.e4.ui.releng</code> module from the <code>/cvsroot/eclipse</code>'s <code>e4/releng</code> directory. | #Checkout the <code>org.eclipse.e4.ui.releng</code> module from the <code>/cvsroot/eclipse</code>'s <code>e4/releng</code> directory. | ||
#Right-click on the <code>e4.ui.compatibility.psf</code> file and select 'Import project set...'. You '''will''' have compiler errors. | #Right-click on the <code>e4.ui.compatibility.psf</code> file and select 'Import project set...'. You '''will''' have compiler errors. | ||
| + | #Repeat the procedure for <code>e4.ui.psf</code> and <code>e4.ui.css.psf</code>. | ||
==Running the tests== | ==Running the tests== | ||
Revision as of 08:46, 9 February 2010
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.
- 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...'. You will have compiler errors. - Repeat the procedure for
e4.ui.psfande4.ui.css.psf.
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.
Known issues
- If you get a
NullPointerExceptioninOSGiContextStrategylike the stack trace below, you are seeingbug 299070. To workaround the problem, you can checkoutorg.eclipse.e4.core.servicesfrom CVS and then apply the patch that's there until a proper fix has been checked in.
java.lang.NullPointerException at org.eclipse.e4.internal.core.services.osgi.OSGiContextStrategy.addingService(OSGiContextStrategy.java:71) at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896) at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261) at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273) at org.eclipse.e4.internal.core.services.osgi.OSGiContextStrategy.lookup(OSGiContextStrategy.java:123) at org.eclipse.e4.core.services.internal.context.EclipseContext.internalGet(EclipseContext.java:347) at org.eclipse.e4.core.services.internal.context.EclipseContext.get(EclipseContext.java:316) at org.eclipse.ui.PlatformUI.getTestableObject(PlatformUI.java:171) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:43)