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.
.png&w=2560&q=75)
