One of the variable extractor in my script, fetching the value during 1st loop execution and passing it through the script. But the same not fetching the value during repeated loop execution (when loop count is 2 or more)
What do you get in your variable extractor content starting from loop count 2?
Could you provide screen shots so we can understand better?
State and Inmate Loop count = 2
'regionIsoCode' is extracted from '/shop/inmate-finder' from 'Search for State' transaction.
Extracted value is passed into '/shop/inmate-finder/region' at 'Select State' transaction.
(Loop1) 1st time value is extracted and passed into correctly.
(Loop2) But when 2nd time, 'regionIsoCode' is not being extracted, throws error <not-found>
I want 'regionIsoCode' to be extracted multiple times with respective loop count and to be passed on to the script.
Looking at your screen shots it seems that your variable extractor is configured to extract all occurrences. Do you need to evaluate the extraction on each loop iteration?
Also if the second extraction returns <NOT FOUND> that probably means that the server response is not the expected one. You should check on your check virtual user output to check the server response on the second iteration so you can figure out why the second time the variable extractor does not match anything.
Thank you for your support.
Yes, i need to evaluate the extraction on each loop iteration. Please suggest.
Response : HTTP/1.1 302 Found
Assertion : Variable 'extractedRegionCode' extraction failed. No match found for expression: 'isocodeShort" : "(.*?)",'
@Sumith H, did you get a solution or answer to this issue. I have have been having same problem in Neoload and did not on any solution to get by this
I see the same issue. Performing the extraction with a request action, will NOT result in the getting the new value. Is this a know bug or is there some solution?
There could be several reasons for this behaviour, looking at the original poster, we would need to see the loop value, based on the screen shot, it suggests that he has extracted one state but is looping at least twice so the second iteration won't have a state value. If you can provide more info on your issue I can help resolve it
Update. I found that if I went to advanced mode then unselected the "stop extraction at first match" the variable did get updated on each loop. Note I also kept "occurrence to extract; 1" setting.