Addition of Websocket Ping/Pong Filter modifies generated HTML report

[Nikhil Ranka]

Hello Peter,

First of all, thanks for the plugin. To an extent have set it up successfully to test web sockets.

A couple of areas where your guidance would help:

1. On using the WebSocket Ping/Pong filter noticed that the HTML report changes. Assuming that each filtered request is logged.
   Is there a way, the requests can be grouped? Based on the README, had tried this setting websocket.result.size_includes_filtered_frames=true in user.properties but the result remains the same.
   Additional Info:
   The test plan is executed from the command line

   2. Currently, in the Test Plan the Ping/Pong sampler with Ping/Pong filter is used. The purpose of using the filter is to filter Pong Requests that are sent randomly.
   Is there a way the Ping/Pong sampler can be configured to not expect Pong responses, like the pong(just send pong) option? Given the existence of Pong filter, this would prevent additional failures from being reported in the reports.

Thanks!

[Peter Doornbosch]

Hi,

Thanks for the feedback.

(1) I don’t get it. What do you mean with “the HTML report changes”? And with grouping you mean that you want to avoid you see each individual request? I don’t know, i’m not that familiar with HTML report. This is certainly not something that can be achieved by a websocket plugin setting.
websocket.result.size_includes_filtered_frames determines (as the name suggests ), whether the size of the filtered (and thus: discarded) frames should be included in the size that is reported in the sampler output.

(2) I’m afraid not .

Regards
Peter