[Service Virtualization]: Messaging Support for ActiveMQ Classic & ActiveMQ Artemis

BlazeMeter Service Virtualization now supports ActiveMQ Classic and ActiveMQ Artemis, expanding JMS-based messaging simulation to include two of the most widely used message brokers in enterprise environments.

Highlights include:

  • Virtualization of both JMS producers and consumers
  • Full support for Point-to-Point (Queue) and Publish-Subscribe (Topic) messaging models
  • Request/Reply support for simulating synchronous flows over asynchronous systems
  • Message recording from virtualized producers or consumers to auto-generate realistic Messaging Virtual Services

These capabilities enable comprehensive end-to-end testing of asynchronous systems without needing access to live infrastructure. They enhance test coverage, resiliency, and scalability.

 

 

[Service Virtualization]: Enhanced Messaging Configuration & Connection Validation

We’ve simplified Messaging Broker configuration to accelerate setup and reduce friction.

New features include:

  • A Test Connection button to validate broker connectivity before launching a Virtual Service, helping catch setup issues early
  • Support for dynamic name/value pairs in the Configurations tab, eliminating hardcoded values and improving environment flexibility

These updates promote reusable configurations and help teams maintain clean, scalable service definitions across test environments. 

Picture, Picture 
 

[API Testing & Monitoring]: AI Script Assistant: Now Converts Postman Scripts

The AI Script Assistant has been enhanced to help convert Postman scripts into BlazeMeter-compatible syntax for API Monitoring.

Trained using real-world examples submitted by users, the assistant now supports most common patterns, making it easier to migrate tests and reduce manual script rewrites.

Note: Some highly custom logic may still fall outside current support, but coverage and accuracy continue to improve rapidly.

 
 

[API Testing & Monitoring]: DNS Errors Now Reported as Custom Status Code (50000)

 To improve visibility and automation, DNS errors are now exposed as a dedicated custom status code: 50000.

This code can be used in:

  • Assertions
  • Extractions
  • Post-response scripts

This allows your tests to detect and respond to DNS issues programmatically, reducing the need for manual result inspection and increasing workflow resilience.