We’ve added details about the test status, test name, script name, whether dedicated IPs are used and the status of each session - multi-location/multi-test. We’ve also enlarged the elapsed time indicator and moved links to learning resources to the bottom left.
Are you testing your system behind a firewall? You’ll be happy to hear that we’ve made the installation process of our on-prem testing much simpler.
We’ve updated the Usage Report both in the UI and the CSV document. Six columns have been added:
Note: You can enjoy the improved reporting abilities for data created as early as January 2017.
We’ve enabled adding OAuth tokens to your API tests.
We’ve added the ability to create tests for every operation in your API with the single click of button.
We’ve enabled executing API Quick Tests by using Private Locations behind a firewall.
We’ve added the ability to make changes to the API Key or Basic Auth for your API tests without having to regenerate all of your tests. Your authentication changes are automatically applied to your tests the next time you execute them.
New geo-locations available:
You can now run your BlazeMeter tests through Azure’s geo-locations.
Use the scripts from your shared folders while functional testing, to save time, reduce friction and improve your workflow
We would love to hear what you think.
Have you verified that your API isn't vulnerable to a SQL injection attack? The API Test Maker now lets you create SQL injection tests. Confirm that each endpoint in your API is safe.
You can still find all the good stuff in the Timeline Report: