Community
Participate
Working Groups
Using the connection property (<property name="tptp.test.connection" value="tptp:rac://${hostname}:10002/default" />), JUnit Plug-in Tests cannot be executed.
Exception when lauching a JUnit Plug-in test suite via ASF using the connection property: [tptp:execution] adding file BVT/AllBVTJUnitPluginTests.testsuite [tptp:execution] Test started! [tptp:execution] Test 'BVT/AllBVTJUnitPluginTests.testsuite' executing [tptp:execution] org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750) [tptp:execution] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [tptp:execution] java.lang.RuntimeException: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.handleException(TestExecutionHarnessExecutorStub.java:347) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:434) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830) [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750) [tptp:execution] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [tptp:execution] Caused by: org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422) [tptp:execution] ... 4 more [tptp:execution] org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException [tptp:execution] at org.eclipse.hyades.test.core.launch.delegates.AbstractLaunchConfigurationDelegate2.launch(AbstractLaunchConfigurationDelegate2.java:195) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614) [tptp:execution] at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:607) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.launch(AbstractTestExecutionService.java:797) [tptp:execution] at org.eclipse.hyades.test.core.services.AbstractTestExecutionService.execute(AbstractTestExecutionService.java:585) [tptp:execution] at org.eclipse.hyades.automation.server.AbstractService.execute(AbstractService.java:43) [tptp:execution] at org.eclipse.hyades.automation.server.ServiceProxy$1.run(ServiceProxy.java:141) [tptp:execution] at org.eclipse.hyades.automation.core.utils.ReusableThread.run(ReusableThread.java:131) [tptp:execution] at java.lang.Thread.run(Thread.java:801) BUILD FAILED /home/build/BVT/scripts/build.xml:28: java.lang.NullPointerException There are two issues: 1) The error returned does not accurately reflect what is failing. See defect #220543. 2) The deployment created under the covers to execute the test suite should handle a user-defined Location/Workbench Location. This would require a new property (including documentation http://help.eclipse.org/help33/topic/org.eclipse.hyades.test.doc.user/ref/rsupported-test-execution-service-properties.htm) for specificing a Location/Workbench Location file. Although this is required for the TPTP BVT, the work-around is to use a deployment with a Workbench Location or a .launch file from an Eclipse launch configuration.
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html).
Increasing the severity since Bobby was able to run a TPTP JUnit Plug-in test suite using the TPTP 4.4.1 driver without specifying a deployment (and workbench location). That is, the local deployment was used. Bobby, can you confirm if there was a launch configuration created in the 4.4.1 Eclipse UI for the test suite(s) that were executed via ASF?
Paul, in 441 the plugin junits executes fine from ant using the defaults, no extra configuration was done (no deployment, artifacts or location were created).
(In reply to comment #4) > Paul, in 441 the plugin junits executes fine from ant using the defaults, no > extra configuration was done (no deployment, artifacts or location were > created). > Thanks Bobby. Did you create a a launch configuration in the Eclipse UI for the test suite(s) (e.g. run the test suite from the Eclipse UI) before they were executed via ASF?
Hi Paul, No I didn't create anything extra, just checked out the test projects from cvs, unzipped tptp 441 and ran against it.
This is required for the TPTP BVT since the artifact and workbench location need to be manually generated when testing a build with new plug-in versions. In addition: [220390] Connection property does not deploy all dependencies Using the connection property (<property name="tptp.test.connection" value="tptp:rac://${hostname}:10002/default" />) does not deploy all dependencies. For example, when running the /org.eclipse.hyades.test.ui.logViewer.tests/JUnit/Test.UI.FrameworkEditors_logViewer_UtilitiesTest.testsuite JUnit, the depednanct org.eclipse.hyades.test.ui plug-in (and thus org.eclipse.hyades.test.ui.forms.base.ExecutionEventDetailsPart.java class) is not deployed. Although this is required for the TPTP BVT, the work-around is to use a deployment/artifact/location containing the necessary dependencies.
*** Bug 220390 has been marked as a duplicate of this bug. ***
Required since blocking the TPTP test automation.
Deferring to TPTP 4.5.3 since TPTP 4.5.2 development is closed (http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.5.2/schedule.html) and P2 defects are not considered candidates during release shut-down.
Required for the TPTP BVTs.
No longer required by a consuming product.
Closing.
