TAST DokuWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Objects Identification ======

{{:TAST-icon.png?nolink&70|}}

When working with an automation tool, it is very important to be able to identify objects and work with them. Otherwise, the automation tool will not know where to click or type.

For solving this issue, normally, the object properties are used. Those are some of the attributes, identifications, names, etc... that every object uses for being recognized and modified.

As TAST user, it is possible to work with them. After creating the messages (let us use the CLICK message as an example), and the parameters needed for it (for instance, clicking on the LOGIN button), we can select how to identify the button. 

As it is shown in the image beside, the dropdown "Search by" gives us the option of choosing between:

  * Class Name
  * Css Selector
  * Id
  * Link Text
  * NAme
  * Partial Link Text
  * Tag Name
  * XPath

{{:Search_by_eng.png?nolink&2500|}}

With every one of them, TAST user will have to fill out the field "Element" at the right side, that will contain the value of the option selected in "Search by". For example, if we want to use the attribute "Id" for the Login button, we will have to write in the element field, the ID of the button itself.
 
Nevertheless, for avoid complications and problems while running the test, we have to make sure that the attribute we choose defines UNIQUELY the button (or other element) we want to work with. For instance, if the webpage has two different buttons with the same Tag Name, the user needs to avoid the usage of Tag Name property for its definition (otherwise, the automatic test will not know which one of them is the correct one and, so, it will fail). Since these parameters are needed to be __unique__, there are two options in TAST to help us to make it happen ([[XPath]] and [[CSS Selector]]).

===== Tools for finding selectors: =====

==== Checking Selectors: ====

Google Chrome explorer gives us the chance to check if a CSS Selector or a Xpath is uniquely defined. For doing this, the procedure is as follows:

  * Open Google Chrome, and navigate to the webpage that will be tested.
  * Press F12, and after that press CTRL + F (Strg+F in German keyboards).
  * A search bar appears downwards. Use it to introduce the Xpath or CSS selector, and at the right side will appear a number "n/n" if this number is 1/1, the element is defined uniquely.

==== Selectors Finder Tools: ====

Also, for ease the way of work with this attributes, in case of need, user can download here {{Fire-IEBrowser1.4.xls}} an __excel sheet__ that helps to choose the proper identifier.

The working of this tool is as follows:

  * First of all, the excel book needs some permissions (for granting them, click on "Enable Content", 

{{:excel permissions_eng.png?nolink&400|}}

  * Then, a popup comes out saying "FIRE - IE BROWSER - WEB ELEMENT DETAILS". Click on "Proceed.."

  * After that, an explorer opens up, only by introducing the URL and clicking in Load, the user can be able to click (with the right mouse button) in the desired element. A pop up asks for a name to classify the element (the user can choose the one easier to remind).

  * When all the elements needed are clicked and named, after closing the explorer, the user can see a complete list with all the elements chosen before, and the main used attributes and identifiers (XPath, CSS, ID and name), and the type of element.

**Please take care to ensure that the CSS or the Name are Unique before using them, to avoid errors in the test launch.**

{{:google_eng.png?nolink&1500|}}
TAST DokuWiki

User Tools

Site Tools

Page Tools
