I am creating a script for a scenario wherein people login to apply leave. I have a set of collaborators which I have included in my parameter list for login.
now, usera applies for leave on say 20th april, then userb, userc and so on.... but when usera would login again, it would fail as he can't apply leave for the same date again..
yes.. I think that's a way out.... but what worries me is thte parameter file has 3000+ users. How do I check for all of them? and while running in in PC, there would be any users logged in simultaneously.....
Could you think of something little less difficult?
Have your user login and randomly choose a date to apply for. I'm assuming that when the user applies for leave on a "duplicate" date, that the system responds with an error. Can you capture this error from the server response (i.e. "Leave Already Requested", then write some code to hande this (try again with another date, keep trying 5 times then exit gracefully, etc...)?
Also, with regard to having the same user logged in simulataneously - that is easy enough to control with your parameter settings based on the requirements of the test. Just remember that Random is not Unique. [img]/images/graemlins/cool.gif[/img]
SoCalGal - Defender of end user response times!