[news.eclipse.tptp] Re: Eclipse -TPTP Error

[Matthias Wiskow <matthias.wiskow@xxxxxxxxxxxxx>]

Hi Balakrishna,

you don't necessarily have to use deployment files.

If you want to use the recording instance of TPTP also as executing context:
- In the Launch Config dialog, select the default "local_deployment" option
- In the test suite's overview tab, checkmark "Use current workbench as 
context"

If you want to use a different Eclipse installation on the same host as 
execution context:
- Make sure the test candidate is "loaded" with TPTP capabilities.
  One convenient way to achieve this is following:
  - In the test candidate's eclipse folder, create a folder "links"
  - In folder "links", create a file "tptp.link" (as an example)
  - Edit file "tptp.link" to contain following line:

    path=C:/path/to/tptp_installdir

    After starting the test candidate, the Manage Configurations dialog 
should show the TPTP plug-ins.

- In the test suite's overview tab:
  - Uncheckmark "Use current workbench as context"
  - As Eclipse Location specify the absolute path to the test 
candidate's Equinox launcher plug-in, e.g. 
C:\Eclipse3.3\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.wr.jar

- In the Launch Config dialog, select the default "local_deployment" option

HTH,
Matthias

Balakrishna wrote:
> Hi All,
>
>
> I have installed  Eclipse 3.3 with TPTP 4.4 plugins on Windows platform 
> and the Auto GUI Recorder plugins 4.4.0.1 versions
>
> I have created the Test container as mentioned in the Eclipse TPTP.
>
> I have recorded a few scenarios  and then want to run them together in 
> standard mode of execution which will generate a log file .
>
> The Standard mode of execution involves three stages :
>
> 1. Creation of a location file
> 2.Creation of an artifact  file
> 3. Creation of a Deployment file.
>
> I have followed all the steps but when I launch the test container  with 
> the new configuration and then select the test suit created and the 
> Deployment file and then click on the Apply Button
> The progress of the execution starts and then after a while it stops at 36%
> Also a message appears as ïPreparing and Deployingï
> After sometime it fails with a message as :
>
> org.eclipse.hyades.internal.execution.local.control.InactiveProcessException 
>
> IWAT4039E The Test Execution Harness reported the following 
> problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException 
>
> java.lang.RuntimeException: 
> org.eclipse.hyades.internal.execution.local.control.InactiveProcessException 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.handleException(TestExecutionHarnessExecutorStub.java:347) 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:434) 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarness.launchTestExecution(TestExecutionHarness.java:2098) 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarness.access$2(TestExecutionHarness.java:1830) 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarness$2.run(TestExecutionHarness.java:750) 
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: 
> org.eclipse.hyades.internal.execution.local.control.InactiveProcessException 
>
> at 
> org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.launch(TestExecutionHarnessExecutorStub.java:422) 
>
> . 4 more
>
> IWAT4039E The Test Execution Harness reported the following 
> problems:org.eclipse.hyades.internal.execution.local.control.InactiveProcessException 
>
> An exception stack trace is not available
>
>
> Could you please assist me out in trouble shooting this issue.?
>
> In Quick mode , we can select all the earlier recorded tests at a tretch 
> and then run them together but we donït have a method to verify the log 
> file as per my understanding.
>
>
>
> Thanks & Regards,
> Balakrishna.