I had a similar requirement:
In my test plan an http request was being called like this:
/myurl/a/b/c/trackid=abcd-efgh
Where abcd and efgh are unique numbers for each User (Thread) / Loop.
I added a User Parameters control before calling this http request like
this:
Name 1: id_first
User_1: ${__Random(1,1000,ID_FIRST)}
Name 2: id_second
User_2: ${__Random(2001,3000,ID_SECOND)}
Then I replace these variables in the original http request like this:
/myurl/a/b/c/trackid=${ID_FIRST}-${ID_SECOND}
Notes:
a) I checked the option Update Once Per Iteration in the User Parameters
control
b) My test plan has other http request that need the same calculated track
id for that User / Loop.
b) I first used id_first and id_second but every time I call them in other
http request the random numbers are re-calculated. Using ID_FIRST and
ID_SECOND solved that problem for me.
I hope this is similar to your problem and can help you.
Regards,
Rodolfo
On Wed, Jun 2, 2010 at 12:12 PM, virkenator <[email protected]> wrote:
>
> Hi Deepak,
>
> Thank you for the help. I tried it, but in vain. May be I need to explain
> you more details. When I create a patient, that data needs to be posted
> through the HTTP request to the server.
> Here is how my script works.
> 1. A user logs in
> 2. Goes to the patient registration form.
> 3. Adds patient id, which has to be unique every time patient needs to be
> added.
> 4. Saves the form and logs out.
> This script has all the HTTP requests. During the step 3, there are two
> fields(patient id and patientkey) which need to be edited (which I am
> presently editing manually) and posted as the HTTP request for step 3.
> I am wondering is there any way, I can increment or create unique values
> for
> these two fields and then POST them as a HTTP request automatically.
>
> Deepak Shetty wrote:
> >
> > This is one way
> > add a User Parameters , just one user will do, specify the name like
> > currentTime and value like ${__time(YMD)}${__time(HMS) . Also check
> update
> > once per iteration (basically generating a timestamp , you can use other
> > ways to generate a timestamp too , the reason I do it this way is that I
> > need this value for multiple samplers)
> > Then when you need to post a unique data element, you can provide a value
> > like
> > ${userIdPrefix}_${__threadNum()}_${currentTime}
> >
> > where userIdPrefix is a variable normally defined as JMeterCreatedUser or
> > something .
> >
> > Note that because JMeter can call javascript or even Java/BSH any method
> > you
> > want of generating unique ids works (for example you could use UUID's)
> >
> > regards
> > deepak
> >
> > On Tue, Jun 1, 2010 at 4:42 PM, virkenator <[email protected]> wrote:
> >
> >>
> >> I am a newbie. I am using JMeter to test registration form based
> >> software.
> >> Here's my scenario:
> >>
> >> A user logs in and adds a patient in database. I am able to automate
> this
> >> process by recording it, however I want to automate the add patient
> >> scenario, since a unique patient id is required to add a patient and
> save
> >> it
> >> on the database. The procedure I am following right now is manually
> >> entering
> >> ids and then running the automated script, which is not putting any load
> >> or
> >> stress on the site.
> >> If somebody could please tell me how to generate unique ids and how to
> >> fit
> >> this procedure in already working script or how to increment previous id
> >> whenever the script is run.
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/how-to-generate-unique-ids-in-jmeter-tp28748660p28748660.html
> >> Sent from the JMeter - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/how-to-generate-unique-ids-in-jmeter-tp28748660p28758835.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
