Home » Archived » Test and Performance Tools Platform (TPTP) » Using the Automated GUI Recorder for an executable-supported Eclipse plugin
| Using the Automated GUI Recorder for an executable-supported Eclipse plugin [message #47814] |
Wed, 21 December 2005 14:11  |
Eclipse User |
|
|
|
Hi,
My application is an executable that has a plug-in for Eclipse (for its UI).
In order to run the application, the executable must be launched first. The
executable starts a JVM with some start-up class that invokes Eclipse
(org.eclipse.launcher.Main) with some arguments that are read from a file.
(The arguments for the JVM are also read from a file.)
I am trying to use the AGR to test the application's plug-in, without
success for now. Here's what I have tried to do, please let me know where
I'm wrong or what's missing. (Are there documents explaining the TPTP
testing platform architecture? I have only found very high level ones.)
1. Create a new TPTP test type for my application, and a wizard to create
test suites of that type.
2. Use the registered execution components provided by TPTP (for launching a
Java process).
3. Create a new ExecutableObjectAdapter that sets the name of the executable
and the command-line arguments to those required for my application. The
executable object adapter creates input files with JVM arguments and Eclipse
arguments, which are the same as those created by the AGR executable object
adapter:
JVM: -Dtptp.automated.gui=true -Dtptp.automated.gui.resource.id=... -Dtptp.automated.gui.executor=...
Eclipse: -data TPTP-Auto-Workspace-...
These input files will be used by the application's executable to start
the JVM and Eclipse with the correct parameters.
4. Use the exact same ExecutionEnvironmentAdapter,
ExecutionDeploymentAdapter, launchconfigRunHandler that the AGR uses.
This works up to the initialization of the HyadesRunner. The HyadesRunner
object waits for a command (from the agent controller?) during its
initialization, and the command never arrives. Any idea what may be wrong?
BTW, the test should run on the local host. Remote testing is not needed at
this stage.
Thanks,
Shlomy
|
|
|
| Re: Using the Automated GUI Recorder for an executable-supported Eclipse plugin [message #47844 is a reply to message #47814] |
Thu, 22 December 2005 01:10  |
| Eclipse User |
|
|
|
Can you try using the Agent Controller instead of the integrated version of
the Agent Controller (i.e. download and run "Agent Controller" from TPTP's
download page). There are issues with the integrated version of the Agent
Controller as noted by defect#: 114461
What you have mentioned below sounds correct.
"www.eclipse.org" <sreinstein@e-sim.co.il> wrote in message
news:doc9gt$5lh$1@utils.eclipse.org...
> Hi,
>
> My application is an executable that has a plug-in for Eclipse (for its
UI).
> In order to run the application, the executable must be launched first.
The
> executable starts a JVM with some start-up class that invokes Eclipse
> (org.eclipse.launcher.Main) with some arguments that are read from a file.
> (The arguments for the JVM are also read from a file.)
>
> I am trying to use the AGR to test the application's plug-in, without
> success for now. Here's what I have tried to do, please let me know where
> I'm wrong or what's missing. (Are there documents explaining the TPTP
> testing platform architecture? I have only found very high level ones.)
>
> 1. Create a new TPTP test type for my application, and a wizard to create
> test suites of that type.
> 2. Use the registered execution components provided by TPTP (for launching
a
> Java process).
> 3. Create a new ExecutableObjectAdapter that sets the name of the
executable
> and the command-line arguments to those required for my application. The
> executable object adapter creates input files with JVM arguments and
Eclipse
> arguments, which are the same as those created by the AGR executable
object
> adapter:
>
JVM: -Dtptp.automated.gui=true -Dtptp.automated.gui.resource.id=... -Dtptp.a
utomated.gui.executor=...
> Eclipse: -data TPTP-Auto-Workspace-...
> These input files will be used by the application's executable to start
> the JVM and Eclipse with the correct parameters.
> 4. Use the exact same ExecutionEnvironmentAdapter,
> ExecutionDeploymentAdapter, launchconfigRunHandler that the AGR uses.
>
> This works up to the initialization of the HyadesRunner. The HyadesRunner
> object waits for a command (from the agent controller?) during its
> initialization, and the command never arrives. Any idea what may be wrong?
> BTW, the test should run on the local host. Remote testing is not needed
at
> this stage.
>
> Thanks,
> Shlomy
>
>
|
|
|
| Re: Using the Automated GUI Recorder for an executable-supported Eclipse plugin [message #47874 is a reply to message #47844] |
Thu, 22 December 2005 03:59 |
| Eclipse User |
|
|
|
I should just mention that AGR tests that launch Eclipse directly (such as
the examples in the AGR introduction document) work well with the IAC. I
only experience the problem when I use my application to launch Eclipse.
Shlomy
"Ali Mehregani" <amehrega@ca.ibm.com> wrote in message
news:dodg1g$94n$1@utils.eclipse.org...
> Can you try using the Agent Controller instead of the integrated version
> of
> the Agent Controller (i.e. download and run "Agent Controller" from TPTP's
> download page). There are issues with the integrated version of the Agent
> Controller as noted by defect#: 114461
>
> What you have mentioned below sounds correct.
>
> "www.eclipse.org" <sreinstein@e-sim.co.il> wrote in message
> news:doc9gt$5lh$1@utils.eclipse.org...
>> Hi,
>>
>> My application is an executable that has a plug-in for Eclipse (for its
> UI).
>> In order to run the application, the executable must be launched first.
> The
>> executable starts a JVM with some start-up class that invokes Eclipse
>> (org.eclipse.launcher.Main) with some arguments that are read from a
>> file.
>> (The arguments for the JVM are also read from a file.)
>>
>> I am trying to use the AGR to test the application's plug-in, without
>> success for now. Here's what I have tried to do, please let me know where
>> I'm wrong or what's missing. (Are there documents explaining the TPTP
>> testing platform architecture? I have only found very high level ones.)
>>
>> 1. Create a new TPTP test type for my application, and a wizard to create
>> test suites of that type.
>> 2. Use the registered execution components provided by TPTP (for
>> launching
> a
>> Java process).
>> 3. Create a new ExecutableObjectAdapter that sets the name of the
> executable
>> and the command-line arguments to those required for my application. The
>> executable object adapter creates input files with JVM arguments and
> Eclipse
>> arguments, which are the same as those created by the AGR executable
> object
>> adapter:
>>
>
>
>
>
> JVM: -Dtptp.automated.gui=true -Dtptp.automated.gui.resource.id=... -Dtptp.a
> utomated.gui.executor=...
>> Eclipse: -data TPTP-Auto-Workspace-...
>> These input files will be used by the application's executable to
>> start
>> the JVM and Eclipse with the correct parameters.
>> 4. Use the exact same ExecutionEnvironmentAdapter,
>> ExecutionDeploymentAdapter, launchconfigRunHandler that the AGR uses.
>>
>> This works up to the initialization of the HyadesRunner. The HyadesRunner
>> object waits for a command (from the agent controller?) during its
>> initialization, and the command never arrives. Any idea what may be
>> wrong?
>> BTW, the test should run on the local host. Remote testing is not needed
> at
>> this stage.
>>
>> Thanks,
>> Shlomy
>>
>>
>
>
|
|
|
| Re: Using the Automated GUI Recorder for an executable-supported Eclipse plugin [message #48224 is a reply to message #47844] |
Tue, 27 December 2005 02:49 |
| Eclipse User |
|
|
|
Hi,
I've tried the Agent Controller and it produces the same problem. I found
out that the Executor stub (TestExecutionHarnessExecutorStub.launch)
actually hangs on the call to "waitForProcess" until the timeout is reached.
I assume that "waitForProcess" is waiting for the test process to indicate
that it's ready to communicate, and this does not happen for some reason. It
happens for AGR playback when Eclipse is started directly, but not when it
is started from my executable, even though the AutoGuiRunner is invoked to
start running a script.
Any idea what can be wrong?
Is "waitForProcess" in the executor stub waiting for a message that should
be sent from RemoteComponentSkeleton.initializeEngine0 (the agent created in
the HyadesRunner constructor) that indicates that the test process is up?
Thanks,
Shlomy
"Ali Mehregani" <amehrega@ca.ibm.com> wrote in message
news:dodg1g$94n$1@utils.eclipse.org...
> Can you try using the Agent Controller instead of the integrated version
> of
> the Agent Controller (i.e. download and run "Agent Controller" from TPTP's
> download page). There are issues with the integrated version of the Agent
> Controller as noted by defect#: 114461
>
> What you have mentioned below sounds correct.
>
> "www.eclipse.org" <sreinstein@e-sim.co.il> wrote in message
> news:doc9gt$5lh$1@utils.eclipse.org...
>> Hi,
>>
>> My application is an executable that has a plug-in for Eclipse (for its
> UI).
>> In order to run the application, the executable must be launched first.
> The
>> executable starts a JVM with some start-up class that invokes Eclipse
>> (org.eclipse.launcher.Main) with some arguments that are read from a
>> file.
>> (The arguments for the JVM are also read from a file.)
>>
>> I am trying to use the AGR to test the application's plug-in, without
>> success for now. Here's what I have tried to do, please let me know where
>> I'm wrong or what's missing. (Are there documents explaining the TPTP
>> testing platform architecture? I have only found very high level ones.)
>>
>> 1. Create a new TPTP test type for my application, and a wizard to create
>> test suites of that type.
>> 2. Use the registered execution components provided by TPTP (for
>> launching
> a
>> Java process).
>> 3. Create a new ExecutableObjectAdapter that sets the name of the
> executable
>> and the command-line arguments to those required for my application. The
>> executable object adapter creates input files with JVM arguments and
> Eclipse
>> arguments, which are the same as those created by the AGR executable
> object
>> adapter:
>>
>
>
>
>
> JVM: -Dtptp.automated.gui=true -Dtptp.automated.gui.resource.id=... -Dtptp.a
> utomated.gui.executor=...
>> Eclipse: -data TPTP-Auto-Workspace-...
>> These input files will be used by the application's executable to
>> start
>> the JVM and Eclipse with the correct parameters.
>> 4. Use the exact same ExecutionEnvironmentAdapter,
>> ExecutionDeploymentAdapter, launchconfigRunHandler that the AGR uses.
>>
>> This works up to the initialization of the HyadesRunner. The HyadesRunner
>> object waits for a command (from the agent controller?) during its
>> initialization, and the command never arrives. Any idea what may be
>> wrong?
>> BTW, the test should run on the local host. Remote testing is not needed
> at
>> this stage.
>>
>> Thanks,
>> Shlomy
>>
>>
>
>
|
|
|
Goto Forum:
Current Time: Wed May 07 09:20:33 EDT 2025
Powered by FUDForum. Page generated in 0.04399 seconds |
Home