version: "2026" language: "en"

Release 2025.3 - November 6, 2025

In 2025.3, we are introducing full request/response parameterization, new functional HTTP steps, improved filtering, and greater visibility into performance consumption.

Parameterization in request bodies and headers

Go now supports parameterization across request components inside a sequence.

You can now insert variables into:

• Request bodies
• Request headers

This enables highly dynamic test flows, simplifies reuse, and supports execution across multiple environments without modifying the underlying sequence.

Parameterization in Timeline

We have also extended the same parameterization capabilities to Timeline.

You can now apply variables directly inside:

• Timeline request bodies
• Timeline request headers

This ensures that timeline-based performance tests are fully data-driven and flexible, matching the functionality available in sequences.

New HTTP functional steps from the context menu

To accelerate Flow creation, Go now allows you to insert HTTP calls manually in a Sequence by right-click and choosing it in the context menu.

Once done, you can select between GET, POST, PUT, and DELETE calls.

These functional steps behave like any other HTTP action in a sequence, and support parameterization, validation, and filtering.

HTTP request/response filtering

Go now includes dedicated filters for HTTP request and response data inside sequences.

You can filter on:

• Request headers
• Request body
• Response headers
• Response body

This makes it easier to find specific values, debug large payloads, and identify fields suitable for parameterization or assertions.

New Data Item: Dictionary

A new Dictionary data item is now available to support richer, structured data management.

Key capabilities:

• Supports static and dynamic key--value pairs
• Can be used for parameterization within sequences and timelines
• Ensures consistent variable management across complex scenarios

This provides significantly better support for reusable configuration values, environment-specific parameters, and structured datasets.

Timeline resource estimation (VUM & performance insights)

Go now calculates and displays estimated performance consumption metrics before executing a Timeline.

You will now see:

• Expected Virtual User Minutes (VUM) consumption
• Peak Virtual Users during execution
• Total expected runtime duration

This allows users to plan load tests with precision, control usage costs, and understand the performance footprint of each timeline.