January 2018 Release
What’s New in NeoLoad 6.3?
NeoLoad 6.3 is now available. This latest release includes enhancements in the areas of NeoLoad platform openness and core load testing features. NeoLoad 6.3 includes several enhancements that make it more useful in environments like banking, healthcare and government that have stringent security concerns. Business that use Windows environments will also find that NeoLoad 6.3 is easier to use. Business that use Dynatrace as part of their performance testing ecosystem will find that NeoLoad 6.3’s enhanced integration features will lead to easier use and higher operational efficiency.
NeoLoad Web – Expanded REST API Support
NeoLoad Web’s REST API provides methods to enable the following actions (which are accessible through the GUI):
- Modify the name, description or success status of a test
- Delete a test result
The ability to modify the success status of a test through the API enables a tester to completely define and customize success or failure criteria for tests. Testers can programmatically (using the REST API) define what success/failure means, based on data from test results which they can access using the same REST API.
Enhanced Security for Test Credentials
After making a recording for a test, the credentials used to make the recording are not stored in plain text. Because of this, a person cannot use NeoLoad’s configuration files to access credentials to improperly gain access to a system.
- Testers can declare and use “password variables” that are always encrypted when stored, but are unencrypted when used during tests
- Recorded forms containing passwords are identified; passwords on those forms are replaced by password variables. This means the stored version of the generated script will contain an encrypted version of the password
- Passwords in recorded requests are hidden so that nothing is stored clear on disk
Enhanced Dynatrace Integration
NeoLoad 6.3 includes enhancements to both Neoload’s native integration with Dynatrace, as well as a bundle of Advanced Actions leveraging the analysis of load testing using Dynatrace’s OneAgent. The expanded capability means tighter integration with a key element of the testing ecosystem, leads to faster test cycles, and enables pre-production (“Shift Right”) as well as Component/API-level testing (“Shift Left”) testing.
These new features make it easier and more effective to interact with Dynatrace APM deployed in the testing environment while load testing an application with NeoLoad. With that setup, testers can precisely analyze how the whole application and its ecosystem is behaving.
Details – Native Integration
The native enhancements for Dynatrace support in NeoLoad 6.3 are as follows:
- Testers can now target several system profiles during a session recording with Dynatrace
- During a Dynatrace session recording, testers will now know exactly to which test the recording is associated with, in addition to the NeoLoad project name and scenario
Details – OneAgent Custom Actions bundle
A bundle of Advanced Actions is available for download from Neotys Labs that provides the following actions :
- DynatraceEvents: Links a load testing event to all services used by an application monitored by Dynatrace.
- DynatraceMonitoring: Inbound from Dynatrace to NeoLoad: Retrieve Infrastructure and Services metrics from DynaTrace (AppMon or OneAgent) and insert them in NeoLoad External Data so that you can correlate NeoLoad and DynaTrace metrics within NeoLoad.
Microsoft Monitoring Enhancements
Monitoring a Windows machine or a Microsoft Server (SQL Server, IIS, .Net) offers new authentication capabilities. Instead of using the account of the user that launched NeoLoad or the Monitoring Agent, NeoLoad also offers the possibility to specify the account to be used to connect to each Windows machine or service (SQL Server, IIS, ASP.Net).
Access to NeoLoad Web URLs from within NeoLoad
A tester/developer writing “glue code” within NeoLoad’s GUI that integrates with other tools can easily access URLs related to NeoLoad Web making the integration tighter with NeoLoad Web. The tester/developer can access the following URLs:
- The NeoLoad Web front-end
- The entry point of the NeoLoad Web APIs
- A running test in NeoLoad Web
Testers/developers can also access Proxy settings in different situations and points of the product:
- From the standard command-line output (Stdout) when running a test from there, the URL of the running test is clearly displayed
- When using the NeoLoad GUI Runtime API access to the running test URL
- When using either the Custom Action API or the JS API, access is available to both the URL of the running test and the NeoLoad Web front-end URL