Perform a Load Test

In this tutorial, learn how to perform a Load Test using real user flow examples, along with the Performance Metrics set of results.

To Create a Single Load Test 

Select a project to perform the load test on.

    1. Go to the Load Tests tab.

    2. Click on Create New green button on the far right on the screen.

    3. Click on the radio button for Single Load Test, then click Submit.

          The following window will display:

         

 

    4. Complete the fields as follows:

Load Test Title = Enter the name of the load test.  In this example, we have named this test "Sample Single Load Test"

Target = What category to target for this Single Load Test?

• Select Project radio button to target an actual project.  In this example, we have selected the "1- Cloud scale execution" project
• Select Module radio button if target a module within this project *NOTE: a Module is a categorization system in the Functionize platform.
• Select Test Case radio button to target a specific test case.
• Select Tags radio button to target an existing tag in this project.  *NOTE: a Tag is a categorization system in the Functionize platform.

*Project = Select from the dropdown menu.  *Depending on what Target has been chosen previously will depend on what dropdown menu displays to select from.

Project Environment = Select the environment to test in.   

Region = Select the region/location from the dropdown menu to run the Load Test from.

Virtual User Count = Enter the numerical value for the desired virtual user count.

Duration = Enter how long the Load Test should run.

Schedule = Select Yes to run the test at a scheduled date (a date dropdown will appear).  Select No to run the test manually.

 

    6.  Click Add New.

    7.  A Single Load Test has now been created in less than a minute!

 

To Execute the Single Load Test

1. Click the  button, under Status.

                

*A warning will pop-up asking to confirm.  If yes, click on Execute Load Test.

     2. The Single Load Test will execute and the status icon will change to a spinning icon, indicating the execution of the load test is running.

     3. Once the load test is complete, go to the Action column and select the report icon to go to the Performance Metrics Reports for results.

                       

To Create a Group Load Test

Select the project to perform the load test on.

    1. Go to the Load Tests tab.

    2. Click on Create New green button on the far right on the screen.

    3. Click on the radio button for Group Load Test, then click Submit.

        The following window will display, offering additional configuration options:

              

      5. Complete the fields as follows:

Load Test Title = Enter the name of the load test.  In this example, we have named this test "Sample Group Load Test".

Region= Select the region/location from the dropdown menu to run the Load Test.

Schedule = Select Yes to run the test at a scheduled date (a date dropdown will appear).  Select No to run the test manually.

Group Data

Duration = Enter how long the Load Test should run.

State = Select STEADY* or RAMP   Reference example: Let's say we have 1000 users for this load test. . Functionize will spin up 1000 virtual machines where each one essentially represents a user.

• If Steady is selected, then there will be a consistent "steady" state of load of all 1000 users for the duration selected.
• If Ramp state is selected, then (in this example) the test will begin with 100 users and every minute we will incrementally increase the load by 100 until we reach 1000.  

Project Environment = Select the environment to test in.  

Add as many Test Cases to specifically target test cases using the Add New Test button.

               

Select the test cases from the drop-down menu. Then indicate the number of Users (Required) and number of Transactions (optional) as detailed below:

    Users = A required field that indicates the number of dedicated users that will execute each test case until the end of the test. Example: there may need to be 500 users running through a particular flow for one hour, with no upper limit on how many times they can run through that particular scenario.

    Transactions = An optional field that indicates the number of transactions/executions that each test can handle, per user.  Example: To ensure that 5,000 customers can move through a checkout process within one hour.  To facilitate this, set X number of users and then limit the total executions possible by setting the transaction field = 5,000.

         

Add Groups for further configuration, granularity, and control, by clicking on the Add New Group button. From here, setting different durations, states and project environments for groups of test cases within the project.

To Execute the Group Load Test

     1. Click the  button, under Status from the Load Tests tab.

*A warning will pop-up asking to confirm. If yes, click on Execute Load Test.

     2. The Group Load Test will execute and the status icon will change to a spinning, indicating the execution of the load test is running.

     3. Once the Load test is complete, go to the Action column and select the report icon to go to the Performance Metrics Reports for results.

Performance Metrics & Results

Functionize provides a robust set of Performance Metrics Results in the graphic display as follows:

Summary of the Load Test

Where:

CLIENTS = # of users used in the Load Test

TOTAL RUNS = total # of execution runs

FAILED = total # of tests that failed

WARNINGS = total # of test with warnings

PASSED = total # of tests that passed

PAGE LOADS = total # of page loads

REQUESTS = the total # of instances where APIs or other data were called upon.

 

List of Performance Metrics provided for each URL, along with a link to each Page Resource:

Performance Trend Line

The dynamic report showing all pages by default, or use the drop-down menu to hone into a specific page. Hover over any metric to display the performance data captured.

Comparative Page Performance

Shows a comparison between the fastest and slowest page load.

Average Page Performance

Average Page performance is broken down for every page within the load test, in milliseconds (ms).

Performance Details

Each bar represents a URL. URLs can be filtered by performance events.

Action Duration

Shows action duration, in seconds, for each step. Can filter by all test cases within the load test to see what the action duration is for each.

Geographical Overview

Black terminal icons show the servers where the test(s) are being run from.

Red target icons show where the simulated user is kicking off the test(s) or indicates a jump point.

Hovering over the Green connection lines will offer a more granular set of detail, as shown in the example below: