1. Functionize
  2. User Guide
  3. Test Editing & Debugging

Decision Actions

Follow

Decision Actions are created to make an Action dependent on a previously executed Action. This creates a conditional workflow for one element of your test. 

To facilitate a Decision Action, an optional Verify Action must happen before your conditional Action. The Verify Action must take place first to confirm the absence or presence of the element you are testing. Most commonly this is used with Click and Input Actions to confirm a certain link or field is visible before interacting with the element.

For best results, when recording in Architect be sure to add Verify Actions before interacting with elements that may be part of a conditional test workflow. If you have all the Verify Actions you need, skip to Step 7 below. If you need to add one or more verifications to your test, start at Step 1.  

Create a Decision Action in an Existing Test

  1. Open your Project and select your test to view the Test Details page.

  2. Click View Results to open Slider View.
    Decision12.png
  3. Select the dependent Action.
    Decision13.png
  4. Insert an Action before the dependent Action. Select Verify.
    Decision14.png
  5. Select the element to be verified in the screenshot.
    Decision15.png
  6. Confirm the verification. Click Insert.
    Decision16.png
  7. Close Slider View and return to the Test Details page.

  8. Expand the Verify Action to view the Action Settings. Check the Optional Action flag and click Save.
    Decision1.png

  9. Open the Action Settings for the dependent Action. Select the Advanced tab.
    Decision6.png
  10. Select the Decision Action step.
    Decision7.png
  11. Select the result to use (read more about this option below). Save the changes.
    Decision8.png
  12. The dependent Action will now display the condition that it executes only if the optional step is successful.
    Decision9.png

Decision Result

Decision Actions can be set to execute if the optional Verify was successful or unsuccessful. By default, they are triggered when the result of the Verify is True, but you can alternately select False. These can be set up in combinations to perform limited conditional workflows.

For example: Your site displays a banner informing the visitor about site cookies upon first visit. Once the "Accept" button is clicked, the banner clears. One way to confirm this is working properly would be to set an optional Verify to successfully confirm the banner is visible followed by a dependent action to click Accept. You could then clone the verification, and set the next dependent action to open a menu on the Verify unsuccessfully confirming the banner is visible. 

Note: This type of workflow could be executed more easily with custom JavaScript code or utilizing Not on page verifications.
ConditionalUsage.png

Create a Decision Action - Alternate Method

  1. Open your Project and select your test to view the Test Details page.

  2. Expand the Verify Action to view the Action Settings.

  3. Check the Optional Action flag. Save the Action change.Decision1.png
  4. Open the Actions Menu. Select Decision Actions.
    Decision2.png
  5. Check the box next to the dependent Action. Click Update.
    Decision4.png
  6. Select your optional Verify Action. Click Submit.
    Decision5.png
  7. The dependent Action will now display the condition that it executes only if the optional step is successful.
    Decision9.png



Related articles