Displaying test status
Refer to chapter Performance Testing, Security Testing, and MITRE ATT&CK® on how to start a test case.
A few seconds after you start a test, the page automatically switches to a test status page.
You can also navigate to the status page by clicking the 
icon in the top navigation menu.
Status tab
The following figure shows the information on Status > Summary tab of an HTTPS CPS test.
The data is updated every second. It includes Layer 2, Layer 3, Layer 4, and Layer 7 data.
The following figure shows the information on Status > Throughput of a mixed traffic case.
The following figure shows the information on Status > Interface tab of an HTTP CC test.
The following figure shows the information on Status > Load tab of an HTTP CC test (Simuser mode).
The Load Generator Status chart includes the following information:
| Pcore | The physical CPU core number. |
| TCP SYN Backlog | The length of TCP-SYN queue on server side. |
| Desired Load | The desired load that you specify in the load profile, or manually request in the Load Control pane. |
| Current Load | The currently achieved load. |
| Idle Time | The idle time for this CPU, an indicator of CPU utilization. Less value means the CPU is more busy. The max value is 9999. |
If you have selected the Simusers/second or Connections/second mode when creating a case, the following window will appear beside the Load Generator Status table. You can set, increment, or decrement the desired simulated users or connections per second when the case is running.
- If you click
, the Desired Load will come into force immediately. - If you click
or 
, the simusers or connections will increase or decrease by the specified number until it reaches the Desired Load.
Client tab
The following figure shows the information on Client > Layer 4 > Port 2 tab of an HTTP CPS test.
For TCP Response Time, the following information is shown:
| TCPv4_Time_to_TCP_Syn_Ack/TCPV6_Time_to_TCP_Syn_Ack | The elapsed time (unit: milliseconds) between sending the SYN packet from the client and receiving the SYN/ACK packet from DUT. |
| TCPV4_Time_to_TCP_First_Byte/TCPV4_Time_to_TCP_First_Byte | The elapsed time (unit: milliseconds) between sending the SYN packet from the client and receiving the first Layer 7 packet from DUT. |
| TCPV4_Estimated_Server/TCPV4_Estimated_Server | An estimate of the time taken for the server to respond to a request (unit: milliseconds), derived from the formula, Time to TCP first byte - 2 X Time to TCP Syn/Ack. |
Server tab
The following figure shows the information on Server > Layer 2 tab of an HTTP CPS test.
For TCP Response Time, the following information is shown:
| TCPv4_To_First_ RX_Data/TCPv6_To_First_ RX_Data | The elapsed time (unit: milliseconds) between sending the SYN packet from the client and receiving the SYN/ACK packet from DUT. |
| TCPv4_To_First_TX_Data_ACK/TCPv6_To_First_ RX_Data | The elapsed time (unit: milliseconds) between sending the SYN packet from the client and receiving the first Layer 7 packet from DUT. |
| TCPv4_To_Connection_Close/TCPv6_To_First_ RX_Data | An estimate of the time taken for the server to respond to a request (unit: milliseconds), derived from the formula, Time to TCP first byte - 2 X Time to TCP Syn/Ack. |