Re: Abbot question

Hi Doug,

   Java UI Testing in the Abbot docs refers to UIs which are directly  
generated by Java, ie applets and thick clients.  Java-based back-ends  
which generate markup for presentation in a browser require browser- 
focused testing, so Abbot does not help in those cases.

On Jan 5, 2009, at 11:56 AM, Meil, Doug wrote:

> Hi there Timothy-
>
> I have a question about Abbot that might be a good addition for the  
> FAQ page…
>
> http://abbot.sourceforge.net/doc/FAQ.shtml
>
> … the website states “Abbot helps you test your Java UI”.  What do  
> you mean, specifically, by “Java UI”?
>
> Applets?  Thick-client (i.e., native) Java applications?  My guess  
> is “yes” for both.
>
> But what about web-applications?  Specifically, web applications  
> developed in Java?  (e.g., Servlets, struts/servlets, Google Web  
> Toolkit, etc.).  It doesn’t appear that this is intended for Abbot,  
> at least from what I can read in the online docs.
>
> Sorry it’s kind of a basic question, but a lot of tools say they  
> support “Java UI testing” but you kind of have to read the fine  
> print to find out what they mean, exactly.

tester class questions

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

_______________________________________________
abbot-users mailing list
abbot-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/abbot-users

Re: tester class questions

Thanks Grant.

That's pretty much what I thought.

I would prefer to use the xxTester classes, but have had problems
where they can't find a component or can't find the popup for the component,
although I used the finder to find the component and can't manipulate it 
with the component method.

Curt

-----Original Message-----
From: Grant Birchmeier [mailto:gbirchmeier <at> connamara.com]
Sent: Wednesday, January 14, 2009 2:51 PM
To: Hicks, Curt
Subject: Re: [abbot-users] tester class questions

As far as I can tell, there is no point to having more than one of any
tester class.

Regarding tester vs. methods, from my experience the tester classes
simulate user actions, i.e. if you use a JButtonTester to click a
button, the tester actually moves the mouse pointer and executes a
click.  The methods... just do what Java can do programmatically.
Since you're trying to simulate a user using your UI, you should use
the testers.

-Grant

On Wed, Jan 14, 2009 at 2:27 PM, Hicks, Curt <Curt.Hicks <at> us.fujitsu.com> wrote:
>
> Is there any point to having more than one instance of a particular tester
> class ?
> e.g. once I've gotten a JComboBoxTester do I need to get another one, or can
> I just
> continue to reuse the first one ?
>
> what is the difference between using the JComboBoxTester to select an index,
> and using the comboBox method directly ?
> It appears that  the tester classes generate events on the AWT thread ?  Is
> this
> the only difference ?
>
> Thanks very much.
>
> Regards,  Curt Hicks
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> abbot-users mailing list
> abbot-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/abbot-users
>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Re: tester class questions

On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:

>
> Is there any point to having more than one instance of a particular  
> tester class ?
> e.g. once I've gotten a JComboBoxTester do I need to get another  
> one, or can I just
> continue to reuse the first one ?
>
A single one will suffice.

> what is the difference between using the JComboBoxTester to select  
> an index,
> and using the comboBox method directly ?
> It appears that  the tester classes generate events on the AWT  
> thread ?  Is this
> the only difference ?
>
In the case of the combo box, notification events will fire in both  
cases (most Swing components do *not* fire notifications if you change  
their state).

When invoked programmatically, the combo list popup is never activated  
or selected.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Re: tester class questions

I'm using debug statements as I develop my tests.
I can see that what's printing in the debug statements, 
e.g. the number of items in a combobox pulldown, the 
selected item, or the items available for selection. 

(Note that the code being tested DOES change the possible
combobox values based on othe values.) 

Is this because I'm using the comboBox methods rather than
the Tester methods ?

Thanks very much.

Regards, 
Curt Hicks 

-----Original Message-----
From: Timothy Wall [mailto:twall <at> users.sf.net]
Sent: Wednesday, January 14, 2009 3:09 PM
To: Hicks, Curt
Cc: abbot-users <at> lists.sourceforge.net
Subject: Re: [abbot-users] tester class questions

On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:

>
> Is there any point to having more than one instance of a particular  
> tester class ?
> e.g. once I've gotten a JComboBoxTester do I need to get another  
> one, or can I just
> continue to reuse the first one ?
>
A single one will suffice.

> what is the difference between using the JComboBoxTester to select  
> an index,
> and using the comboBox method directly ?
> It appears that  the tester classes generate events on the AWT  
> thread ?  Is this
> the only difference ?
>
In the case of the combo box, notification events will fire in both  
cases (most Swing components do *not* fire notifications if you change  
their state).

When invoked programmatically, the combo list popup is never activated  
or selected.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Re: tester class questions

I don't understand what you're asking.

On Jan 14, 2009, at 6:09 PM, Hicks, Curt wrote:

>
> I'm using debug statements as I develop my tests.
> I can see that what's printing in the debug statements,
> e.g. the number of items in a combobox pulldown, the
> selected item, or the items available for selection.
>
> (Note that the code being tested DOES change the possible
> combobox values based on othe values.)
>
> Is this because I'm using the comboBox methods rather than
> the Tester methods ?
>
>
> Thanks very much.
>
> Regards,
> Curt Hicks
>
>
> -----Original Message-----
> From: Timothy Wall [mailto:twall <at> users.sf.net]
> Sent: Wednesday, January 14, 2009 3:09 PM
> To: Hicks, Curt
> Cc: abbot-users <at> lists.sourceforge.net
> Subject: Re: [abbot-users] tester class questions
>
>
>
> On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:
>
>>
>> Is there any point to having more than one instance of a particular
>> tester class ?
>> e.g. once I've gotten a JComboBoxTester do I need to get another
>> one, or can I just
>> continue to reuse the first one ?
>>
> A single one will suffice.
>
>
>> what is the difference between using the JComboBoxTester to select
>> an index,
>> and using the comboBox method directly ?
>> It appears that  the tester classes generate events on the AWT
>> thread ?  Is this
>> the only difference ?
>>
> In the case of the combo box, notification events will fire in both
> cases (most Swing components do *not* fire notifications if you change
> their state).
>
> When invoked programmatically, the combo list popup is never activated
> or selected.
>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Re: tester class questions

I don't follow your question.  What is "this" in your question?

On Wed, Jan 14, 2009 at 5:09 PM, Hicks, Curt <Curt.Hicks <at> us.fujitsu.com> wrote:
>
> I'm using debug statements as I develop my tests.
> I can see that what's printing in the debug statements,
> e.g. the number of items in a combobox pulldown, the
> selected item, or the items available for selection.
>
> (Note that the code being tested DOES change the possible
> combobox values based on othe values.)
>
> Is this because I'm using the comboBox methods rather than
> the Tester methods ?
>
>
> Thanks very much.
>
> Regards,
> Curt Hicks
>
>
> -----Original Message-----
> From: Timothy Wall [mailto:twall <at> users.sf.net]
> Sent: Wednesday, January 14, 2009 3:09 PM
> To: Hicks, Curt
> Cc: abbot-users <at> lists.sourceforge.net
> Subject: Re: [abbot-users] tester class questions
>
>
>
> On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:
>
>>
>> Is there any point to having more than one instance of a particular
>> tester class ?
>> e.g. once I've gotten a JComboBoxTester do I need to get another
>> one, or can I just
>> continue to reuse the first one ?
>>
> A single one will suffice.
>
>
>> what is the difference between using the JComboBoxTester to select
>> an index,
>> and using the comboBox method directly ?
>> It appears that  the tester classes generate events on the AWT
>> thread ?  Is this
>> the only difference ?
>>
> In the case of the combo box, notification events will fire in both
> cases (most Swing components do *not* fire notifications if you change
> their state).
>
> When invoked programmatically, the combo list popup is never activated
> or selected.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> abbot-users mailing list
> abbot-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/abbot-users
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Fwd: daily report

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

_______________________________________________
abbot-users mailing list
abbot-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/abbot-users

Re: tester class questions

Sorry !  The missing part is that what I see displayed in 
the GUI, does not match the debug statements. Presumably 
because I'm not using the tester methods, but operating 
directly on combobox.

Curt

-----Original Message-----
From: Grant Birchmeier [mailto:gbirchmeier <at> connamara.com]
Sent: Wednesday, January 14, 2009 6:09 PM
To: Hicks, Curt
Cc: Timothy Wall; abbot-users <at> lists.sourceforge.net
Subject: Re: [abbot-users] tester class questions

I don't follow your question.  What is "this" in your question?

On Wed, Jan 14, 2009 at 5:09 PM, Hicks, Curt <Curt.Hicks <at> us.fujitsu.com> wrote:
>
> I'm using debug statements as I develop my tests.
> I can see that what's printing in the debug statements,
> e.g. the number of items in a combobox pulldown, the
> selected item, or the items available for selection.
>
> (Note that the code being tested DOES change the possible
> combobox values based on othe values.)
>
> Is this because I'm using the comboBox methods rather than
> the Tester methods ?
>
>
> Thanks very much.
>
> Regards,
> Curt Hicks
>
>
> -----Original Message-----
> From: Timothy Wall [mailto:twall <at> users.sf.net]
> Sent: Wednesday, January 14, 2009 3:09 PM
> To: Hicks, Curt
> Cc: abbot-users <at> lists.sourceforge.net
> Subject: Re: [abbot-users] tester class questions
>
>
>
> On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:
>
>>
>> Is there any point to having more than one instance of a particular
>> tester class ?
>> e.g. once I've gotten a JComboBoxTester do I need to get another
>> one, or can I just
>> continue to reuse the first one ?
>>
> A single one will suffice.
>
>
>> what is the difference between using the JComboBoxTester to select
>> an index,
>> and using the comboBox method directly ?
>> It appears that  the tester classes generate events on the AWT
>> thread ?  Is this
>> the only difference ?
>>
> In the case of the combo box, notification events will fire in both
> cases (most Swing components do *not* fire notifications if you change
> their state).
>
> When invoked programmatically, the combo list popup is never activated
> or selected.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> abbot-users mailing list
> abbot-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/abbot-users
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

Re: tester class questions -

I figured it out. 

I was finding the combobox and then changing parameters elsewhere that
affected the allowed values in the combobox.  

Finding the comboBox afterwards solved this particular problem.

Thanks for your help. 

Curt 

-----Original Message-----
From: Grant Birchmeier [mailto:gbirchmeier <at> connamara.com]
Sent: Thursday, January 15, 2009 9:35 AM
To: Hicks, Curt
Subject: Re: [abbot-users] tester class questions

Can you paste a simplified fragment of code that illustrates your problem?

-Grant

On Thu, Jan 15, 2009 at 8:38 AM, Hicks, Curt <Curt.Hicks <at> us.fujitsu.com> wrote:
> Sorry !  The missing part is that what I see displayed in
> the GUI, does not match the debug statements. Presumably
> because I'm not using the tester methods, but operating
> directly on combobox.
>
> Curt
>
> -----Original Message-----
> From: Grant Birchmeier [mailto:gbirchmeier <at> connamara.com]
> Sent: Wednesday, January 14, 2009 6:09 PM
> To: Hicks, Curt
> Cc: Timothy Wall; abbot-users <at> lists.sourceforge.net
> Subject: Re: [abbot-users] tester class questions
>
>
> I don't follow your question.  What is "this" in your question?
>
>
> On Wed, Jan 14, 2009 at 5:09 PM, Hicks, Curt <Curt.Hicks <at> us.fujitsu.com> wrote:
>>
>> I'm using debug statements as I develop my tests.
>> I can see that what's printing in the debug statements,
>> e.g. the number of items in a combobox pulldown, the
>> selected item, or the items available for selection.
>>
>> (Note that the code being tested DOES change the possible
>> combobox values based on othe values.)
>>
>> Is this because I'm using the comboBox methods rather than
>> the Tester methods ?
>>
>>
>> Thanks very much.
>>
>> Regards,
>> Curt Hicks
>>
>>
>> -----Original Message-----
>> From: Timothy Wall [mailto:twall <at> users.sf.net]
>> Sent: Wednesday, January 14, 2009 3:09 PM
>> To: Hicks, Curt
>> Cc: abbot-users <at> lists.sourceforge.net
>> Subject: Re: [abbot-users] tester class questions
>>
>>
>>
>> On Jan 14, 2009, at 3:27 PM, Hicks, Curt wrote:
>>
>>>
>>> Is there any point to having more than one instance of a particular
>>> tester class ?
>>> e.g. once I've gotten a JComboBoxTester do I need to get another
>>> one, or can I just
>>> continue to reuse the first one ?
>>>
>> A single one will suffice.
>>
>>
>>> what is the difference between using the JComboBoxTester to select
>>> an index,
>>> and using the comboBox method directly ?
>>> It appears that  the tester classes generate events on the AWT
>>> thread ?  Is this
>>> the only difference ?
>>>
>> In the case of the combo box, notification events will fire in both
>> cases (most Swing components do *not* fire notifications if you change
>> their state).
>>
>> When invoked programmatically, the combo list popup is never activated
>> or selected.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> abbot-users mailing list
>> abbot-users <at> lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/abbot-users
>>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword