Neotys just released the newest version of its NeoLoad Load Testing platform, which integrates with popular Continuous Integration (CI) and Continuous Delivery (CD) toolchain elements across the entire application lifecycle.
What’s new in NeoLoad 6.1?
NeoLoad 6.1 continues Neotys’ focus on accelerating DevOps team alignment with their internal Agile and DevOps processes for greater testing coverage and application reliability under load. This release includes several new capabilities that enhance DevOps use cases, further enables Component/API Testing, improves collaboration, and adds several additional capability enhancements.
With the latest version of NeoLoad Web included in NeoLoad 6.1, collaboration with everyone involved in performance test execution or analysis is available through either a SaaS-based or on-premises deployment. The Docker-based on-premises deployment accommodates customers who have security or other concerns with using a SaaS deployment.
Generic REST/JSON Monitor:
This new capability provides easy access to any monitoring element that provides a REST/JSON API, opening up NeoLoad monitoring to provide external visibility of monitored elements during tests.
Docker Monitoring Using cAdvisor: Using the Generic JSON Monitor capability, users can easily monitor Docker-based apps (E.g., via cAdvisor).
View the Pass/Fail Status of a Test: All tests run in NeoLoad are assigned an externally-available status, which shows whether a particular test run was completed successfully or failed, based on defined SLAs. This opens up NeoLoad to more easily integrate load testing process in any CI environment. In a CI scenario where NeoLoad is automatically and programmatically run, the process exit code reflects the success or failure state.
Define Load Test Environment at Runtime:
At runtime, the same NeoLoad project can be used to launch a test in a specific environment (integration, pre-prod, etc.) without having to modify the project or having several versions of the project for each target environment.
Enhanced Component Testing with JSON Support: NeoLoad 6.1 now natively and fully supports JSON to express requests and responses for popular REST-based APIs. This enhancement makes it easier and more natural to load test REST-based APIs, and simplifies the design for complex web apps that use JSON. JSONPath expressions are supported to extract or validate data from JSON data in Variable Extractors, Validators, and Framework parameters; JSON pretty printing is also supported.
Easily Create Requests from External Content: Users can accelerate the process of API testing when creating a new request, using content that is cut-and-pasted “as-is” from an external source (e.g., from SoapUI and Postman).
Multiple Customizable, Shareable Dashboards: Easy collaboration with everyone involved in performance test execution or analysis is enabled with this innovative and Neotys-exclusive NeoLoad Web feature. It allows users to create and use several customized dashboards to organize their work, and to share test data for running tests or completed tests with other users belonging to the same account, and who work as a team on that shared dashboard.
REST API Access to Test and Monitoring Data:
The NeoLoad Web centralized REST API provides access to test data for a running or terminated test. Test data can be pushed to an external tool (e.g., Elastic Search, Tableau, etc.) and can be used to decide to continue or abort a process, for automatic testing in the context of a Continuous Integration process or to send load test values to a third-party program.
Advanced Actions Option – Consider as a Request: A new option is available for Advanced Actions so that its activity is taken into account in global statistics such as ‘All requests’ (impacting statistic value and graphs). The Advanced Action is also listed in reports and GUI, the same as for HTTP requests. When running a test that uses only Advanced Actions (e.g., JMS or MQTT testing) this capability provides visible global statistics in default graphs.
Scheduled Tests Can Send Data to NeoLoad Web: When scheduling a test, users can decide to send run-time test data to NeoLoad Web.