Releases

NeoLoad 6.8

NeoLoad 6.7

NeoLoad 6.6

NeoLoad 6.5

NeoLoad 6.4

NeoLoad 6.3

NeoLoad 6.2

NeoLoad 6.1

NeoLoad 6.0

January 2019 Release

What’s New in NeoLoad 6.8?

Automate Performance Testing in Enterprise Bimodal IT Environments: NeoLoad Covers Traditional and Agile Approaches

NeoLoad continues to build support for the Enterprise bimodal IT organizations who develop and test applications with two separate styles of work:

  1. Waterfall development for existing application maintenance and internal business operations
  2. Agile development for digital innovations

The NeoLoad performance testing platform covers the range of these application and API testing needs and optimizes performance testing within both development methodologies.

Testing, updating and maintaining the range from modern to legacy technologies continues to get easier with NeoLoad. New integrations include Tricentis Tosca, an SAP GUI functional testing tool, and enhancements to NeoLoad’s Data Exchange API. To support rapid application development of innovative applications, use the additional capabilities in the Shift Left feature set. NeoLoad 6.8 introduces Test Design as Code and the ability to branch and tag tests within GIT. Enhancements to NeoLoad’s Data Exchange API also help developers and testers performance test in agile environments.

Tricentis Tosca Integration

Use NeoLoad’s pre-built integration with Tricentis Tosca, a functional testing tool for SAP GUI applications. Convert functional test assets from Tosca into performance tests in NeoLoad with one click. As functional scripts change, NeoLoad uses the changes to update the performance test. Be more productive when creating and maintaining performance test designs for the monolithic SAP application updates and new implementations. Share and repurpose test assets across applications throughout the develop and test cycles and collaborate better as a team. NeoLoad is the only platform on the market that has this capability.

Available on GitHub.

Data Exchange API

Import third party data into NeoLoad’s dashboard from multiple sources like APM tools that monitor the same applications being tested under load. Show performance test results from NeoLoad and monitoring results from APM tools that test the same application, in one dashboard. Alternatively, expose the NeoLoad performance test results in the APM tools as well with the two-way data exchange.

Teams can share results across dev, ops, testers and business owners.

Test Design as Code

Previous NeoLoad releases enabled the definition of test settings in domain specific language (YAML). Now, design performance tests as you code with NeoLoad 6.8. Integrate performance testing into continuous integration pipelines. Define test script and settings as code to enable automated CI/CD processes to update and maintain tests and to consume and use results. (This is not possible if you rely on a GUI definition that requires a human to open NeoLoad.) Use IDEs and CLIs to develop, run, and maintain performance tests for APIs. Find performance issues early and often when they are easier and less costly to fix. With minimal coding, set the tests’ population, VU path, transactions, requests, delays, variables and etc.

Read more in the documentation.

GIT Branches and Tagging

Integrate with GIT to version control and collaborate on performance tests using NeoLoad’s GIT integration. NeoLoad now provides the ability to choose branches and align branches for the Integrate with GIT to version control and collaborate on performance tests using NeoLoad’s GIT integration. NeoLoad now provides the ability to choose branches and align branches for the different versions of the tested application. GIT users work on branches (Push/Get) and with Tags (Tag and retrieve a Tag) to improve test asset reuse and team collaboration. Build performance testing into agile SDLC pipelines to continuously improve software delivered.

Enhanced Webhooks Support

Introduced in NeoLoad 6.5: Integrate performance testing into test ecosystem with Webhooks. Configure the applications to be notified, for example, inside SMS or Slack, from triggers like a test begins or ends, into a complex CI workflow and automate performance triggers (for example, stop the CI process if a performance test fails). Or use webhooks as a simple notification mechanism, for example, adding a row to a Google Sheet as a log for load test activity.

Now: NeoLoad’s support for webhooks is advanced. Test IDs are now provided as variables for the webhook payload – the NeoLoad Web API can be called to perform custom actions in the CI pipeline. A link to the graph summary of the test is also accessible in the payload.

How to Update to NeoLoad 6.8

Provided you have a valid support package, here’s how to update your version of NeoLoad:

  1. Download NeoLoad 6.8
  2. Install NeoLoad in a new directory (do not install on top of the old version).
  3. You don’t need a new license key. You will just be asked to activate your current license key for version 6.8
  4. Make sure you back up your projects before using them with the new version.

Get more information about upgrading NeoLoad to version 6.8, NeoLoad Web on-premise to version 1.8 or download the NeoLoad Free Edition!

Keep Me Informed