Service Virtualization now records each transaction edit as a version, giving release owners an attributable history they can compare and restore before a dependent test cycle is put at risk.
That capability is the most consequential control addition in BlazeMeter 3.2. The release also extends AI-assisted log investigation to multi-tests, raises the test-file upload limit, improves monitoring navigation, and adds destination controls to ShiftLeft Converter.
Version virtual service transactions for audit and recovery
Virtual service configurations often become critical test infrastructure when dependent systems are unavailable, expensive to access, or difficult to reproduce. A poorly understood transaction change can therefore invalidate test evidence or delay a release investigation.
BlazeMeter 3.2 automatically creates a new version whenever a transaction is edited. Each version captures the change and the user responsible. Teams can:
- Review prior transaction states
- Compare versions in a side-by-side diff
- Restore an earlier version when a change causes unexpected behavior
- Establish clearer accountability during incident analysis
For QA and platform leaders, this creates a practical control point without forcing teams to rebuild their working process. It is particularly useful where virtual services support regulated workflows, shared integration environments, or release gates that require traceable test conditions.
Triage multi-test failures with scenario-level AI analysis
AI Log Analysis now supports multi-tests, not only Performance and Browser-based test reports. Results are organized by scenario and include the scenario name, detected solution count, and an AI-assigned priority score.
This helps performance engineers move from a broad multi-scenario result set toward a more focused investigation queue. It can reduce time spent locating the scenarios that deserve first review, especially when test suites combine multiple user journeys or service paths.
The feature should support, not replace, engineering judgment. Teams need defined review practices for AI-generated findings, including validation against service telemetry, known environment conditions, and release acceptance thresholds.
Support larger performance-test assets
The maximum upload size for a single file used in test configuration has increased from 50 MB to 100 MB.
This removes a prior constraint for teams using larger datasets, payload files, certificates, or supporting test assets. It may reduce the need to split files or redesign test inputs solely to meet the former platform limit.
Release owners should still apply basic asset governance:
- Avoid placing sensitive production data in test uploads
- Define retention and access expectations for uploaded files
- Review file provenance before shared test execution
- Keep large assets aligned to approved workspace and project boundaries
Make API Monitoring easier to operate at scale
API Monitoring users can now pin frequently accessed buckets. Pinned buckets appear in a dedicated section at the top of the Buckets panel, and the preference persists per user across sessions.
The panel also supports independently collapsing and expanding team sections. For users who belong to many teams, this keeps less relevant bucket groups out of the active working view while retaining their team name and bucket count. The browser retains each user's collapsed state after page reloads.
These are small workflow changes with useful operational impact. Monitoring owners can reach priority bucket groups faster, while large organizations can reduce visual clutter without changing shared team structures or permissions.
Direct converted scripts to the right delivery context
ShiftLeft Converter now lets users select both the conversion output format and the destination for converted assets. Available output formats are JMX and YAML, and users can choose the specific account, workspace, and project for upload.
The last selected destination is pre-filled for later conversions. This reduces repetitive setup, but teams should confirm that the remembered destination remains appropriate when moving between programs or environments.
For DevOps and test-platform teams, destination selection provides a stronger path for maintaining project boundaries during migration from LoadRunner or SOAPUI assets. It supports more consistent ownership, access management, and lifecycle handling for converted scripts.
Operational considerations for release governance
The changes in 3.2 are most valuable when mapped to existing quality controls rather than treated as isolated product features.
Recommended actions include:
- Define who may modify and restore virtual service transactions
- Include transaction-history review in incident and release evidence procedures
- Set a human review standard for AI Log Analysis findings
- Confirm workspace and project conventions for converted test assets
- Review file-upload policies for sensitive data and large test fixtures
This is also a good time to distinguish user-local convenience settings, such as pinned buckets and collapsed panels, from organization-wide configuration and access controls. They solve different problems and should be governed accordingly.
How Merito helps
Merito helps enterprises fit BlazeMeter capabilities into an operating model that supports delivery speed and accountable quality. We can assess current test workflows, define workspace and project governance, establish virtual-service change controls, and align performance evidence with release decision processes.
For teams adopting or expanding ShiftLeft Converter, Merito can also help standardize asset migration patterns, destination rules, and CI/CD integration practices. The objective is clear: test assets and evidence stay usable for engineers while remaining defensible for platform owners, auditors, and release leadership.
Merito is an authorized Perforce reseller and services partner. Our Perforce BlazeMeter team can scope licensing, sizing, and rollout for 3.2, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.