Vulcan Knowledge Base

Load Test Scenarios

Connecting to a Chassis

Different load test scenarios use different communication patterns. There are three load test scenarios you can create, None, Raw, and Transaction/HTTP GET. Click Add Scenario button, to see the dialog window for scenario selection as shown below.

None Scenario

A None type scenario provides the simplest communication pattern: establishes connections, keep connections, and close connections. You can use this scenario to test DUT’s capability of connection per second (CPS), concurrent connections, or simply a connection ping (whether a connection can be established or not).

Raw Scenario

A Raw type scenario establishes connections, generating traffic, and close the connections. The direction of the traffic can be configured as client-to-server (upload), server-to-client (downstream), or bidirectional.

Transaction Scenario

Different from Raw scenario, a Transaction scenario uses the request-response commutation model. After a connection is established, the client will send a message to the server to emulate a request. Upon receiving the request message, the server will respond a message to the client.

This communication model is so called client-server model. It is the fundamental communication framework for the majority of applications on the internet. Many applications are based on this communication model, e.g. WWW, email, network printing.

HTTP GET Scenario

HTTP GET scenario is a special Transaction type in that the content of the request and response are predefined to be HTTP request and response. The content of the request message is predefined to:

GET / HTTP/1.1\r\n

The content of the response message is predefined to:

HTTP/1.1 200\r\n

Content-Length: 1\r\n

Content-Type: test/plain\r\n