The network activity action lets you capture network traffic while an ATS test is running.

‍

Use the network capture recording action

There is one prerequisite for enabling network activity capture:

In the channel start action, you need to activate the recorder button

A green dot appears when the action is successfully activated, and the network activity icon is added to your channel start action.

‍

You can then add the network capture action to your script.

This action has two functions:

‍

Capture network settings

Cette action vous permet de paramétrer la capture du réseau. Elle n’est pas obligatoire, vous pouvez ajouter des paramètres au cours du test.

This action allows you to set the network capture settings. It is not mandatory; you can add parameters during the test.

This action can be called multiple times to change the attributes.

‍

• Latency

This voluntarily adds seconds of waiting time before each network traffic request.

‍

• Traffic idle

When an action is executed, there are potentially several background requests (invisible to the user) running on the application.

For each ATS action running on an application, the record will retrieve all background requests.

With this parameter you can determine the maximum response time after each request.

By default, the waiting time between a request and its response is 3 seconds.

Beyond the waiting time entered, if the request is not answered, the test execution continues and this request will potentially not be counted in the final capture.

Example :

If you send 10 requests, you're bound to wait for 10 responses. If, during execution, only 6 requests have been answered after 3 seconds, then the test will continue and you will potentially only see these 6 requests in the capture.

‍

• URL filter

This parameter lets you filter the URLs to which requests can only be sent.

You can manually add one or more URLs to which requests will be sent.

These URLs are in the form of regular expressions.

‍

• Bandwidth limit

By default, the data reception rate is not limited.

You can set a maximum number of bytes per second for a download or upload limit.

Examples of use: If you want to simulate a weak network connection or a site with degraded performance…

‍

Recorder action

The recorder action records network traffic during script execution.

The action breaks down as follows:

• Pause recording of background requests
• Resume recording of background requests

‍

All actions between the record on action and the record pause action will be recorded.

‍

Capture result

Once the script has been run, you can retrieve the capture in the target > networkcapture directory.

You'll find one capture per channel launched during script execution.

‍

This will generate HAR files with unique identifiers and data in JSON format.

In this file you'll find the list of requests linked to specific actions in the test scenario (see the URL used, URL details, server response, etc.).

‍