| [agr] please explain the meaning of this exception [message #112210] |
Tue, 11 September 2007 13:17  |
Eclipse User |
|
|
|
Originally posted by: bmf1972.fastmail.fm
There was an error while running the macro associated with the test
case: New wireXN Project. org.eclipse.core.runtime.CoreException: A
time-out occurred while waiting for the nested shell
org.eclipse.jface.wizard.WizardDialog to complete. It is likely caused
by the absence of the shell.
at
org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell.playback(MacroCommandShell.java:896)
at
org.eclipse.tptp.test.auto.gui.internal.macro.Macro.playback (Macro.java:346)
at
org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.r unMacro(MacroManager.java:574)
at
org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.a ccess$4(MacroManager.java:568)
at
org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager$1 $MacroOperationWrapper.run(MacroManager.java:501)
at java.lang.Thread.run(Thread.java:619)
|
|
|
|
| Re: [agr] please explain the meaning of this exception [message #113087 is a reply to message #112982] |
Sun, 23 September 2007 15:58  |
| Eclipse User |
|
|
|
Originally posted by: bmf1972.fastmail.fm
Hi Liz,
I am running Eclipse 3.3 with the latest TPTP&AGR plugins.
I tried to write a test for the JDT new project wizard and that worked
I tried to write a test for my own Eclipse plugin new project wizard and
that didn't work... It seems that the test workspace is somewhat
different than the workspace used to write the test... Once I changed
the script to invoke the new wizard through the File menu instead of
through the new toolbar selection-button (I cannot find the name of that
toolbar), then it suddenly worked!
The real problem is that those tests are executed behind the scenes and
I, as an user, have no clue about what is going on! If I had the
possibility to execute a selected test step-by-step, while seeing the
workspace under test in real-time, that could be great... Of course, a
detailed log could be helpful.
Adrian.
Liz Dancy wrote:
> I will need some more context as to when this occured and the type of test
> case you were running. If you would like to debug, you can start by
> inserting wait commands around the command that is failing (if you don't
> know at which point it is failing then add several wait commands around the
> suspected area of the Macro). This will allow you to watch the playback and
> hopefully see the failure.
>
> The syntax is " <command type="wait" time-to-wait="5000"/> where "5000" can
> be your choice of how long to wait.
>
> It is likely caused by some discrepancy between the recording environment
> and the playback environment.
>
> For example, if the wizard in question did not open during playback but was
> present during recording, this could cause the exception.
>
> Sincerely,
>
> Liz Dancy
>
> "Adrian Herscu" <bmf1972@fastmail.fm> wrote in message
> news:fc64gf$b6d$1@build.eclipse.org...
>> There was an error while running the macro associated with the test case:
>> New wireXN Project. org.eclipse.core.runtime.CoreException: A time-out
>> occurred while waiting for the nested shell
>> org.eclipse.jface.wizard.WizardDialog to complete. It is likely caused by
>> the absence of the shell.
>> at
>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell.playback(MacroCommandShell.java:896)
>> at
>> org.eclipse.tptp.test.auto.gui.internal.macro.Macro.playback (Macro.java:346)
>> at
>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.r unMacro(MacroManager.java:574)
>> at
>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.a ccess$4(MacroManager.java:568)
>> at
>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager$1 $MacroOperationWrapper.run(MacroManager.java:501)
>> at java.lang.Thread.run(Thread.java:619)
>
>
|
|
|
|
| Re: [agr] please explain the meaning of this exception [message #113188 is a reply to message #113100] |
Mon, 24 September 2007 20:53 |
| Eclipse User |
|
|
|
Originally posted by: bmf1972.fastmail.fm
No. Same machine, same configuration, clean Eclipse+TPTP+AGR
installation, clean workspace, administrative privileges.
Adrian.
Rohit wrote:
> Adrian,
> I suggest that you keep the wait time pretty high. Was the recording and
> actual execution of the test case done on the same machine or machines
> with the same software and hardware configuration? Iam asking this since
> i have noticed that if a test is recorded on a machine of one config and
> replayed on another config it sometimes dosnt work (Not sure why).
>
> Is this your scenario?
>
|
|
|
|
| Re: [agr] please explain the meaning of this exception [message #113594 is a reply to message #113087] |
Mon, 01 October 2007 10:59 |
 Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Adrian,
Currently, inserting artificial wait times and verification hooks (e.g.
logging current state and status) is the only method to debug AGR tests.
However, there is room here for improvement, especially with status
monitoring and logging when executing a test. Please open an enhancement
for adding status monitoring and logging when executing a test:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP%20T esting
Component: Test.Execution.CommonRunner
Paul
"Adrian Herscu" <bmf1972@fastmail.fm> wrote in message
news:fd62fr$ghu$1@build.eclipse.org...
> Hi Liz,
>
> I am running Eclipse 3.3 with the latest TPTP&AGR plugins.
> I tried to write a test for the JDT new project wizard and that worked
> I tried to write a test for my own Eclipse plugin new project wizard and
> that didn't work... It seems that the test workspace is somewhat different
> than the workspace used to write the test... Once I changed the script to
> invoke the new wizard through the File menu instead of through the new
> toolbar selection-button (I cannot find the name of that toolbar), then it
> suddenly worked!
>
> The real problem is that those tests are executed behind the scenes and I,
> as an user, have no clue about what is going on! If I had the possibility
> to execute a selected test step-by-step, while seeing the workspace under
> test in real-time, that could be great... Of course, a detailed log could
> be helpful.
>
> Adrian.
>
> Liz Dancy wrote:
>> I will need some more context as to when this occured and the type of
>> test case you were running. If you would like to debug, you can start by
>> inserting wait commands around the command that is failing (if you don't
>> know at which point it is failing then add several wait commands around
>> the suspected area of the Macro). This will allow you to watch the
>> playback and hopefully see the failure.
>>
>> The syntax is " <command type="wait" time-to-wait="5000"/> where "5000"
>> can be your choice of how long to wait.
>>
>> It is likely caused by some discrepancy between the recording environment
>> and the playback environment.
>>
>> For example, if the wizard in question did not open during playback but
>> was present during recording, this could cause the exception.
>>
>> Sincerely,
>>
>> Liz Dancy
>>
>> "Adrian Herscu" <bmf1972@fastmail.fm> wrote in message
>> news:fc64gf$b6d$1@build.eclipse.org...
>>> There was an error while running the macro associated with the test
>>> case: New wireXN Project. org.eclipse.core.runtime.CoreException: A
>>> time-out occurred while waiting for the nested shell
>>> org.eclipse.jface.wizard.WizardDialog to complete. It is likely caused
>>> by the absence of the shell.
>>> at
>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell.playback(MacroCommandShell.java:896)
>>> at
>>> org.eclipse.tptp.test.auto.gui.internal.macro.Macro.playback (Macro.java:346)
>>> at
>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.r unMacro(MacroManager.java:574)
>>> at
>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.a ccess$4(MacroManager.java:568)
>>> at
>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager$1 $MacroOperationWrapper.run(MacroManager.java:501)
>>> at java.lang.Thread.run(Thread.java:619)
>>
|
|
|
| Re: [agr] please explain the meaning of this exception [message #114142 is a reply to message #113594] |
Thu, 04 October 2007 18:19 |
| Eclipse User |
|
|
|
Originally posted by: bmf1972.fastmail.fm
Added (https://bugs.eclipse.org/bugs/show_bug.cgi?id=205494)
Paul Slauenwhite wrote:
> Hi Adrian,
> Currently, inserting artificial wait times and verification hooks (e.g.
> logging current state and status) is the only method to debug AGR tests.
> However, there is room here for improvement, especially with status
> monitoring and logging when executing a test. Please open an enhancement
> for adding status monitoring and logging when executing a test:
>
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP%20T esting
>
> Component: Test.Execution.CommonRunner
>
> Paul
> "Adrian Herscu" <bmf1972@fastmail.fm> wrote in message
> news:fd62fr$ghu$1@build.eclipse.org...
>> Hi Liz,
>>
>> I am running Eclipse 3.3 with the latest TPTP&AGR plugins.
>> I tried to write a test for the JDT new project wizard and that worked
>> I tried to write a test for my own Eclipse plugin new project wizard and
>> that didn't work... It seems that the test workspace is somewhat different
>> than the workspace used to write the test... Once I changed the script to
>> invoke the new wizard through the File menu instead of through the new
>> toolbar selection-button (I cannot find the name of that toolbar), then it
>> suddenly worked!
>>
>> The real problem is that those tests are executed behind the scenes and I,
>> as an user, have no clue about what is going on! If I had the possibility
>> to execute a selected test step-by-step, while seeing the workspace under
>> test in real-time, that could be great... Of course, a detailed log could
>> be helpful.
>>
>> Adrian.
>>
>> Liz Dancy wrote:
>>> I will need some more context as to when this occured and the type of
>>> test case you were running. If you would like to debug, you can start by
>>> inserting wait commands around the command that is failing (if you don't
>>> know at which point it is failing then add several wait commands around
>>> the suspected area of the Macro). This will allow you to watch the
>>> playback and hopefully see the failure.
>>>
>>> The syntax is " <command type="wait" time-to-wait="5000"/> where "5000"
>>> can be your choice of how long to wait.
>>>
>>> It is likely caused by some discrepancy between the recording environment
>>> and the playback environment.
>>>
>>> For example, if the wizard in question did not open during playback but
>>> was present during recording, this could cause the exception.
>>>
>>> Sincerely,
>>>
>>> Liz Dancy
>>>
>>> "Adrian Herscu" <bmf1972@fastmail.fm> wrote in message
>>> news:fc64gf$b6d$1@build.eclipse.org...
>>>> There was an error while running the macro associated with the test
>>>> case: New wireXN Project. org.eclipse.core.runtime.CoreException: A
>>>> time-out occurred while waiting for the nested shell
>>>> org.eclipse.jface.wizard.WizardDialog to complete. It is likely caused
>>>> by the absence of the shell.
>>>> at
>>>> org.eclipse.tptp.test.auto.gui.internal.commands.MacroComman dShell.playback(MacroCommandShell.java:896)
>>>> at
>>>> org.eclipse.tptp.test.auto.gui.internal.macro.Macro.playback (Macro.java:346)
>>>> at
>>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.r unMacro(MacroManager.java:574)
>>>> at
>>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager.a ccess$4(MacroManager.java:568)
>>>> at
>>>> org.eclipse.tptp.test.auto.gui.internal.macro.MacroManager$1 $MacroOperationWrapper.run(MacroManager.java:501)
>>>> at java.lang.Thread.run(Thread.java:619)
>
|
|
|
Powered by
FUDForum. Page generated in 0.03284 seconds
] 
Search
Help
Register
Login
Home
