The above illustrates a comparison between a recorded request and its playback. Using the same example script, we will perform playback of User Path “Recording1,” reviewing the same parameter, JSESSIONID, to validate that NeoLoad is automatically handling it. You will then have the ability to confirm that NeoLoad is handling a dynamic parameter, checking other parameters for their dynamic makeup. This will execute the recorded script live, as is. If you believe or know a parameter value is dynamic, you can run a playback, or validation, of the script using the checkVU feature (Check User Path). Let’s take our next step, and focus on comparisons of a recorded script to its playback. NeoLoad handles most cookie parameters and values, but if not, you know from this comparison that you have to manually do the correlation (extraction and replacement through regular expression). From the example above, we know that the JSESSIONID value is different between the two, so it is a dynamic value each time the user performs the transaction and is linked to the user session.
NeoLoad will highlight parts in green that are added to the other. Those not highlighted are the same between the two comparisons. The value is highlighted in gray, which indicates that the value is different between the two. There is a cookie header with a JSESSIONID parameter. In the screenshot above, we are comparing two requests. Let’s take a look at using the feature with two recordings to identify something dynamic:Īs you can see, when using two recorded scripts with the same transactions and requests, you can compare the request information side-by-side. This can range from common session IDs to security tokens, from unique universal identifiers (UUIDs) to transaction IDs and timestamp values, etc. By using this feature, you will be able to identify dynamic values within your application.
#Neoload correlation software
NeoLoad’s load testing software has a powerful feature that allows you to compare two recorded scripts, or compare a recorded script with the live playback to the application server. We will explore this technique using Tricentis NeoLoad. There are compelling load testing tools that have features to help with this, saving time and money. So, how do we identify what is dynamic in a recorded script through “comparisons”? Use a process to compare either two recorded scripts or a recorded script to a live playback. You will need to perform a correlation to handle the values and make them dynamic so that they are unique and different with each iteration of your script. To do so, it’s essential to be able to identify what parameters have dynamic values in your user scripts. This means ensuring your test runs on your application server with fresh, dynamic data every time. If you don’t have clean, accurate, stable designs for running your load test, you are destined to fail. There are many factors, methods, and testing philosophies that go into designing load test scripts. Scripting is the cornerstone of load testing.
0 kommentar(er)
