My question would be why? Neoload will use ${__OSVSTATE} repeatedly for a given value (ie. ABC). So ${__OSVSTATE} will be used everywhere you see ABC. Neoload will increment the variable name automatically if the framework rule matches another value, for example XYZ would be replaced with ${__OSVSTATE-1}
Because therein lies the problem I am having right now. The values are different each time.
Now I am getting ${__OSVSTATE} = ABC and ${__OSVSTATE} = XYZ.
I want ${__OSVSTATE-1} = ABC, ${__OSVSTATE-2} = XYZ, etc.
For every screen I open within the webapplication another ID is given. For most of the time the values appear in order. However, the variable name does not increment automatically. For which I am used to getting.
I believe this depends on scope, if ABC is extracted and used, THEN... XYZ is found, extracted and used, the variable name is reused.
Yes, that what happens at the moment. Is there a way to force incrementing variable names? Because I have 40 of such values and the way they are extracted is not always in the same way. Making them unique would also help with correlating, as in what is what.
I’m not aware of a way of forcing naming. Reusing variables is managed by Neoload and is likely there to maximise efficiency and minimise resource consumption.
