| tptp.automated.gui workaround, any luck? [message #89876] |
Mon, 11 December 2006 17:07  |
Eclipse User |
|
|
|
Originally posted by: emmanuelproulx.yahoo.com
I'm trying to execute a test I made using the Automaded GUI Recorder, from
within the Runtime Workbench. I'd like to use the workaround documented
here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=165526
This says that if I add the following to the VM arguments, and I run the
Runtime Workbench, my test will be executed:
-Dtptp.automated.gui=true
-Dtptp.automated.gui.testsuite.plugin=<plugin id that has your test suite in
it>
-Dtptp.automated.gui.testsuite.path=/<path to the test suite within the
plugin>
When I try to run with these arguments, I get an error message: "The
workbench is running in headless TPTP automated GUI mode but the JVM
property tptp.automated.gui.executor is not set."
Anybody has tried this before?
Emmanuel
|
|
|
| Re: tptp.automated.gui workaround, any luck? [message #89891 is a reply to message #89876] |
Mon, 11 December 2006 17:32  |
| Eclipse User |
|
|
|
Originally posted by: emmanuelproulx.yahoo.com
I tried adding the following:
Dtptp.automated.gui.executor=org.eclipse.hyades.test.tools.c ore.internal.plugin.harness.WorkbenchExecutorStub
Now the error is gone BUT nothing gets executed.
I also tried with other executors (TestExecutionHarnessExecutorStub,
ProcessExecutorImpl) without success.
Please advise.
Emmanuel
"Emmanuel Proulx" <emmanuelproulx@yahoo.com> wrote in message
news:elk3ag$ohu$1@utils.eclipse.org...
> I'm trying to execute a test I made using the Automaded GUI Recorder, from
> within the Runtime Workbench. I'd like to use the workaround documented
> here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=165526
>
> This says that if I add the following to the VM arguments, and I run the
> Runtime Workbench, my test will be executed:
> -Dtptp.automated.gui=true
> -Dtptp.automated.gui.testsuite.plugin=<plugin id that has your test suite
> in it>
> -Dtptp.automated.gui.testsuite.path=/<path to the test suite within the
> plugin>
>
> When I try to run with these arguments, I get an error message: "The
> workbench is running in headless TPTP automated GUI mode but the JVM
> property tptp.automated.gui.executor is not set."
>
> Anybody has tried this before?
>
> Emmanuel
>
|
|
|
|
| Re: tptp.automated.gui workaround, any luck? [message #90039 is a reply to message #90025] |
Tue, 12 December 2006 19:24 |
| Eclipse User |
|
|
|
Originally posted by: emmanuelproulx.yahoo.com
I'm using:
Eclipse Build id: I20061206-1721
AGR version 4.2.1
JDK version 1.5.0_08
Emmanuel
"Liz Dancy" <lizdancy@ca.ibm.com> wrote in message
news:elmtbe$jt8$1@utils.eclipse.org...
> The patch and workaround you referenced are based on the 4.2.1 branch of
> the AGR so please ensure you are using 4.2.1 and not the latest release
> for the workaround. In addition, if you could provide the Eclipse SDK
> Build ID (Under Help > About Eclipse SDK) as well as the JRE version you
> are using this would be very helpful in reproducing the problem.
>
> Sincerely,
>
> Liz Dancy
> "Emmanuel Proulx" <emmanuelproulx@yahoo.com> wrote in message
> news:elk4oh$bmg$1@utils.eclipse.org...
>>I tried adding the following:
>> Dtptp.automated.gui.executor=org.eclipse.hyades.test.tools.c ore.internal.plugin.harness.WorkbenchExecutorStub
>>
>> Now the error is gone BUT nothing gets executed.
>>
>> I also tried with other executors (TestExecutionHarnessExecutorStub,
>> ProcessExecutorImpl) without success.
>>
>> Please advise.
>>
>> Emmanuel
>>
>> "Emmanuel Proulx" <emmanuelproulx@yahoo.com> wrote in message
>> news:elk3ag$ohu$1@utils.eclipse.org...
>>> I'm trying to execute a test I made using the Automaded GUI Recorder,
>>> from within the Runtime Workbench. I'd like to use the workaround
>>> documented here:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=165526
>>>
>>> This says that if I add the following to the VM arguments, and I run the
>>> Runtime Workbench, my test will be executed:
>>> -Dtptp.automated.gui=true
>>> -Dtptp.automated.gui.testsuite.plugin=<plugin id that has your test
>>> suite in it>
>>> -Dtptp.automated.gui.testsuite.path=/<path to the test suite within the
>>> plugin>
>>>
>>> When I try to run with these arguments, I get an error message: "The
>>> workbench is running in headless TPTP automated GUI mode but the JVM
>>> property tptp.automated.gui.executor is not set."
>>>
>>> Anybody has tried this before?
>>>
>>> Emmanuel
>>>
>>
>>
>
>
|
|
|
| Re: tptp.automated.gui workaround, any luck? [message #90328 is a reply to message #90039] |
Thu, 14 December 2006 15:12 |
 Chris McGee
Messages: 99
Registered: July 2009 |
Member |
|
|
Hi Emmanuel,
You shouldn't need an executor to use this patch. It bypasses all of
those things.
I could imagine that one of two things are happening. Either eclipse is
running with the standard 4.2.1 AGR (without the patch) or for some
reason it is not receiving two of the system properties that you have
specified as VM arguments.
Here is how I have been using this patch:
1) I check out the 4.2.1 version of the TPTP AGR from CVS into my workspace
2) I apply the patch to the source code
3) I open up my runtime configuration dialog (Run->Run...)
4) I create a new runtime workbench configuration (using a different
workspace path from my usual runtime workbench
"${workspace_loc}/../runtime-tptp-agr-test")
5) I specify that it should "Clear workspace data before launching"
6) In the arguments tab I add the following VM arguments (these point to
my test suite that I have in my workspace, which will be loaded into the
runtime workbench as a plugin)
-Dtptp.automated.gui=true
-Dtptp.automated.gui.testsuite.plugin=org.foobar.someplugin
-Dtptp.automated.gui.testsuite.path=/test-resources/MyTestSu ite.testsuite
Now, when I run this runtime workbench, it automatically begins
executing my test suite and shows a dialog when it is finished running
the tests.
You don't need an agent controller with this setup. :-)
I hope that this helps,
Chris McGee
Emmanuel Proulx wrote:
> I'm using:
> Eclipse Build id: I20061206-1721
>
> AGR version 4.2.1
>
> JDK version 1.5.0_08
>
> Emmanuel
>
> "Liz Dancy" <lizdancy@ca.ibm.com> wrote in message
> news:elmtbe$jt8$1@utils.eclipse.org...
>> The patch and workaround you referenced are based on the 4.2.1 branch of
>> the AGR so please ensure you are using 4.2.1 and not the latest release
>> for the workaround. In addition, if you could provide the Eclipse SDK
>> Build ID (Under Help > About Eclipse SDK) as well as the JRE version you
>> are using this would be very helpful in reproducing the problem.
>>
>> Sincerely,
>>
>> Liz Dancy
>> "Emmanuel Proulx" <emmanuelproulx@yahoo.com> wrote in message
>> news:elk4oh$bmg$1@utils.eclipse.org...
>>> I tried adding the following:
>>> Dtptp.automated.gui.executor=org.eclipse.hyades.test.tools.c ore.internal.plugin.harness.WorkbenchExecutorStub
>>>
>>> Now the error is gone BUT nothing gets executed.
>>>
>>> I also tried with other executors (TestExecutionHarnessExecutorStub,
>>> ProcessExecutorImpl) without success.
>>>
>>> Please advise.
>>>
>>> Emmanuel
>>>
>>> "Emmanuel Proulx" <emmanuelproulx@yahoo.com> wrote in message
>>> news:elk3ag$ohu$1@utils.eclipse.org...
>>>> I'm trying to execute a test I made using the Automaded GUI Recorder,
>>>> from within the Runtime Workbench. I'd like to use the workaround
>>>> documented here:
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=165526
>>>>
>>>> This says that if I add the following to the VM arguments, and I run the
>>>> Runtime Workbench, my test will be executed:
>>>> -Dtptp.automated.gui=true
>>>> -Dtptp.automated.gui.testsuite.plugin=<plugin id that has your test
>>>> suite in it>
>>>> -Dtptp.automated.gui.testsuite.path=/<path to the test suite within the
>>>> plugin>
>>>>
>>>> When I try to run with these arguments, I get an error message: "The
>>>> workbench is running in headless TPTP automated GUI mode but the JVM
>>>> property tptp.automated.gui.executor is not set."
>>>>
>>>> Anybody has tried this before?
>>>>
>>>> Emmanuel
>>>>
>>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.01909 seconds
] 
Search
Help
Register
Login
Home
