Following are the fields for test case configuration:

- Project: The Project is the parent directory of the Sub Project.
- Sub-Project- Sub-Project is the directory where all test assets (Script, Scenario, TestSuite, Services etc.) are stored.
- Test Case Name- Enter the test case name in the required format.
- Description- Describe the test case in this field.
- Scenario- This option is used to Edit the scenario which is used in the script. Also can edit the scenario.conf file in the UI mode by clicking on the advance option. Users can edit the selected Scenario. An edit can be done via Text mode i.e. scenario configuration file will open in Text mode. Users can edit the configuration value in the scenario and save it. They can also edit the scenario configuration through scenario UI by clicking on the “Edit Scenario in GUI” button. It will redirect the user to scenario GUI where they can make the changes and save it. Users can also edit the script which is associated with the selected scenario by clicking on the “Edit Script” button. It will redirect the user to the script manager where they can make the changes and save it.

## Check profile

Select the profile from the drop-down and click the add-in table option. Also, the user can switch to Add New Checkprofile screen. They can add multiple check profile by adding them to the table.

## Check Script

In the Check Script section, the user can compare multiple TRs and define the pass/fail criteria. They can compare the current test run by selecting the previous testrun as a baseline.

- Compare test Run- Select the baseline and scenario for comparison.
- Select the Override Checkprofile SLA with the option and specify the baseline test. It is optional to select this option.
- Pass/Fail Criteria- In the Pass/Fail Criteria section, the user can specify any % value to the Critical threshold (default 50%) Warning threshold (default 20%), and Overall Fail Criteria (default 10%) which works on rules defined in Check Profile.

According to the Pass/Fail Criteria configuration, the colour code will be shown in the Test Status report. The Default value for the SLA variation is upto 20% shows green, 50% shows Yellow otherwise Red.
Let's see with an example: If SLA is given for a Metric value=10 then the metric value between 8 to 12 is shown as Green, and between 5 to 8 and 12 to 15 will be shown as Yellow otherwise it will be shown as Red.
If SLA >10 then the metric value between 8 to 10 is shown as Green, between 5 to 8 will be shown as Yellow, and less than 5 will be shown as Red.
Similarly, if SLA < 10 then the metric value between 10 to 12 is shown as Green, between 12 to 15 will be shown as Yellow, and greater than will be shown as Red.
If 10% or more of the metrics are red, the overall test status will be failed. You can configure the percentage value as per the requirement.

Note:

1. Variation is checked based on the operator used in the rule. For less than on the higher side, for greater than it is the lower side, and for equal to the operator it’s on both sides.
2. The Critical Threshold cannot be zero as the Critical threshold should be greater than Overall Fail Criteria and if the user specifies the Critical Threshold as 0 then the Overall fail criteria will have to be less than 0 which is not possible.

## Advanced Settings:

1. Select the check box if you want to Run Post Check Script on failure.
2. Select the check box if you want to include transaction Count in Report.
3. Select the check box if you want to include unexpected transaction in Reports (Apply rule on current).
4. Select the check box if you want to Report Generation of Duration Phase.

## Iteration

Users can add a Parameter Name by clicking on “Add Parameter”. These added Parameter names should already exist in Scenario OR Script otherwise they will not get impacted. Once the user clicks on “Add Parameter” then one POP UP will get displayed where they need to enter the Parameter Name. Also, select that defined Parameter name used in Scenario OR used in Script by clicking on the Radio button. Once the user adds the Parameter name then they can add value to the Parameter Name respectively.

Once the user is done with the Parameter Name and value of the Parameter name, then they need to click on ‘Save”. If the user clicks on the “Close” button, then no update will get impacted. The total Number of Rows in the Iteration Name will be the count of execution of the Test Case.

User can also view these parameters in text mode.

## Pre Test Script

The Pre-Test Script tab enables user to perform some actions like copy, delete, upload, download, etc before executing the script. They can add different actions on selected servers. Specify the required actions in this tab that needs to perform before executing the test cases. The Pre-Test Script tab enables users to add different actions on selected servers. They can specify the required configuration in this tab before executing the test cases. Based on the selected action, input fields are displayed. For example, selecting the action "Copy_File" displays the Source and Destination fields. Select Action from the drop-down and add the server name for the action.

The following actions can be defined in the Pre-Test Script tab:

- Copy_File: COPY_FILE is a utility to copy a file from the source path to the destination path on the selected server. The command is executed via the Cavisson agent if available on the server otherwise it is executed using ssh. Authentication information is taken from the LoadTest server database.
- Start_Command: To start a service on the server machine. It is also done with and without the CavMon agent.
- Stop_Command: Enables the user to stop service on the server machine. It is also done with and without the CavMon agent.
- Remove file: Enables the user to remove a file on the server machine.
- Start_service_sudo: To start a service on the server machine. When running the privileged command with the pseudo prefix, users will be prompted for their regular password before it is executed.
- Stop_service_sudo: Enables the user to stop service on the server machine.
- Upload: To upload a file on the server. It can also be done in two ways - With and without a CavMon agent.
- Download: This enables the user to download a file from the server. It is done using nsu_import_file.
- Sleep: To provide sleep between any two actions. This function suspends the execution of the calling thread for the specified time.

User can configure the required action in the following ways:

- Using the GUI mode
- Using the Text mode

Note: To specify the Pre-Test Script in Text Area, click View in Text mode and write the required script in the given text box.

## Post Test Script

Using the Post Test Script tab, the user can specify the required actions that can be performed after the execution of the test case. Select the action name from the drop-down and the server name to add action.

Note: The functionality of the Post-Test Script is similar to the Pre-Test Script tab. The only difference between them is that the Pre Test Script is executed before running the test cases, while the Post Test Script is executed after running the test case.

## Mail Configuration

User can send TestCase reports from Load Test to the selected users. Using the Mail Configuration tab, user can configure the email settings in Load Test and send reports as an attachment. Add the To, Cc, and Bcc to whom the test report is to be shared.

Before using the mail feature, user need to ensure that the global Email/SMS settings are specified for the host, port, and sender.

Specify the required email IDs in the To, Cc, and Bcc fields. On report generation, an email is sent to the mentioned users in the To, Cc, and Bcc fields.

Note: Multiple email addresses can be entered. Press ENTER key after each email address. Without pressing ENTER key email will not be saved.