As every tester knows, software testing is not a one-size-fits-all practice. Needs vary based on scope, size, and available resources.
Often, in the middle of a testing sprint or when the test results are being analyzed, a tester may find them wishing their testing tool could do more for them. For many testing tools on the market, what you get is...well, what you get.
Not with BlazeMeter.
With BlazeMeter, you get a tool built for and a team dedicated to customer success. And part of that dedication is taking feedback and implementing it into our offerings. We work closely with our partners to understand their pain points and work to improve BlazeMeter testing to alleviate those pain points.
Our Service Virtualization capabilities directly address customer pain points in a variety of ways – bridging testing gaps with a multitude of helpful features that were worked on together with customers to deliver the value they needed.
In this blog, we will break down several BlazeMeter Service Virtualization features that were either improved upon or created based on valued customer feedback.
5 BlazeMeter Features Created Based on Customer Feedback
At BlazeMeter, we pride ourselves on being an incredibly flexible solution. If there is something within your unique testing workflow that is not being addressed or could be done better, we will create a solution that works for you. Below are the results of the kind of collaboration we pride ourselves on.
Support for data models with Import/Export function
When using BlazeMeter’s Service Virtualization, users can now export test data for backing up and then also import it back into the service as needed. This applies to all test data assets (including CSV files).
Issue: If a Service was lost or deleted, there was no way to get the test data models back into the Service. Import/Export had worked at a Service level; everything related to the Service was exported except the test data models.
Solution: By adding support for Test Data models, we are enabling the exported zip file to contain all the test data models used within that Service.
Value: Time saved and re-work eliminated.
Update the location of a Virtual Service
Users can now change the location of an existing Virtual Service.
Issue: If a customer decides that – due to heavy use of Virtual Service and Performance Testing – they must separate the private locations for both components.
Solution: Both the Virtual Service and Performance Testing can be split across two separate private locations. You can now create a private location specific to the Virtual Service. Then they would move all their Virtual Services from the current OPL to the new OPL.
Value: Time saved and more efficient test execution.
Deploy multiple Virtual Services on same port
Users can now deploy multiple Virtual Services on a single port that is exposed to the applications within the network. Rather than exposing dozens of ports for dozens of Virtual Services, users can expose only a certain number of ports if they choose.
Issue: Each Virtual Service required its own port for running. If a user was using private locations, this meant they would need 100 open ports for 100 Virtual Services. This many open and exposed ports could lead to security issues.
Solution: On private locations, users can now create groups of Virtual Services. Each group consists of only a handful of ports that are opened, which makes it far more efficient and secure.
Value: Improved security and time saved.
Update Virtual Service name
Previously, users could only name a Virtual Service as it was being created. There was no way to change or edit the name once it was created. Now, once the Virtual Service is stopped, users can rename it as they see fit.
Issue: Users could not change the name of a Virtual Service without deleting it.
Solution: Once the Virtual Service is stopped, a user can rename the existing Virtual Service and adhere to their preferred naming convention without having to create an entirely new Virtual Service.
Value: Improved organization and more efficient testing.
Reliability and recovery of transactions
Deleted transactions are now available to recover within 30 days of deletion. This is an Admin-level feature only. If a user deletes a transaction by accident, they can reach out to their Admin to recover it.
Issue: If a user deletes a transaction, there was no way for either the users or their Admins to recover it. Once deleted, they are lost forever.
Solution: Deleted transactions are now available for recovery within 30 days of their deletion.
Value: Time saved and more efficient test execution.
Bottom Line
At BlazeMeter, we pride ourselves on delivering a testing solution that suits any set of unique circumstances or needs. Our leading Service Virtualization capabilities make the lives of testers easier by saving time through efficiency and enhanced productivity. If there is a feature that is currently not available and a user feels it would be helpful, we work closely with them to make that a reality.
Start testing with the industry’s most flexible performance testing tool for FREE today!