Attributes in Swing.snapshot output

Question

question

ChrisB asked Nov 15, '10 ChrisB posted Nov 15, '10

Attributes in Swing.snapshot output

Good morning,

When a snapshot command is done in a Swing session XML is returned representing the full hierarchy of components in the AUT. There are attributes in those elements for some of the component properties. For example:

Another attribute that comes through is name, if a component name has been set via the setName() method.

QUESTION: What is the list of properties that will come through as XML attributes? We've got className, name, and what else? This is for customer Pillar Data Systems specifically, but really for anyone doing Swing testing.

Thanks,

Chris

iTest GUI Testing(Web-Java Swing-etc)

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2010-11-15T23:09:30Z

PreetS answered Nov 15, '10 PreetS posted Nov 15, '10

The attributes that appear in the snapshot are the attributes we think could be used to identify a particular control. They vary based on the type of control, and if they are defined in the application.

For labels, you do not see the value of the label because, the most common thing you'd want to do with a label is to get it's text. So if you identify a label by it's text to get it's text.. that would make no sense.

You can, however, override the list of attributes that appear in the snapshot by implementing iTestable

4

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ChrisB commented · Nov 15, 2010 at 11:34 PM

ITestable is an option, and we'll use it if we need to. However, it will be lighter-weight to just use an attribute that we know is going to be included. Can you provide some examples for some of the common component types?

0 ·

PreetS ChrisB commented · Nov 15, 2010 at 11:44 PM

The best option to use is the "name" property. Names act like IDs for swing application.

When in question, add a name

However, here is some attributes that would generally show up. This is not the complete list, but the most common ones:

* All controls have name. This is has the highest priority and should be used when you can

* Most controls may have label, if iTest can associate a label with that control; e.g a label "first name" next to a text box

* Tooltip text appears for most controls as an attribute

* Image src for buttons that have images and no text

* Content Type and URL for Swing editor panes if they are valid

* Text for all sorts of buttons and controls that extend from buttons

* Text of popup menus

* Text for tooltip controls

* Title of frames

* Title and modality of windows and dialogs

0 ·

tlawall PreetS commented · Nov 16, 2010 at 12:07 AM

* Most controls may have label, if iTest can associate a label with that control; e.g a label "first name" next to a text box
* Tooltip text appears for most controls as an attribute

* Image src for buttons that have images and no text

* Content Type and URL for Swing editor panes if they are valid

* Text for all sorts of buttons and controls that extend from buttons

* Text of popup menus

* Text for tooltip controls

* Title of frames

* Title and modality of windows and dialogs

Preet, do all of these items actually show up as XML attributes in the tags, so that they are selectable in the tree with Xpath, or are they properties that I'd have to use queries with "property()" on a describe response?

0 ·

PreetS tlawall commented · Nov 16, 2010 at 12:27 AM

These are the attributes that show up in the XML (if they are valid and present for those controls)

The describe property set is a much much larger set of properties that is not present in the XML

0 ·

question