Configuring a run for Rate Schedules or VU Schedules

You can configure Rate Schedules or VU Schedules to be run on HCL OneTest™ Server.

Before you begin

  • You must be a member of the project with the Owner or Tester role to configure and run tests.
  • You must have read Test run considerations for schedules if you are configuring a run for Rate Schedules or VU Schedules that have JMeter tests.

Procedure

  1. Open the project that contains the test assets you have added from the Git repository and click Execution.
  2. Select the branch of the repository that contains the test assets that you want to run.

    All test assets in the selected branch are displayed on the Execution page.

  3. Identify the test asset that you want to run from the test assets listed. You can also identify the test asset by completing any of the following actions:
    • Search for the test asset by entering any text contained in the test asset name in the Search text box.
    • Create a filter query by using the New filter option. Enter the relevant parameters and apply the filter query. You can save the filter query for retrieving it from the list of saved filters.
    • Retrieve a saved filter by using the Open filters icon Image of the icon.. Select and apply the saved filter.
      Note: To open the filter query, you must have created and saved a filter query.
  4. Click the Execute icon Image of the icon. in the row of the identified test asset.

    The Execute test asset dialog box is displayed.

  5. Select the version of the test resources that you want to run by completing any of the following actions:
    Note: The test resources in the version can contain the test assets, datasets, AFT XML files, API environment tags, and other resources specific to projects created from any of the desktop clients.

    • Expand the list in the Version field, find the version of the test resources, and then select the version.

      Use the following details about the version of the test resources that are displayed to identify the version that you want:
      • Commit message.
      • Tags labeled by the user for the version committed.
      • The user who committed the version to the repository.
      • Relative time of the commit. For example, 2 hours ago or 3 days ago.

      The list displays the versions of the test resources committed by all users to the branch in the repository. The versions are arranged with the latest version committed followed by the earlier committed versions.

    • Expand the list in the Version field, and search for the version that you want to select by entering a partial or the complete commit message of that version.

      The version that matches the search criteria is displayed and is selected for the test run.

    The default value for the version selected for the run is the latest version in the selected branch in the repository. If you do not select any version, then the latest version is selected for the test run.

    Notes:
    • If you have selected a version but you do not want to use that version in the test run, you can remove the selected version by clicking the Image of the icon. icon and the default version is selected for the test run.
    • If you are repeating a test or you are rerunning the test from the Results page, then the version of the test resources that you had selected for the earlier run, is shown as selected. You can either retain this version or select any other version from the list. You can also remove the earlier version by clicking the Image of the icon. icon.
  6. Select the time for scheduling the test run from the following options:
    • Select Now, to initiate the test run immediately after you click Execute.
      Important: Click Execute only after you have configured the other settings in this dialog box.
    • Select Later and configure the date and time for scheduling a test to run at the scheduled date and time.

    The default time for scheduling a run is Now.

    Notes:

    • If you have configured some or all of the settings for the current test run, and you do not want to continue with those settings, you can reset the settings by clicking Reset.

    • If you are repeating a test run and do not want to use the saved settings from a previous run, you can reset all the saved settings to their default values by clicking Reset.

  7. Enter a label for the test run that helps you to identify the test on the Results page.

    After the test run completes, the text that you entered is displayed for the test under the Labels column on the Results page. After you have created a label, it can be used by any member of the project.

    The default value for the Label field is null or an empty field.

    Important: The configuration that you set for the test run in the Execute test asset dialog box is preserved when you run the same test again. Those changes are not visible when another user logs in to HCL OneTest™ Server. For example, if you created new variables on the server, those variables are available only for you when the same test is run again.

    If you want to run the test immediately or at the scheduled time, click Execute, or continue with the next step.

  8. Click Advanced to make the following advanced configurations:
    1. Enter any Java arguments that must be passed to the test run at runtime in the Java Arguments field, if applicable for the test.

      For example, you can set a maximum Java heap size.

    2. Enter program arguments that must be passed to the test run at run time in the Program Arguments, if applicable for the test
    3. Enter the environment variables that must be passed to the test run at run time in the Environment Variables field, if applicable for the test.

      For example, enter the environment variables when third-party libraries used in the test run refer to the environment variables for configuration.

    Note: You must separate the arguments or variables with a white space when you enter them in the same line or you must start each argument or variable on a new line.

    The default value for each of the fields for the advanced settings is null or an empty field.

    If you want to run the test immediately or at the scheduled time, click Execute, or continue with the next step.

  9. Follow the instructions in this step if you are running a test asset that contains datasets:
    1. Click the DATA SOURCES tab, if it is not already open.
    2. Consider the following information about datasets before you select a dataset:

      The default value for the datasets in the DATA SOURCES tab is null if the test asset did not have an associated dataset. If the asset had an associated dataset, the default value is the associated dataset.

      You can utilize the dataset stored as an Excel or CSV file to override the original dataset associated with the Suite, test or schedule. For example, you have associated a dataset in .xlsx, .xls, or .csv format with the test or schedule in desktop clients. If you have another set of data stored in an Excel or CSV file, you can select that dataset from the Override list. If you want to run a test or schedule by using the schema created from the Data Fabrication page, see related links.
      Remember: You must have uploaded the dataset as an Excel or CSV file into the Git repository, and ensured that both the original dataset (from the test asset) and new datasets (added to the project) have the same column names.
    3. Select the dataset that you want to use in the test run from any of the following options:
      • Select the dataset that is displayed as the default dataset when the test asset contains a single dataset.
        Note: If there is only one dataset in the test asset, then that dataset is displayed as the default dataset.
      • Select the dataset from the list.
        Note: If there are multiple datasets in the test asset, the datasets are listed in their increasing alphabetical order.
      • Select the dataset from the Override list to override the dataset that was associated with the test in the desktop client.
        Important: If the test contains an encrypted dataset, the Project Owner must classify it in the DATA SECURITY tab on the Project page before you can select it. You must have added datasets to your project from the Dataset page for the datasets to be displayed in the Override list.

    If you want to run the test immediately or at the scheduled time, click Execute, or continue with the next step.

  10. Follow the instructions in this step if the test requires a variable that must be passed to the test at the test run time.
    1. Click the VARIABLES tab, if it is not already open.
    2. Choose one of the following methods to add the variables:
      • To add new variables manually, click the Add Variable icon Image of the Add icon, enter the name, and value of the variable.
      • To add new variables from your local computer or from the Git repository that is associated with your server project, click the Upload icon Image of the icon and select the Upload from local system or Browse from server to select the variable file.
        Note: You must have created a file with the variables before you can select the file.

    The default value for the variables is null or an empty field.

    If you want to run the test immediately or at the scheduled time, click Execute, or continue with the next step.

  11. Follow the instructions in this step if you are running a test that has static agents configured:
    1. Click the LOCATION tab, if it is not already open.
      The static agents configured in the test asset are listed under the Host column. The information about the availability of the agent is displayed.
      Note: You must have added agents to your project from the Infrastructure page for the agents to be displayed under the Override column.
    2. Select the agent where you want to run the test asset.

      You can select the same agent configured in the test asset. Alternatively, you can override the agent with any other agent added to the project by selecting it from the list in the Override column.

    The default value for the agents is null or an empty field if there were no agents configured in the test asset. If the test asset had agents configured, the default agent is the first one on the list of agents listed in the increasing alphabetical order.

    If you want to run the test immediately or at the scheduled time, click Execute, or continue with the next step.

  12. Follow the instructions in this step if you want to change the location for running the test:
    1. Click the LOCATION tab, if it is not already open.
      The Default Cluster is the default location where the test runs, and is listed under the Host column. The information about the availability of the default location is displayed.
      Important: You must have added remote Docker hosts that are registered with HCL OneTest™ Server to your project from the Infrastructure page. The remote Docker hosts are then displayed under the Override column.
      Notes:
      • If remote Docker hosts are not added to your project, the option No override options is displayed as the default value and the test runs in the Kubernetes cluster of HCL OneTest™ Server.
      • If remote Docker hosts are added to your project, the added Docker hosts are displayed along with their availability status and ownership information.
    2. Select the location where you want to run the test asset from the following options:
      • Select the Default Cluster when no remote Docker hosts are available in your project.
      • Select the remote Docker host from the list when a remote Docker host is available in your project.
      • Select No override options, if you have selected any remote Docker host and want to revert to the Default Cluster to run the test asset.

    If you want to run the test immediately or at the scheduled time, click Execute.

  13. Click Execute.
    The test run is started.

Results

You have either started or scheduled a test run for a Rate Schedule or VU Schedule.

What to do next

You can choose to perform any of the following tasks after you have initiated or scheduled a run: