[pde-dev] Profiling PDE Junit Plugin Tests

[Scott Gelb <SGelb@xxxxxxxxxxxxxx>]

Greetings,

 

   I'm new to Eclipse PDE development, so please bare with me...

 

   I've been having some difficulty using a few of the profilers out there to investigate some memory issues in a few of my junit tests. These tests require the pde and thus they run as junit plugin tests via the Eclipse environment. If I try to use the Eclipse profiler, I get the same error/exception that I receive when trying to run a pde test as a normal junit test:

 

org.eclipse.core.internal.runtime.AssertionFailedException: assertion failed: The application has not been initialized.

at org.eclipse.core.internal.runtime.Assert.isTrue(Assert.java:101)

at org.eclipse.core.internal.runtime.InternalPlatform.assertInitialized(InternalPlatform.java:191)

at org.eclipse.core.internal.runtime.InternalPlatform.getPluginRegistry(InternalPlatform.java:410)

at org.eclipse.core.runtime.Platform.getPluginRegistry(Platform.java:321)

at com.metamatrix.core.util.SmartPdeTestSuite.<init>(SmartPdeTestSuite.java:24)

at com.metamatrix.modeler.core.PdeTestAutomatedTestUtil.suite(PdeTestAutomatedTestUtil.java:73)

at com.metamatrix.modeler.core.PdeTestAutomatedTestUtil.main(PdeTestAutomatedTestUtil.java:40)

Exception in thread "main"

 

   What type of strategy do people use when profiling junit tests that require the pde? Is there a way to bootstrap a profiling tool to the jvm that the pde initializes? Again, I apologize for my naiveté, but I'm nearing my wits' end on figuring out a good way to accomplish this goal.

 

Thanks,

Scott