Home » Eclipse Projects » Remote Application Platform (RAP) » RAP UI Testing (automation)
| RAP UI Testing (automation) [message #48414] |
Wed, 19 September 2007 21:39  |
Eclipse User |
|
|
|
Originally posted by: just4lists.nospammail.net
This is a multi-part message in MIME format.
------=_NextPart_000_004E_01C7FB0D.F5D62FF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
From the patch posted at http://wiki.eclipse.org/RapUITesting
writer.set("UserData", new String[] {newValue, "selenium"});
Shouldn't it be?
writer.set("UserData", new String[] {"selenium", newValue});
I'm doing some research to fix the IDs in the rendered html code (needed =
for test automation). If you have any further ideas on this, please use =
this thread to share them.
Best regards,
Joel Oliveira
------=_NextPart_000_004E_01C7FB0D.F5D62FF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16527" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DVerdana size=3D2>From the patch posted at =
</FONT><A=20
href=3D"http://wiki.eclipse.org/RapUITesting"><FONT face=3DVerdana=20
size=3D2>http://wiki.eclipse.org/RapUITesting</FONT></A></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2><EM>writer.set("UserData", new =
String[]=20
{<STRONG>newValue, "selenium"</STRONG>});</EM><BR></FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2>Shouldn't it be?</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2><EM>writer.set("UserData", new =
String[]=20
{<STRONG>"selenium", newValue</STRONG>});</EM></FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2>I'm doing some research to fix the =
IDs in the=20
rendered html code (needed for test automation). If you have any further =
ideas=20
on this, please use this thread to share them.</DIV>
<DIV><BR></DIV></FONT>
<DIV><FONT face=3DVerdana size=3D2>Best regards,</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2>Joel =
Oliveira</DIV></FONT></BODY></HTML>
------=_NextPart_000_004E_01C7FB0D.F5D62FF0--
|
|
|
| Re: RAP UI Testing (automation) [message #48444 is a reply to message #48414] |
Wed, 19 September 2007 22:11  |
| Eclipse User |
|
|
|
Originally posted by: just4lists.nospammail.net
From a post in the qooxdoo list:
> Jim Hunter schrieb:
> We just add an id to the controls we want to test using
> ctrl.setHtmlAttribute('id', 'ourID'). I understand that
> setHtmlAttribute is getting changed to setHtmlProperty (at least I
> think this is true) in the very near future.
Best regards,
Joel Oliveira
> "Joel Oliveira" <just4lists@nospammail.net> escreveu na mensagem
> news:fcs4vs$go5$1@build.eclipse.org...
> From the patch posted at http://wiki.eclipse.org/RapUITesting
>
> writer.set("UserData", new String[] {newValue, "selenium"});
>
> Shouldn't it be?
>
> writer.set("UserData", new String[] {"selenium", newValue});
>
> I'm doing some research to fix the IDs in the rendered html code (needed
> for test automation). If you have any further
> ideas on this, please use this thread to share them.
>
>
> Best regards,
>
> Joel Oliveira
|
|
|
| Re: RAP UI Testing (automation) [message #48519 is a reply to message #48444] |
Thu, 20 September 2007 07:55 |
 Benjamin Muskalla
Messages: 237
Registered: July 2009 |
Senior Member |
|
|
Hi Joel,
see comments inline:
Joel Oliveira wrote:
> From a post in the qooxdoo list:
>
>> Jim Hunter schrieb:
>> We just add an id to the controls we want to test using
>> ctrl.setHtmlAttribute('id', 'ourID'). I understand that
>> setHtmlAttribute is getting changed to setHtmlProperty (at least I
>> think this is true) in the very near future.
That's what i suggested in the "Anyone from Qooxdoo on this newsgroup?"
thread. Unfortunately this is a little bit complicated as you have to
hack RAP (or register a PhaseListener) and provide some better
identifier than the existing id. Nice ideas how to say that for example
a button should be called "mytestablebutton" on the client-side? Sure
there are ways but no way which is really nice and non intrusive.
>
> Best regards,
>
> Joel Oliveira
>
>> "Joel Oliveira" <just4lists@nospammail.net> escreveu na mensagem
>> news:fcs4vs$go5$1@build.eclipse.org...
>> From the patch posted at http://wiki.eclipse.org/RapUITesting
>>
>> writer.set("UserData", new String[] {newValue, "selenium"});
>>
>> Shouldn't it be?
>>
>> writer.set("UserData", new String[] {"selenium", newValue});
That's right but this patch step is not needed as the id is assigned
automatically by the WidgetManager on the client-side. Just ask the
widgets for getUserData("id").
>>
>> I'm doing some research to fix the IDs in the rendered html code
>> (needed for test automation). If you have any further
>> ideas on this, please use this thread to share them.
>>
>>
>> Best regards,
>>
>> Joel Oliveira
>
|
|
|
| Re: RAP UI Testing (automation) [message #50213 is a reply to message #48519] |
Thu, 27 September 2007 19:34 |
| Eclipse User |
|
|
|
Originally posted by: just4lists.nospammail.net
Patch submitted.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204859
Comments?
"Benjamin Muskalla" <bmuskalla@innoopract.com> escreveu na mensagem
news:fct967$jlk$1@build.eclipse.org...
> Hi Joel,
>
> see comments inline:
>
> Joel Oliveira wrote:
>> From a post in the qooxdoo list:
>>
>>> Jim Hunter schrieb:
>>> We just add an id to the controls we want to test using
>>> ctrl.setHtmlAttribute('id', 'ourID'). I understand that
>>> setHtmlAttribute is getting changed to setHtmlProperty (at least I
>>> think this is true) in the very near future.
> That's what i suggested in the "Anyone from Qooxdoo on this newsgroup?"
> thread. Unfortunately this is a little bit complicated as you have to hack
> RAP (or register a PhaseListener) and provide some better identifier than
> the existing id. Nice ideas how to say that for example a button should be
> called "mytestablebutton" on the client-side? Sure there are ways but no
> way which is really nice and non intrusive.
>>
>> Best regards,
>>
>> Joel Oliveira
>>
>>> "Joel Oliveira" <just4lists@nospammail.net> escreveu na mensagem
>>> news:fcs4vs$go5$1@build.eclipse.org...
>>> From the patch posted at http://wiki.eclipse.org/RapUITesting
>>>
>>> writer.set("UserData", new String[] {newValue, "selenium"});
>>>
>>> Shouldn't it be?
>>>
>>> writer.set("UserData", new String[] {"selenium", newValue});
> That's right but this patch step is not needed as the id is assigned
> automatically by the WidgetManager on the client-side. Just ask the
> widgets for getUserData("id").
>
>>>
>>> I'm doing some research to fix the IDs in the rendered html code (needed
>>> for test automation). If you have any further
>>> ideas on this, please use this thread to share them.
>>>
>>>
>>> Best regards,
>>>
>>> Joel Oliveira
>>
|
|
|
| Re: RAP UI Testing (automation) [message #50503 is a reply to message #50213] |
Sat, 29 September 2007 13:40 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
to me it seems to be a valid approach to improve the possibilities of
automated testing of RAP UIs. Benny do you agree? But I also think - as the
id generation increases the streams sent from and to the client - we should
add a system property to switch this functionality on and off (standard
would be off). This would not hurt since there is no need for human readable
ids in a non testing environment.
By the way we do not really need the w-prefix of the widgets anymore, do we
(R
|
|
|
| Re: RAP UI Testing (automation) [message #50560 is a reply to message #50503] |
Tue, 02 October 2007 07:25 |
| Eclipse User |
|
|
|
Originally posted by: just4lists.nospammail.net
Comments inline.
Best regards,
Joel Oliveira
"Frank Appel" <fappel@innoopract.com> escreveu na mensagem
news:fdlkkc$sgj$1@build.eclipse.org...
> Hi,
>
> to me it seems to be a valid approach to improve the possibilities of
> automated testing of RAP UIs. Benny do you agree? But I also think - as
> the id generation increases the streams sent from and to the client - we
> should add a system property to switch this functionality on and off
> (standard would be off). This would not hurt since there is no need for
> human readable ids in a non testing environment.
This is true. It should be just a small amount of extra info... but I
agree... it's always extra info that is not always needed.
> By the way we do not really need the w-prefix of the widgets anymore, do
> we (Rüdiger?), so we could actually use only the integer values of from
> IdGenerator at generall runtime mode (beside that this would break our
> current unit tests...).
I already learned (from previous experiences _:) ) only integer values are
not such a good idea (they get messed up with the array index - never know
if you getting the widget by id or by it's position in the elements array -
but this also dependes on the implementation).
> In case we use different ids for automated UI tests, we could also use
> fully qualified names for the ids and may add some additional
> functionality like whether a button is in radio, check or push mode
> (org.eclipse.swt.widgets.button[radio]4711 as id for example).
I believe that adding the fully qualified name could be overkilling... but
button-radio-4711 looks better.
> One last thing - I think this discussion actually belongs to the rap-dev
> mailing-list. As far as I know, the eclipse-newsgroups are dedicated to
> user questions (in our case people that are developing their application
> by using rap).
Agree. I will post further discussion in the mailing-list.
>
>
> Ciao
> Frank
>
>
> "Joel Oliveira" <just4lists@nospammail.net> schrieb im Newsbeitrag
> news:fdh0kh$n7b$1@build.eclipse.org...
>> Patch submitted.
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=204859
>>
>> Comments?
>>
>> "Benjamin Muskalla" <bmuskalla@innoopract.com> escreveu na mensagem
>> news:fct967$jlk$1@build.eclipse.org...
>>> Hi Joel,
>>>
>>> see comments inline:
>>>
>>> Joel Oliveira wrote:
>>>> From a post in the qooxdoo list:
>>>>
>>>>> Jim Hunter schrieb:
>>>>> We just add an id to the controls we want to test using
>>>>> ctrl.setHtmlAttribute('id', 'ourID'). I understand that
>>>>> setHtmlAttribute is getting changed to setHtmlProperty (at least I
>>>>> think this is true) in the very near future.
>>> That's what i suggested in the "Anyone from Qooxdoo on this newsgroup?"
>>> thread. Unfortunately this is a little bit complicated as you have to
>>> hack RAP (or register a PhaseListener) and provide some better
>>> identifier than the existing id. Nice ideas how to say that for example
>>> a button should be called "mytestablebutton" on the client-side? Sure
>>> there are ways but no way which is really nice and non intrusive.
>>>>
>>>> Best regards,
>>>>
>>>> Joel Oliveira
>>>>
>>>>> "Joel Oliveira" <just4lists@nospammail.net> escreveu na mensagem
>>>>> news:fcs4vs$go5$1@build.eclipse.org...
>>>>> From the patch posted at http://wiki.eclipse.org/RapUITesting
>>>>>
>>>>> writer.set("UserData", new String[] {newValue, "selenium"});
>>>>>
>>>>> Shouldn't it be?
>>>>>
>>>>> writer.set("UserData", new String[] {"selenium", newValue});
>>> That's right but this patch step is not needed as the id is assigned
>>> automatically by the WidgetManager on the client-side. Just ask the
>>> widgets for getUserData("id").
>>>
>>>>>
>>>>> I'm doing some research to fix the IDs in the rendered html code
>>>>> (needed for test automation). If you have any further
>>>>> ideas on this, please use this thread to share them.
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Joel Oliveira
>>>>
>>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 22:14:12 GMT 2024
Powered by FUDForum. Page generated in 0.03955 seconds |
] 
Search
Help
Register
Login
Home
