This allows all stakeholders to prioritize their time and attention only when a performance test showcases a regression in the state of performance. This gives a performance engineering organization the freedom to encourage the implementation of performance testing within the CI/CD toolchains, while receiving automated notifications from NeoLoad when a substantial performance variance is detected in the system. This allows our customers to define multiple metrics that are part of their test scenario and automatically compare them to a stated baseline value, within tolerance limits. While we view this automation of performance regression detection as most useful in CI/CD toolchains, it is broadly applicable to all NeoLoad testing activities and can be used with any test initiatives. In this new version of NeoLoad we’ve added a feature called Objectives, which allows testing organizations to define the success or failure of a test – the object of the test – to be based on static definitions, prior test results, or an automated process that determines this on your behalf. NeoLoad Web ObjectivesĪs customers add performance testing into their CI/CD toolchains as part of a continuous performance practice, the volume of test results is anticipated to expand dramatically. This feature will be available to all NeoLoad customers on a current license model as soon as you upgrade to version 2023.1. It is important to remember that full support for SSO in our protocol-based user paths has been available within NeoLoad for several years. This initial release of SSO capabilities for RealBrowser includes support for NTLM and Kerberos additional SSO options will be added in subsequent releases. These credentials will be passed when the application interrogates the browser object during the test run. We are pleased to announce that support for passing SSO credentials has been added, allowing users to specify the login, password, and critically the origin URL for SSO support. Not doing so could lead to scenarios where results could include unrealistic user paths through the system under test. When interacting with RealBrowser test scripts against applications that support Single Sign On (SSO) capabilities, the test scripts needed to be created in a way that user authentication is captured as part of the user flow. The release cadence for NeoLoad (approximately once every three months) means that our customers will have access to four releases each calendar year. There are several benefits to this new scheme as it relates to patching, support, and version currency, and will provide customers with greater clarity on how current their deployments of NeoLoad are. This is simply a naming convention change although the previous version was 9.2, the upgrade process remains entirely consistent from past versions. In this system, 2023.1 represents the first release of NeoLoad in 2023. In an effort to standardize our product version numbers across Tricentis, we are moving to a new version numbering system for NeoLoad. We are pleased to announce the release of NeoLoad 2023.1! While there are many new features and enhancements in this version of our software, this article will focus on two of the most impactful upgrades for our customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |