Starting an HTTP/2 CPS test
This test establishes a TCP connection (three-way handshake), optional SSL connection (handshake), completes an HTTP/2 transaction (HTTP/2 request and response), and closes the TCP connection (Reset). It creates one HTTP/2 GET per TCP connection.
To start an HTTP/2 CPS test:
- Go to Cases > Performance Testing > HTTP/2 > CPS to display the test case summary page.
- Click + Create New to display the Select case options dialog box.
- In the popup dialog, for the Network Config option, select the network template you have created in Cases > Security Testing > Objects > Networks. Then the network related options will automatically be filled. See Using network configuration templates for how to create a network template.
- Select a Certificate Group if applicable.
- Click OK to continue.
- Configure the test case options as described below.
- Click Start to run the test case.
FortiTester saves the configuration automatically so you can run the test again later. You can also click Save to save the test case without running it.
Tip 1: You can also copy an existing case, and change its settings to create a new case. In the case list, click Clone to clone the configuration. Only the case name is different from the original case. Tip 2: You can add or edit a comment when the test is running. This comment can be used to search for the test result in the Results page. This is useful especially when the test runs for a long time. |
HTTP/2 Test Case common options
HTTP/2 Test Case configuration specific to CPS
Settings | Guidelines |
---|---|
Load |
|
Mode |
Simuser: Simulated users. Simuser simulates a user processing through an Actions list one at a time. It allows you to determine the maximum number of concurrent users your device, infrastructure, or system can handle. NOTE: If the user wants FortiTester to create connections as fast as possible, the user should set the Mode to Simulated Users. What is the difference between Simuser and Connections/second? |
Requests per Connection |
Number of HTTP requests per connection. The default is 0, which means as many as possible. The valid range is 0 to 50,000. |