Search

Understanding Test Actions

Functionize offers a wide variety of Test Actions to automate testing of your application under test (AUT). There are two categories of Test Actions that we will provide details for below: Element-based and Non-Element-based.

Architect Test Actions

Certain Test Actions are added automatically by Architect during recording, such as Pageinit, every time a URL opens or reloads. Some Test Actions, such as opening the Email Reader tool or Not on Page, are available to add via Architect during initial recording or Local Edit.

Inserting Test Actions

Functionize has a feature called Quick Add  that makes it easy to insert Test Actions without having to record with Architect or regenerate with Create Agent. Element-based Test Actions can be added to existing tests through the Slider View. Here the element can be selected and associated attributes set from the last-run screenshot. Non-Element-based Test Actions can be added to existing tests from the Test Details page as well as the Slider View.

Editing Test Actions

The Test Action Settings for both Element-based and Non-Element-based Test Actions can be viewed and edited in both the Test Details page and Slider View.

Actions List

This list contains all Test Actions available in Functionize automated tests, as well as the Test Action Settings available for each by default. Click the name of any Test Action to jump down to see the default Test Action Setting details.

Element-based Test Actions

  • Click: Click an element on the webpage.
  • Contextswitch: Added to a saved test case to denote switching context, such as browser tabs or iFrames.
  • Doubleclick: Double-click an element on the webpage.
  • Dragby: Track a drag via mouse coordinates.
  • Enter: Add an Enter keypress.
  • ESignature: Enter an E-signature item into a canvas element.
  • Hover: Move the mouse pointer over an application element with ‘on-hover’ activations.
  • Html5dragdrop: Drag and drop HTML5 elements provided by the browser.
  • Input: Enter test data into an element within the application under test.
  • Rightclick: Right-click an element within the application under test.
  • Scroll: Move to new coordinates on the webpage.
  • Select: Select a specific webpage element, such as a drop-down list.
  • Textselect: Select (highlight) text on a webpage.
  • Upload: Upload a static or dynamic file to the application under test.
  • Verify: Verify attributes or CSS properties of any webpage elements.
  • Verify-Visual Verification: Perform a visual check on individual webpage elements based on screenshots from a Baseline or a Previous Step.

Non-Element-based Test Actions

  • Alert: Click OK on a JavaScript alert pop-up modal.
  • Apicall: Open the Functionize API Explorer tool for testing API calls.
  • Break: Pause or stop test execution at the specified point.
  • Conditional: Add custom JavaScript to return a true/false statement. If it returns true, the conditional step executes.
  • Confirmation: Click OK or Cancel on a pop-up modal.
  • Continue: Add custom JavaScript to return a true/false statement, if returns true, the loop will continue.
  • Customcode: Add custom JavaScript functions for advanced testing needs.
  • DBExplorer: Open the Functionize DB Explorer tool for testing backend databases.
  • Download: Download a file from the application under test.
  • Emailreceive: Open the Functionize Email Reader tool.
  • Extension-curl: Call cURL commands to call an API as part of a test execution.
  • Extension-curl extension: Users should be able to copy/paste cURL commands directly from Postman.
  • Extension-Postman Collection: Postman Collection: Users can access Postman Collections via import of your JSON file.
  • FileViewer: Open the Functionize File Viewer tool.
  • Keypress: Add a keypress as part of test execution, such as an arrow key.
  • Loop: Perform a set of test actions a specific number of times or based on adding custom JavaScript to determine when a loop should continue to execute or exit.
  • Mousemove: Moves the mouse pointer to specified screen coordinates.
  • Navigate: Direct the test to a new URL.
  • Notonpage: Confirm an item does not exist on a webpage.
  • Pageinit: Added by Architect every time a page is initialized.
  • Prompt: Input text into a webpage prompt modal.
  • Resize: Resize the browser window.
  • SetCookie: Injecting cookie data into the application under test during test execution.
  • SetHTMLStorage: Injecting HTML5 data into the application under test during test execution.
  • SetVariable: Using a Functionize Expression to store data in a variable to be used later in the same test (Local Variable) or other tests (Project Variable).
  • Smsreceive: Open the Functionize SMS Reader tool to receive a message.
  • Smssend: Open the Functionize SMS Reader tool to send a message.
  • Urlchange: Added by Architect to direct the test to a new URL.
  • VerifyVariable: Verify contents of Variables created by SetVariable action type.
  • Vispagechk: Perform a full-page visual check based on screenshots of a Baseline or a Previous Step.
  • Wait: Set time (in milliseconds) to pause the execution of a test in order to wait for backend processing to complete. This Action Type has SmartWait capabilities to continue the test if network calls complete before wait time.