You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Rob Brandt <rb...@csd-bes.net> on 2010/12/08 07:42:31 UTC
Advice on a testing plan
I am a new jmeter user and am using it to test load capabilities on a
content management/social networking website.
We are particularly concerned about our user registration scenarios, in
which new users tend to come in waves. The registration process has
specific steps; 1) submit a form with user info; 2) fill out a survey;
3) update a "project" form, and 4) make a comment on the project. New
registrants must enter a unique "ticket" number which can only be used
once, each user is permissioned to only fill out the survey once, can
only update their own project form, can comment on any project once
logged in.
I am working my way through setting up jmeter to fully process 1 user as
above. Almost done with that. I am aware that there's some import
facility to load data for the test. I am thinking I will have to load
each ticket registration as a separate test; so, a few hundred different
tests, each with one user and not repeated. Am I thinking about this
right, on the right track?
I am concerned with how jmeter handles sessions, cookies, etc. Since
each user has a unique ticket number that can only be used once, then
must fill out a survey once and only once, update a specific project
page, does jmeter track this correctly? Will I need to include a logout
request at the end so that the "user" tracking doesn't get confused?
Thanks
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Advice on a testing plan
Posted by Rob Brandt <rb...@csd-bes.net>.
Thanks! As I said, I'm new to this, and wasn't aware of the CSV Dataset
Config. Sounds like just the ticket :)
Rob
On 12/8/10 3:51 AM, sebb wrote:
> On 8 December 2010 06:42, Rob Brandt<rb...@csd-bes.net> wrote:
>> I am a new jmeter user and am using it to test load capabilities on a
>> content management/social networking website.
>>
>> We are particularly concerned about our user registration scenarios, in
>> which new users tend to come in waves. The registration process has
>> specific steps; 1) submit a form with user info; 2) fill out a survey; 3)
>> update a "project" form, and 4) make a comment on the project. New
>> registrants must enter a unique "ticket" number which can only be used once,
>> each user is permissioned to only fill out the survey once, can only update
>> their own project form, can comment on any project once logged in.
>>
>> I am working my way through setting up jmeter to fully process 1 user as
>> above. Almost done with that. I am aware that there's some import facility
>> to load data for the test.
>
> CSV Dataset Config can be used to provide the ticket data.
>
>> I am thinking I will have to load each ticket
>> registration as a separate test; so, a few hundred different tests, each
>> with one user and not repeated. Am I thinking about this right, on the
>> right track?
>
> Why have lots of tests? Why not use a variable for the ticket and vary
> the data at run-time?
>
>> I am concerned with how jmeter handles sessions, cookies, etc. Since each
>> user has a unique ticket number that can only be used once, then must fill
>> out a survey once and only once, update a specific project page, does jmeter
>> track this correctly?
>
> JMeter does not do any automatic tracking.
>
> If you provide a Cookie Manager it will handle cookies (don't use
> auto-redirect unless you are sure that redirections don't set
> cookies).
> If the application uses another means for session tracking you may
> need to use URL rewriting or a Regex Extractor to keep track of the
> session.
>
> CSV Dataset will ensure each thread gets its own ticket.
>
>> Will I need to include a logout request at the end so
>> that the "user" tracking doesn't get confused?
>
> That depends on your application.
>
> ==
>
> I suggest you experiment with a simple Test Plan using CSV Dataset and
> the Debug Sampler - or the Java Request Sampler can be used to display
> variables.
>
>> Thanks
>>
>> Rob
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Advice on a testing plan
Posted by sebb <se...@gmail.com>.
On 8 December 2010 06:42, Rob Brandt <rb...@csd-bes.net> wrote:
> I am a new jmeter user and am using it to test load capabilities on a
> content management/social networking website.
>
> We are particularly concerned about our user registration scenarios, in
> which new users tend to come in waves. The registration process has
> specific steps; 1) submit a form with user info; 2) fill out a survey; 3)
> update a "project" form, and 4) make a comment on the project. New
> registrants must enter a unique "ticket" number which can only be used once,
> each user is permissioned to only fill out the survey once, can only update
> their own project form, can comment on any project once logged in.
>
> I am working my way through setting up jmeter to fully process 1 user as
> above. Almost done with that. I am aware that there's some import facility
> to load data for the test.
CSV Dataset Config can be used to provide the ticket data.
> I am thinking I will have to load each ticket
> registration as a separate test; so, a few hundred different tests, each
> with one user and not repeated. Am I thinking about this right, on the
> right track?
Why have lots of tests? Why not use a variable for the ticket and vary
the data at run-time?
> I am concerned with how jmeter handles sessions, cookies, etc. Since each
> user has a unique ticket number that can only be used once, then must fill
> out a survey once and only once, update a specific project page, does jmeter
> track this correctly?
JMeter does not do any automatic tracking.
If you provide a Cookie Manager it will handle cookies (don't use
auto-redirect unless you are sure that redirections don't set
cookies).
If the application uses another means for session tracking you may
need to use URL rewriting or a Regex Extractor to keep track of the
session.
CSV Dataset will ensure each thread gets its own ticket.
> Will I need to include a logout request at the end so
> that the "user" tracking doesn't get confused?
That depends on your application.
==
I suggest you experiment with a simple Test Plan using CSV Dataset and
the Debug Sampler - or the Java Request Sampler can be used to display
variables.
> Thanks
>
> Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org