Create an Orchestration

Functionize offers the ability to execute multiple test cases from multiple projects, allowing the ability to set test execution run order and creating a better organization of test groups and types. These orchestrations can be executed on 10's, 100's, and 1000's of test cases, from anywhere in the world, across any type of browser or emulated mobile device. With Functionize, a user can create single or group orchestrations.

With a Single Orchestration, there can be one "bucket" of a group of tests to be executed in parallel or sequentially of any test cases using filters such as projects, tags, and modules.

With a Group Orchestration, there can be multiple buckets of the above single orchestration scenario.  However, with group orchestrations there is more granularity capability in organizing the orchestration further.

NOTE: Use the Bulk Action >> Run Tests action to execute multiple test cases within the same project if that is preferable. See Execute a Test Case.

 

To Create a Single Orchestration:

  1. Open the Orchestration tab at the top of the page and click on Create New Orchestration.
  2. In the Create New Orchestration window, begin with the Details tab.
    mceclip1.png
    Title: Give this orchestration a name/title.

    Projects: Select any number of projects in the account to run this orchestration on.

    Environment: Select the environment to run the orchestration in.

    Folders: Select a folder to filter test cases. See How to Create a Folder for further information.

    Tags: Select a Tag to further filter test cases. This is optional; available tags must first be created to use as a categorization

    Test Cases: Select any number of test cases that are available based on the project(s) and tag(s) selected above.

    Schedules: Select the schedule that this orchestration will be run on.  On-Demand | Hourly | Daily

    Select Browser: Select all browsers to run the orchestration in.

    Orchestration Type: Foreground | Background | TDM Run for the purpose of moving visibility where:

     -If Foreground is selected, the test cases within the projects selected will be executed. View the results of the orchestration on the orchestration page or within the actual project(s) that contain those test cases. The user will be alerted if any of the test cases fail.

     -If Background is selected, the tests will NOT execute or update in the project(s). Instead, view the test results from the Orchestrations page. All test cases will have a virtual copy made that runs outside of the project(s). This can be useful when wanting to access test cases within the projects while the orchestration runs. We recommend using this option when selecting an Orchestration Run Type.

     -If TDM Run is selected, the orchestration will execute the selected Test Data along with the test case. See To Create an Orchestration with TDM.

  3. Move to the Integrations tab to add integrations. Select the integrations relevant to your orchestration.
  4. Move to the Advanced tab, to add advanced features on this orchestration.
    NOTE: This tab is optional. By default, the orchestration will run as a Single Orchestration Type, unless Group radio button is chosen here. For Group Orchestration Type instructions, please see To Create a Group Type Orchestration further in this tutorial.mceclip0.png

    ADVANCED TAB (Single Orchestration)

    Run Order
     -Parallel (Default): Select this if to run the tests simultaneously.
     -Sequential:  Select this to run the test sequentially.

    Orchestration Type
     -Select Single radio button.

    Re-Run
     -Select as appropriate.

    Email Alerts
     -Enter email addresses for where the alerts should be sent, separated by a comma.   

    URL Override
     -Add string::replacement, if applicable

    Alerts Delivery
     -Select from the dropdown based on how/when the alerts should be delivered.

    Webhook URL
     -Input the webhook url, if applicable.

    Allowed Test Run Overtime (Max)
     -Input (in minutes) a time limit to change the status of the test case from provisioning to processing.

  5. Click Add New.
  6. The Orchestration Test Cases window will open for you to confirm which test cases to include. Click Submit.
  7. Locate the orchestration to run in the list and click the Execute icon.
  8. In the Execute Orchestration confirmation window, click Run Orchestration. 

 

To Create a Group Type Orchestration:

  1. Open the Orchestration tab at the top of the page and click on Create New Orchestration.
  2. In the Create New Orchestration window, begin with the Details tab.
  3. Move to the Integrations tab to add integrations. Select the integrations relevant to your orchestration.
  4. In the Advanced tab, select the Group Orchestration Type.
    mceclip1.png

    ADVANCED TAB (Group Orchestration)

    Run Order
     -Parallel (Default): Select this to run the tests simultaneously.
     -Sequential:  Select this to run the test sequentially.

    Orchestration Type
     -Select GROUP radio button

    Re-Run
     -Select as appropriate.

    Email Alerts
     -Enter email addresses for where the alerts should be sent, separated by a comma.

    URL Override
     -Add string::replacement, if applicable

    Alerts Delivery
     -Select from the drop-down based on how/when the alerts should be delivered.

    Webhook URL
     -Input the Webhook URL, if applicable.

    Allowed Test Run Overtime (Max)
     -Input (in minutes) a time limit to change the status of the test case from provisioning to processing.
  5. Click Add New.
  6. The Orchestration Test Cases window will open for you to confirm which test cases to include. Click Submit.
  7. In the Orchestration Grouping window, you can make granular changes to your orchestration by segmenting into multiple buckets as well as organizing each group with an overall serial order and specific test run orders. Click Submit.
  8. Locate the orchestration to run in the list and click the Execute icon.
  9. In the Execute Orchestration confirmation window, click Run Orchestration.

 

To Create an Orchestration using Test Data Management:

Please see User Guide: Test Data Management (TDM) - Orchestrations