I have been recording using NeoLoad 5.0.2 against my application. I've been noticing that it is putting traffic into the wrong container, i.e. rather than putting it into the container it should it is putting it into the container after so requests/responses are in the wrong one. I am following the correct procedures, i.e. container name is inputted before I do any actions, and I'm ensuring that after performing a website action I am waiting until the response has been fully received before moving on to the next container. Has anyone experienced this or got any advice? I can fix the issue by manually moving the requests into the right containers but the issue should not be happening in the first place.
When you say that iit s putting the requests in the wrong container, do you mean that you write your container name in the recording bar, you click on your links, wait and you do not see your requests inside that container but only when you start creating a new container in the recording bar?
Could it be because of asynchronous requests issued by the browser? I mean some requests can be sent by the brower without user interaction like when you have PUSH technology involved.
I can assure you that PUSH technology is not involved in this situation. It is as you described though, I write a container name, do my actions and wait for it to fully load. I then go onto my next container and do the same. When I then view the recorded virtual user profile the actions I am expecting in container 1 seem to be in container 2 and those I am expecting to see in container 2 are in container 3 etc. This was never an issue when I was using Neoload 4 to record against the exact same application and I am not doing anything different.