The Client Message operation corresponds to a WebSocket client message that a web client application sends to the tested web server in your scenario. These operations are recorded. You cannot create them manually in the scenario editor. However, you can move these operations between pages in the recorded scenario.
For information on WebSocket support in LoadComplete, see Support for WebSocket Protocol (HTML5).
|Number of occurrences:||Unlimited.|
|Parent operations:||Connection, Page (if connections are hidden in the editor), Scenario (of both connections and pages are hidden), Group, If... Then, If... Else, Loop, While|
|Child operations:||The operation cannot have child operations.|
The Think time box at the top of the editor specifies the number of milliseconds to wait before sending the request.
The SLA edit box at the top of the editor specifies the maximum acceptable duration of the operation, in milliseconds. For WebSocket client messages, the duration is estimated as the time spent on sending the message.
The editor uses the following panels to display operation properties:
|Message Header||Standard and custom headers of the message.|
|Message Contents||The message contents (if any).|
|Data Replacers||A list of rules for replacing message contents with variables. You use this feature to insert needed data to your messages. For instance, to implement data-driven tests, you may replace recorded data with data loaded from a CSV file or Excel sheet.|
|Uses Data From||A list of requests and WebSocket messages, whose data are used in the given message. LoadComplete extracts data to variables, so the panel displays variables as child items of the request or WebSocket message.|
Information about the erroneous settings is displayed in the editor’s header area.