Introducing NeoLoad 7.0

Dynamic infrastructure for Open Shift

Dynamic infrastructure is NeoLoad’s new capacity to interact with container orchestrators, currently OpenShift, to provision and use load testing infrastructure automatically, on demand. When a test is run through NeoLoad Web, controllers and load generators are spun up for the duration of the test and released once the test is finished. The load testing resources are automatically provisioned with pre-set settings within a minute of executing a test on demand and the Docker containers are shut down and released once the test is complete. NeoLoad leaves the machine automatically cleared and ready for any use.

No need to write lengthy scripts to provision machines, manually connect dynamic testing resources to CI pipelines, or manually change the number of load generators used for a test. With dynamic zones, connect to testing resources in OpenShift with a few clicks. Infrastructure is set up only once. Later, increase or decrease the number of load generators easily with a slider scale. Reduce the total cost of hardware ownership as you do more with the same testing resources without the need to tie up machines indefinitely or manual steps to release and reconfigure machines. Reuse the same machines for multiple purposes beyond testing.

Resource reservation generally available

Resource reservation, previously released in preview mode, is now generally available. With resource reservation, reserve load testing infrastructure (controllers and load generators) and virtual users by date and duration to guarantee resources are dedicated for application performance testing for a specific team or team member and avoid testing schedule conflicts among the teams. Share and reserve resources as a team or an individual — any member of the team can cancel, modify, and use the reservation. Optimize test infrastructure usage and improve team collaboration and productivity with resource reservation.

Other enhancements

• Enhanced Dynatrace integration: The HTTP header name used between NeoLoad and Dynatrace can now be customized to use the same value as other testing tools in your stack. Creating Dynatrace settings is now easier and homogeneous for all tools. The working default value is the one recommended by Dynatrace.
• New CSV data format: The format of the .csv created when exporting raw data at a transaction level has been changed and is not compatible with the previous format. Updates include the elapsed time, which is now in milliseconds, a new absolute time, and a virtual user ID to identify the instance of the virtual user.