Hi, This sounds really good and would like to use it too when it is shared. I don't know what's the process so I guess one of the commiters will give you an answer on this.
Just was wondering how do you use this in real life. I mean that for replaying of anonymous (non logged-in users) this is pretty easy. But what about: 1. replaying of authenticated users - do you add an additional login step later when you wanna really use this, or it also captures the login info for you? 2. what about post parameters, are they parsed out of the logs too? (It might be trivial but I never used this sampler so I wouldn't know) 3. how does it work for you if for example in the logs you have an specific Order ID which was generated by the application. The sampler won't know how to parameterize this, right? if so, do you make additional steps that are the same as when developing new scripts or using a proxy to record? This is just something I was wondering about and wanted to hear how you do it... Best, Shmuel. On Thu, Aug 9, 2012 at 5:53 PM, Enric Jaen Villoldo <[email protected]>wrote: > > Hi all, > I have created a timer class for the access log sampler, so that samples > are delayed as indicated in the access log, instead of being sent > arbitrary. > > Also, I am creating an utility class that creates a test plan from an acces > log, with one thread group for each IP. > > These two contributions make replaying the access log much more real. > > > Where is the correct location to commit these classes so you can try it? > >
