Customizing Executors

An Executor is the way in which Functionize interacts with elements on a web page. Different webpages require different types of Executors to be used. This is because Selenium alone, or javascript alone are not sufficient to cover all methods of interaction with a particular element and every edge case. 

Executors are required on all elements, but vary the most on Click or Input actions. 

Typically, executors are set automatically for each action during execution. However, at times a Click or Input action may not work without additional guidance. When a Click or Input doesn't work as expected, we recommend trying other executors on the site under test. 

We support the following types of Executors:

  • ML based (default) We determine to the best of our ability what executor to use
  • Selenium WebDriver
  • Native Javascript
  • Native Operating System
  • Native Javascript, By Coordinate (NOTE: X & Y are automatically created when modeling the test)
  • Native OS, By Coordinate (NOTE: X & Y are automatically created when modeling the test)

To Access Executors

There are two means by which to access executors:

  1. Via Slider View - When viewing the details of an executed test in the slider, you can now click on the cog icon to access some common settings of the test case. When the cog icon is clicked, you will have quick access to modify the executor, as well as common settings.
    NOTE: Not all settings display in this view. Clicking the Action Log, then navigating to the Settings tab will show you additional settings.
    mceclip0.png
  2. Via Expanded Test Step Details - Executors can also be accessed by expanding the detailed view of the test case here as well
    mceclip0.png

See also Making Steps Optional or Suppressed and Skip Scroll.

 

Executor Options

ML (default): This relies on our execution engine selecting the correct method of interaction with the element.

Operating System: This uses an operating system call to position and click the element.

Operating System By Coordinate (only available for Click actions): This uses an operation system call to position, then uses coordinates* to identify where exactly to click within the element.

Native Javascript: This uses Javascript in the web browser to perform the action on the selected element.

Native Javascript By Coordinate (only available for Click actions): This uses Javascript in the web browser to perform the action, using coordinates* to identify specifically where to click within the element.

Selenium Webdriver: This uses the appropriate driver for the browser to perform the action on the selected element.

Selenium By Coordinate (only available for Click actions): This uses Selenium, where a selector is used identify the element and coordinates (MouseX & MouseY) are used to identify where to click within the element. The coordinates are set in Action Log under the Standard Attributes tab. These can be modified to perform the click elsewhere on the screen.
 -MouseX is the distance to the right of the top left of the viewport.
 -MouseY is the distance beneath the top left of the viewport. 

mceclip0.png