Then, click on the ‘Advanced’ button given at the bottom of the pane.This is the request whose response contains the required dynamic value. Select the very first request, under that transaction.Click on the very first transaction with check mark.You can see a checkmark over the icon of Action, Transactions and Requests. NeoLoad will highlight the request(s) and transaction(s) containing the dynamic value in the response.Right-click on the dynamic value and select ‘Flag in the responses’.‘BIRDS’ is passing in the third request and it is the value of ‘categoryId’ parameter. Go to the step that has dynamic value.Please note in this case, we have to correlate ‘BIRDS’. Follow the below steps once you find out the correct dynamic value. Implementation of Correlation LogicĪfter the identification of the dynamic value, the next step is to implement the correlation logic. Now, move to the correlation logic implementation part. Let’s consider, we have identified a value ‘BIRDS’ as a dynamic value that we need to correlate. Hence your investigation starts from this point. In the above example, favicon.ico is failed while performing user path validation and threw an HTTP 404 error which indicates a client-side error. If it fails then there is a possibility of correlation in that particular request. Run the ‘Check User Path’ and validate the script against ‘New User’. The easiest way to start the dynamic value identification method is ‘Check User Path’.
#Interpreting neoload test results manual#
In some complex cases, NeoLoad unable to identify all the dynamic value, hence you have to go for manual correlation. You can also skip this option if you are confident enough to carry out the manual correlation. You can use automatic correlation option that helps to identify and correlate the dynamic values by scanning the recorded script (Refer to Script Recording article). Since NeoLoad has an option to identify the dynamic values automatically based on the custom pre-defined rule (Framework Parameter) or generic rule. The first step is the identification of the correct value which is coming from the server and that value gets change with respect to the user or request or time. So, let’s understand step-by-step the correlation in NeoLoad. These three steps are also applicable for NeoLoad. Replace the Dynamic Values with Correlation Variable.As I explained in the correlation topic of LoadRunner and JMeter, there are 3 steps involved in the correlation which are: Once you record the navigation flow of AUT (application under test) and check the user path then the next step is handling the dynamic value that is ‘Correlation’ in the NeoLoad script.
0 kommentar(er)
