Once the Cavisson machine is installed, user can login to the system and access various features of LoadTest.
Login to Cavisson
User needs to follow the below-mentioned steps to login to Cavisson UI:
- Open a web browser and specify the URL of the server where Product is installed.
- The Cavisson login window is displayed as illustrated in the image.
Figure: Cavisson Login Window
- Enter the Username and Password and click Login. The user logged in to the Cavisson and the Unified Dashboard is displayed.
Figure: Unified Dashboard
Load test: The home page consists of a left panel and a right panel. The left panel contains menu to view details on all test runs, scenarios, data files, and automation. Using these menus, the user can access further sections and can perform various operations, such as compare test runs, generate reports, access various features of the web dashboard and executive dashboard, and so on. On the right panel, a summary of the important aspects is displayed, be it a release version, CPU usage, memory utilization, or alerts generated in the system.
It contains the following menus/sub-menus, and menu items:
- All Test Run
- Data Files
Click for all test runs details page. We get the following figure:
Figure: All Test Run Page
Let us discuss the sub-headings in detail:
- Test Run: It shows the test run having unique numbers and in sequence.
- Test Name: It is given before starting any test. The name doesn’t need to be the same.
- Scenario Name: Specifies the name of the scenario from which the test runs.
- Start Time: Specifies the date and time when the test started.
- Run Time: Determines the duration of the test run.
- User: Shows the number of Virtual users used in a test run.
- Started By: It shows the user who started the test run.
- Notes: A user can specify any note related to that test run.
- Action: It shows various action user can take like deletion, archive, and unlocking.
Click on for scenarios detail. You have the following details as displayed below
Figure: Scenarios Page
Let us discuss in detail:
- Project: Project is the directory.
- Sub-Project: Sub-Project is the directory.
- Scenario: Specifies the scenario on which the test runs.
- Modification Time: This shows the time and date when the scenario is when modified.
Actions on Scenario
– This icon is used for the test to be run.
– This icon is to edit the scenario.
– This icon is to copy the scenario.
– Delete a Scenario
User can view the script used is the scenario creation. To do this, select he scenario and click the View Script button. The script gets displayed on the Script Manager window.
Save Scenario as Profile
User can also save a scenario as a profile. To do this, select a scenario, and click the Save Scenario As Profile button. A dialog box is displayed to provide project, sub-project, and profile name. After specifying the details, click the Save button.
Figure: Save Scenario as Profile
The scenario gets saved as a profile.
This is used to commit the changes to a local repository. Select a record and click the GIT Commit button. A dialog box is displayed where the user needs to provide the comments and click the Commit button.
Figure: GIT Commit
It is used to pull the latest commits from the remote server to the local repository. By refreshing scenarios/scripts, all the recently committed files on master repository are fetched to the scenarios/scripts directory of local repository Select a record and click the GIT Pull button. On successful processing, a message is displayed – Refresh successfully.
Figure: GIT Pull Message
This dialog box –Create Task tab.
Create Task: In this section, user can create a task and schedule it for its execution. To perform this activity, click the Create Task tab. The Scenario Schedule window is displayed with first section as Task Description.
Figure: Create Task Window
Specify the task description, such as task name, project, sub-project, scenario name, and scenario description.
Here, the user can view the version logs of a record. If there is a change in scenario, such as increasing/decreasing Vusers, increasing/decreasing the stabilization or duration time, then these changes are reflecting in UI in the form of a modified file. To use version control feature, select a record and click the Version Control button.
This displays the Version Control window:
Figure: Version Log
Specify the comments and click the Commit button.
- Update: This button is used to update the current version of the scenario.
- Diff: This button is used to get the difference between two scenario versions.
- Delete: This button is used to delete a scenario version.
- Close: This button is used to close the window.
The tasks are executed automatically based on the preconditions, inputs, and the scheduled time. In Scheduler Management, the user is asked to provide some pre-conditions for starting a test. Once conditions are provided, the user is required to specify the email id to make aware that the test has been started (in case the user is not available at a time when test has been started).
Once all the details regarding the test are provided, a time to schedule that task is provided to the user. Once the time matches with server time, the task is executed or in simple words, the test gets started.
To perform this activity, select a scenario and click the Scenario Schedule button. A dialog box is displayed.
Figure: Schedule Scenario
Create Task: In this section, the user can create a task and schedule it for its execution. To perform this activity, click the Create Task tab. The Scenario Schedule window is displayed with the first section as Task Description.
Figure: Create Task Window
Specify the task description, such as task name, project, sub-project, scenario name, and scenario description. Then, click the Next button, the Scenario Parameter section is displayed.
Specify the following details:
- Timeout: Denotes the timeout in seconds.
- Retry Count: Denotes the number of retries.
- Retry Interval: Denotes the interval between each retry.
Post- check Parameters
- Wait Time: This is the waiting time.
- Forcefully: There are following options under this – don’t start a new test, stop previous test and start new test after wait time, start a new test in offline mode.
Once the pre-check and post-check parameters details are specified, click the Next button. The section to add user’s mailing details is displayed. This is used to make the user aware about the schedule details on email.
Specify the user email ID, subject, and body of the email. In the body section, use the predefined parameters, such as test number, start time, and end time. This step is optional and can be skipped by clicking the Skip button. User gets navigated to the next step of the scenario schedule management.
This section displays the summary of the task scheduler. It is divided into two sub-sections – task description, and scenario parameters. Expand the sub-sections to see the details. Next, click the Finish button. A message is displayed that task is added successfully.
In this user can add comments to the committed scenario. To perform this activity, select a scenario and click the Version Commit button. A dialog box is displayed.
Figure: Version Commit Dialog Box
This section describes how to create a scenario profile and configure it for use in other scenarios. If the user selects that particular scenario profile while creating a scenario, the settings are reflected in the created scenario. There is no need to perform the settings repeatedly, the user just needs to select the scenario profile in which the required settings have already been done.
The user needs to follow the below-mentioned steps for creating a scenario profile:
- Login to LOAD TEST. On the left panel, click Scenarios icon, and then click Scenarios Profiles.
Figure: Scenario Profile Selection
- The Scenario Profile window is displayed.
Figure: Scenario Profile Window
- In the Scenario Profile window, click the Add The Create Scenario Profile dialog box is displayed.
Figure: Create Scenario Profile Window
- Specify the Project Name, and SubProject Name, enter the Profile Name and click Next. The Scenario Profile is created and added in the Scenario Profile Schedule Settings window is displayed.
Figure: Scenario Profile Page
- The sections for setting different options (in Global settings, Group-based settings etc.) are displayed. Here, the user can set up a scenario profile and save the settings for later use in scenarios.
Internet Protocol (IP) Address Management
It is a method of tracking and modifying the information associated with a network’s Internet Protocol address (IP address) space. It is an integrated suite of tools to enable end-to-end planning, deploying, managing, and monitoring of your IP address infrastructure, with a rich user experience. It automatically discovers IP address infrastructure servers and Domain Name System (DNS) servers on your network and enables you to manage them from a central interface.
Why IP Management is required?
There is a need for LOAD TEST to support multiple sources of IP addresses for the following reasons.
- Real users use different source IP addresses and hence to emulate the real-world scenarios LOAD TEST should be able to generate virtual users with different source IP addresses.
- When LOAD TEST generates a very high connection rate, the system can run short of IP addresses/ports combinations for creating new connections. Ports are limited to 64K and hence having several sources IPs may be required.
There is a need for LOAD TEST to support multiple servers IP addresses for the following reasons.
- Real servers use different IP addresses and hence to emulate the real-world scenarios LOAD TEST should be able to connect to different servers with IP addresses.
- When LOAD TEST generates a very high connection rate, the system can run short of IP addresses/ports combinations for creating new connections on the server side. Ports are limited to 64K and hence having several destinations IPs may be required.
This is achieved by IP management module of LOAD TEST product.
IP Management in LOAD TEST
Go to Load Test > Scenarios > IP Management.
Figure: IP Management Icon
This displays the IP Management window. Here, the user can assign IP address for client and server.
Figure: IP Management Window
To assign an IP address for the client or server, the user is required to click the Client or Server button respectively.
Assigning IP Address
On the IP Management window, click the Add button. This displays the Add IP window (for either client or server based on the option selected).
Figure: Add IP for Client
The user needs to provide the following inputs:
- IP Version: Select either IPv4 or IPv6.
- Vlan ID: An ID associated with each VLan.
- Network ID: Network ID for client/server.
- Netbits: Bits of IP address, which are used to represent the network.
- Start IP: Start IP of the particular range (netid).
- End IP: Last IP of the given range.
- Number of IPs: Number of PIs in the provided range.
- Gateway: Allows data to flow from one discrete network to another. IP properties Tab of the IP Management affects this field.
- Interface: It is condition-dependent. If we are using more than one Load interface, then only these column becomes visible.
By clicking the Auto Fill button, the details are filled out automatically. To use this option, the user must provide Start IP and End IP or Number of IP.
The user can delete one or more IPs by selecting the record(s) and clicking the Delete button.
Show Required Gateway Configuration
This button is only displayed if there is any gateway entry in the IP entries file. On clicking this button, it displays the gateway IPs of client and server.
Figure: IP Management List
On clicking this button, it fetches those clients’ IPs and server IPs, which are not connected.
Figure: IP Connectivity
The user can set the Gateway configuration for the IPs. Based on the Gateway configuration, the Gateway columns vary in the IP tab. The user can reserve the net ids so that they cannot be added to the IP tab.
Figure: IP Properties
Only Layer 2 device is between client and server (No Gateway configuration required)
If the user wants to set the gateway configuration in such a way that there is no gateway required between client and server then the user needs to use this option.
Only Layer 3 device(s) is between client and server (Gateway configuration always required)
If user always wants to use the Gateway between client and server, then the user needs to use this option.
If the user wants to use first IP as gateway, the user needs to use the following option:
Use first IP address of the IP range as Gateway address if Gateway not specified
User-defined (No enforcement of Gateway configuration)
It means there may or may not be a gateway between the client and server. Therefore, the user can use this option.
The user can reserve net ids that cannot be added to IP tab. This net id is reserved for internal use. We use 192.168.255.0 as the reserved net id for IPV4.
You can use the Data Directory section for data file management. If you override the data directory, the data files of all file parameters are taken from the specified directory. If no file is found, it will be taken from the data directory specified in the file parameter and then from the script directory.
Click on for data files. Once you click this icon the data files page opens as in below figure:
Figure: Data Files
Let us discuss the fields in detail:
- Name: It is the name of the data directory.
- Last Modified: It shows the last date and time when the directory was last modified.
- Action: In action, we have the following option:
- View in file explorer
- Download in zip
- Delete the data directory file
- Upload ZIP: Upload zip of file containing dat, csv, txt, xml, json, cfg, pdf, docx, xls, zip extension, java, jar and js.
Click on for Automation details. You get the following page once you click on the icon.
Figure: Automation Page
In Automation, in the left panel we have the following headings:
- Test Suite
- Test Case
- Test Report
- Check Profile
Let us discuss them in detail:
In Automation, once you click the Summary Icon, you get the following fields:
Figure: Summary- Automation
Recently Executed Test Suites
- Test cycle Number: This is a unique number which generates on every test suite execution.
- Test Suite Number: Specifies the name of the suit.
- Start Time: Date/Time when Gtest Suite start executing.
- End Time: Date/Time when Gtest Suite stops executing.
- Total Cases: It shows the total number of test cases associated.
- Executed: It shows cases that are successfully executed.
- Failed to execute: It shows case which fails to execute.
- Passed: Specifies the cases passed.
- Failed: Shows the cases which are failed.
- Action: Determine the action to be executed.
Total Test Cases
- Test Case ID: This is the unique number which generates for every test case.
- Test Description: It shows the description of the test.
- Test Number: Unique number for the test executed for a particular test case.
- Status Report: Status of test case in Progress/Pass/Fail.
- Pre-Log: It determines whether the logs of prescript are available or not.
- Post Log: It shows whether the logs of postscript are available.
- Test Log: It shows whether test logs are available or not.
In Automation, once you click the Test Suite Icon, you get the following fields:
Figure: Test Suite- Automation
- Project- Project is the directory.
- Sub-Project- Sub Project is the directory.
- Test Suite- Specifies the name of the suit.
- Modification Date-It shows the time and date when test suite is modified.
- TestCase Count- Shows the number of testcase count.
- Action: It shows the action taken for a test suite.
Add Test Suite
To Add a Test Suite, click the button. The following window will open.
Figure: Add Test Suite
Following are the fields to be filled to add the test suite:
- Project: Select the project from the drop-down.
- Subproject: Select the sub-project from the drop-down.
- Test Suite Name: Specifies the name of the suit.
- Test Case: Select the test case from the drop-down.
- Action on Failure: Decide whether to continue or abort the test in case of failure.
- Parameterization Mode: Select the mode based on which parameterization is done
- Execution Count: Enter the number of counts to be executed.
Once all of the above fields are filled, click on the icon on the top right corner to save the test suite.
In Automation, once you click the Test Case Icon, you will get the following figure.
Figure: Test Case
You have the following fields in the test case:
- Project: It is the directory.
- Subproject: It is also a directory.
- Test Case: Here the test name added is mentioned.
- Scenario: Specifies the name of the scenario.
- Description: Describe the test running.
- Action: This shows the number of actions that can be taken against the test.
Add Test Case
To Add a Test Case, click the button. The following window will open.
Figure: Test Case Configuration
Following are the fields for test case configuration:
- Project: Enter the project name from the drop-down.
- Sub-Project- Enter the subproject name from the drop-down.
- Test Case Name- Enter the test case name in the required format.
- Description- Describe the test case in this field.
- Scenario- Select the scenario name. You can also edit, copy, delete or save the scenario selected.
- Check profile: Select the profile from the drop-down and click the add check profile option.
Figure: Check Profile Page
- Check Script
Figure: Check Script
- Compare test Run- Select the baseline and scenario for comparison.
- Pass/Fail Criteria-
- The Metric is green if the variation is up to 20%.
- The Metric is red if the variation is more than 50%.
- The Metric is yellow if the variation is up to 50%.
- The overall test fails if 10% or more metrics are red
Note: 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.
- Advanced Settings:
- Select the check box if you want to Run Post Check Script on failure.
- Select the check box if you want to include the transaction Count in Report.
- Select the check box if you want to include the unexpected transaction in Reports (Apply rule on current).
- Select the check box if you want to Report the Generation of the Duration Phase.
- Iteration- Add a parameter and then save the parameter for iteration.
- Pre-Test Script- Select an action from the drop-down and add the server name for the action.
Figure: Pre-Test Script
- Post Test Script- Select the action name from the drop-down and the server name to add action.
- Mail Configuration- Add the name, cc, and bcc to whom the test report is to be shared.
Figure: Mail Configuration
Note: Multiple email addresses can be entered. Press ENTER key after each email address. Without pressing ENTER key email will not be saved.
In Automation, once you click the Test Report Icon, you will get the following figure.
Figure: Test Reports Page
Following are the fields available on Test Report Page:
- Test Cycle Number: This is the unique number that generates on every suite execution.
- Test Suite Name: Specifies the test suite name.
- Start Time: It shows the start time of the test run.
- End Time: It shows the end time of test execution.
- Total Cases: Total number of test cases associated.
- Executed: Shows the cases which are successfully executed.
- Failed to execute: Cases that are failed to execute.
- Action: Shows various actions like showing logs, locking test cycle number, and deleting test cycle number.
In Automation, once you click the Check Profile Icon , you will get the following figure.
Figure: Check Profile Window
Following are the fields in check profile:
- Project: It is the name of the directory.
- Subproject: It is also the name of the directory but in the sub-category.
- Profile Name: Shows the profile name.
- Profile Description: Shows the profile description.
- Check Rules: Check the rule for the profile.
- Last Updated: It shows the time and date when the document was last updated.
- Updated by: The user who updated the profile.
- Action: Select the action as per the requirement.
Adding Check Profile
Figure: Add Check Profile
You have the following fields in Add check profile:
- Profile name: Enter the profile name in this field in the required format.
- Profile Description: Enter the description of the profile.
- Scenario: Select the required scenario from the drop-down.
- Metric: There are the following options in metric;
- Date Field: Select any one of avg, max, min, Percentile, or count from the dropdown.
- Metric Group: Select the metric group from the drop-down.
- Metric Name: Enter the metric name.
- Indices: Select the required indices from the dropdown like all, specified or
- Operation: Select less than, greater than, or equal to value enter the rule name, and write the name to be displayed.
This section provides a summary of details of the following sections:
- Recent Test Runs
- Transaction Details
Figure: Right Pane
Let us discuss in detail about them.
It provides information about the test run numbers, scenario names, start date and time, test status (Passed, Failed, or running), and enables you to view the reports such as Performance and Summary.
Figure: Recent Test Runs
- Test Run: Specifies the test number that is being executed.
- Scenario Name: Specifies the scenario that is running.
- Start Date and Time: Specifies the start date and time of test execution.
- Started By: Species of the user who started the test.
- Status: Displays the status (Passed, Failed, or Running) of the test being executed.
- Action: Enables you to open the dashboard and generate reports.
A scenario specifies the mix of different users accessing a Web application and hence executing different test scripts. It consists of groups of Virtual users or VUsers, which emulate human users interacting with an application for executing a test script. The users can be grouped into different groups and have different user characteristics.
- Last Modified
LoadTest is further categorized into the following sub-components.
The description of each and every sub-components is provided in subsequent sections: