March 2018New Versions Supported: JMeter 4, Java 9, Taurus 1.10.5 Now you can run JMeter 4, Java 9 and Taurus 1.10.5 on BlazeMeter. We will deprecate JMeter versions <2.13 in April. When we do, we’ll execute these older scripts using the 2.13 engine. Now is a great time to check to see if your <2.13 scripts need edits to run on 2.13. JMeter is great at backward compatibility, but better safe than surprised :-) Sandbox IP Address List Change We have updated our Sandbox location to be served from the following six IP addresses. If you have whitelisted our Sandbox location, you will want to update your whitelist to the following:35.171.138.25135.171.125.5335.171.138.23635.169.68.1234.227.202.25035.170.212.9 Chrome Recording Extension Upgraded The Chrome recording extension has been upgraded:Create and name Transactions as you do your recording with “Edit Transaction Labels”Choose which requests to record with greater precision (i.e. top level requests + cookies, for instance)Run tests as “API Functional Tests” (single VU with enhanced reporting) CloudWatch APM data moved to the Timeline Report CloudWatch now joins our other “inbound” APM integrations on the Timeline Report. Previously CloudWatch data appeared on a separate report tab. Enjoy the streamlined experience :-) Overlay your own data on the Timeline Report (coming soon!) Ever wish you could overlay your own time-series data on the BlazeMeter Timeline Report? We’ll be releasing an API soon which lets you post JSON data to overlay on any test, even in real time. Watch for an update in the next release or drop a line to beta@blazemeter.com if you want to get started right away. Summary report graphs change resolution @ 5 min mark The time-series resolution in the Summary report graphs now changes at the 5-minute mark:In the first five minutes of the test, the graphs show one-second resolution.After five minutes, the graphs switch to one-minute resolution. Taurus Tests now configured on New Test Create Screen Starting today, when you press the “Taurus” test create button, you’ll go to the New Test Create (NTC) screen being rolled out as part of our New Test Create Beta. For advanced users who have been running Taurus tests on BlazeMeter for some time, you’ll be interested to hear that the default execution framework is moving from “Taurus V1” to “Taurus V4” with this update. New Test Create (NTC) Beta Updates We’ve been gradually rolling out a new test create workflow and underlying test execution architecture since earlier in the new year. Here’s a peek at what we’ve added in the most recent drop. If you have questions about the beta (including requests to join the beta and try it out so you can influence our final builds), please drop us a line at beta@blazemeter.com. NTC: Load configuration enhancements The scrolls are “exponential” so that it is easier to configure using them.The test visualization graph now shows a “zoomed in” view of the ramp up period, with ⅔ of the space showing the ramp and ⅓ of the space showing duration of the post-ramp hold period.We added support for the “Limit RPS” setting and “Change RPS” mid-test button. NTC: Debug Test The Debug Test button launches a quick run of your test at low scale to confirm that everything works from the cloud. Unlike the “sandbox test” feature in the previous version, with Debug Test, your settings (such as scale, location or duration) aren’t changed or reset in any way. We also write out a more detailed “trace.jtl” log for these runs to assist with troubleshooting. NTC: File Validation When you upload a file in New Test Create, we validate the uploaded file, checking for:Missing files that are part of configuration (referred within a yml)Broken JMX (XML issues)Invalid YMLTaurus configuration errors The validation occurs automatically on file upload and you can re-validate on demand by clicking the “Revalidate” after making corrections/uploading new files.
