Mapping Guide

Mapping is the means by which PARADIGM-ME identifies which web control corresponds to a given element. Each UITP element can only have one mapping.


Usage

  1. On the properties section of the element to map, open the 'Fields' dialog
  2. Select 'Map Field'
  3. At this point, a dialog containing all the elements and fields of that model level should appear. Insert the mapping URL if needed (starting with 'http:'), select the browser, and check the fields to map.
  4. Hit 'Ok'
  5. After the webbrowser opens and the page is completely loaded, right-click on the upper right corner of the page. At this point a small dialog should appear that allows to map each field accoding to one mapping mode.


Dialog Options

  • Field: the field to be mapped on that iteration
  • Mapping Mode: mapping mode to be used (see next section)
  • Force Refresh: forces PARADIGM-ME to gather data on all elements present on the webpage. By default, it performs this action when mapping the first element, and each time it detects a URL change.
  • Cancel All: cancels mapping session, and preserves previous mapping data.
  • Undo: undo's last mapping made. Field previously mapped will be available on the 'Field' dropdown again. Can be used to undo all actions in that mapping section.
  • Map Field: maps the selected field with the chosen mapping mode.
  • Finish: terminates mapping session. All previous mapping data is substituted with the new one (if field was mapped in this session), or erased.


Mapping Modes


Point
  • Use-case: Click in a fixed location by using coordinates. Used for accessing dynamic elements that cannot be pinpointed by image alone. E.g., a table with dynamic elements, where each row has its own action icon (checkbox, edit, delete, etc).
  • Target UITPs: Call
  • Mode of Operation: Right-click on the point on the website that should be activated.
  • Execution: Mouse click on the captured coordinates.
  • Order of tools used in execution: Sikuli (coordinates).
Point Sequence
  • Use-case: execute web elements only made visible by mouse hovering (e.g., CSS menus).
  • Target UITPs: Call
  • Mode of Operation: Right-click the first point/element to be clicked, then the second, and so on, until the sequence is complete. Click ESC to finish the sequence.
  • Execution: The elements in the sequence will be hovered over, until the last one is reached. The very last element will be clicked.
  • Order of tools used in execution: Selenium (webelement), Sikuli (coordinates)
Area
  • Use-case: Default mapping mode. Used for practically any type of webelement that has corresponding HTML code (i.e., excludes pure CSS or JS elements).
  • Target UITPs: All
  • Mode of Operation: Right-click on the upper left corner of the area to capture, and drag the mouse until its bottom right corner. The web element to capture must be fully contained within this rectangle. Saving a screenshot enables Sikuli to use image-recognition as a backup in case Selenium fails.
  • Execution: The elements will be executed according to the type of their UITP.
  • Order of tools used in execution: Selenium (webelement), Sikuli (image recognition)

Notes:

  1. Since Sikuli always tries to interact with the center of an image, make sure the control to be executed is located roughly in the center of the area mapped.
  2. When mapping elements like input boxes, checkboxes or comboboxes, make sure to include the its tag in the area captured.
Group Area

:!: to be implemented

  • Use-case: Map a group of web elements as a single UITP. Useful for clicking in a single link in a list without having to map each link to its own UITP.
  • Target UITPs: Call


paradigmme/user_manual/mapping.txt · Last modified: 2014/02/02 23:01 by lvilela