| Error executing recorded test suite. [message #51008] |
Thu, 19 January 2006 23:11  |
Eclipse User |
|
|
|
Originally posted by: talktomanalar.yahoo.com
Apologies if this is not the correct newsgroup to post a testing problem.
I created a test suite by using the HTTP Recorder. I was able to
generate the source, but am unable to execute (right click -> Run As ->
Test) the test. The following error appears in the log file.
!ENTRY org.eclipse.hyades.test.core 1 0 2006-01-19 14:14:45.34
!MESSAGE
org.eclipse.hyades.internal.execution.local.control.Inactive ProcessException
!STACK 0
org.eclipse.hyades.internal.execution.local.control.Inactive ProcessException
at
org.eclipse.hyades.execution.harness.TestExecutionHarnessExe cutorStub.launch(TestExecutionHarnessExecutorStub.java:417)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.la unchTestExecution(TestExecutionHarness.java:2058)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness.ac cess$2(TestExecutionHarness.java:1856)
at
org.eclipse.hyades.execution.harness.TestExecutionHarness$2. run(TestExecutionHarness.java:692)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
Any ideas? My environment is Eclipse 3.1.1, TPTP Test 4.1.0 and XSD 2.1.0
regards
m~
|
|
|
|
| Re: Error executing recorded test suite. [message #52224 is a reply to message #51397] |
Tue, 31 January 2006 16:21  |
| Eclipse User |
|
|
|
Originally posted by: talktomanalar.yahoo.com
Thank you Mark. I was able to get it to work by reinstalling all the
components. Seems like I was using an incorrect version of RAC earlier.
BTW I am using Java version 1.4.2_05.
Mark D Dunn wrote:
> This error is a common catch-all exception within the Test Execution
> Harness indicating that the test could not be executed. We will have to
> dig deeper to find the true problem.
> Which JRE are you using? I have tested with IBM 1.4.2 but not with 1.5
> . Make sure you are using a supported JRE. Also, make sure the RAC is
> running. Look at the servicelog.log file in %RASERVER_HOME%\config
> directory and see if it gives a more detailed error message.
> Additionally, look at the error log by Windows->Show View->Error Log.
>
> Let me know if any of these suggestions help. If not, we will keep trying.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03335 seconds
] 
Search
Help
Register
Login
Home
