March 2018 Release
What’s New in NeoLoad 6.4?
NeoLoad 6.4 is now available. This latest release includes enhancements in the areas of NeoLoad platform openness, Component/API testing, and make NeoLoad more compatible with new server-side technologies. Businesses that use New Relic APM as part of their performance testing ecosystem will find that NeoLoad 6.4’s enhanced integration will lead to higher operational efficiency and better analysis of load testing data.
NeoLoad Web – Centralized SLA Summary
Through NeoLoad Web, performance and load testers and other performance stakeholders can quickly understand and identify why a test has failed, with a new, centralized summary page that shows SLA status within NeoLoad. The SLA summary gives you the means to understand why your test has failed. Success or failure of a test is based on defined SLAs, and that all defined SLAs have succeeded. The centralized SLA summary lets you see exactly which SLA failed, and specifically why it failed the defined SLA parameters.
Easier Validation for JSONPath and XPath Responses
Testers doing Component/API testing need easier validation of responses based on content type criteria than was available in NeoLoad 6.3’s implementation for native support of JSON. This new feature speeds up the workflow for testers. Testers using NeoLoad 6.4 are now able to specify EITHER use JSON or XPath when creating a variable extractor or defining a response validation, independent of the Content-Type of the response.Previously, NeoLoad forced you to use the same content type (JSON or XPath) specified in the response extraction type. Now JSONPath or XPath can be used for all requests including manually-defined ones.
Automated Cloud Test Infrastructure
DevOps-focused teams doing automated performance testing are used to being able to use any desired mix of cloud and on-premises load generators. As DevOps practitioners, they may be a lot more comfortable with taking an API-based approach rather than a CLI-based approach. Automated tests can start and use a cloud session using the NeoLoad Runtime API. The API lets users specify the characteristics of a Cloud session, including the desired mix of cloud and on-premises load generators, and can refer to VUH or Cloud credits. This cloud session can then be automatically started and used by an automated test. This feature results in a higher level of test automation, saving time on each test iteration throughout the SDLC.
Additional APM Integration Available
NeoLoad’s integration portfolio with leading APM platforms – Dynatrace, CA, and AppDynamics – has just expanded to include New Relic. A new NeoLoad advanced action enables the analysis of load testing data using NewRelic APM and New Relic Insights. This advanced action provides both an inbound (extract New Relic APM data to NeoLoad to be viewable within NeoLoad’s dashboards) and an outbound (extract NeoLoad load testing data and send it to New Relic’s Insights tool) integration. The Advanced Action is available on Neotys Labs, including a Tutorial Document that shows how to use it. It is also available from NewRelic Plugin Central (in-product) and the NewRelic website. Documentation & Screenshots available from https://github.com/Neotys-Labs/NewRelic
Brotli Server-Side Compression Method Support
Servers and Browsers negotiate a compression algorithm to compress the response content. Brotli server-side compression was created by Google and is named after a Swedish pastry. Brotli is a generic-purpose lossless compression algorithm that compresses data using a combination of a modern variant of the LZ77 algorithm, Huffman coding and 2nd-order context modeling, with a compression ratio comparable to the best currently available general-purpose compression methods. The specification of the Brotli Compressed Data Format is defined in RFC 7932. It is similar in speed with deflate but offers demonstrably denser compression than zopfli, LZMA and bzip2.