You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Marcelo Jara <ma...@hotmail.com> on 2013/04/18 18:12:15 UTC
Adding abandonment rate to my test plan help
I have a test plan that includes a thread group with multiple http samplers in it. The flow is a user making a purchase on a web site. So it includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
To be more realistic, I want to add abandonment rates. So I want to add something that would stop the iteration at either steps 1, 2, or 3. And this should be weighted so more people would abandon at step 3 vs step 1.
What's the best way to do this? Do I add an IF statement before each step and then based on a percentage, either perform the action or not?
Thanks,
Marcelo
Re: Adding abandonment rate to my test plan help
Posted by Deepak Shetty <sh...@gmail.com>.
http://jmeter.apache.org/usermanual/component_reference.html#Throughput_Controller
On Thu, Apr 18, 2013 at 9:12 AM, Marcelo Jara <ma...@hotmail.com>wrote:
> I have a test plan that includes a thread group with multiple http
> samplers in it. The flow is a user making a purchase on a web site. So it
> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> To be more realistic, I want to add abandonment rates. So I want to add
> something that would stop the iteration at either steps 1, 2, or 3. And
> this should be weighted so more people would abandon at step 3 vs step 1.
> What's the best way to do this? Do I add an IF statement before each step
> and then based on a percentage, either perform the action or not?
>
> Thanks,
> Marcelo
RE: Adding abandonment rate to my test plan help
Posted by Marcelo Jara <ma...@hotmail.com>.
Yes. That's correct. We have an idea of abandonment rate based on production web logs and tracking sessions. Another big reason people abandon in our case is price. The total price (including tax and shipping) is seen at different stages of the checkout process.
> Subject: Re: Adding abandonment rate to my test plan help
> From: kirk.pepperdine@gmail.com
> Date: Fri, 19 Apr 2013 10:22:26 +0200
> To: user@jmeter.apache.org
>
> sure both cases are true...
>
> On 2013-04-19, at 10:17 AM, Adrian Speteanu <as...@gmail.com> wrote:
>
> > People often reach pages, by following links, miss-clicking, trying to find
> > various resources, that don't relate to their needs. That also adds to
> > abandonment. That brings me back to Deepak's response. You need to know
> > their percentage and use that.
> >
> > Adrian S.
> >
> >
> > On Fri, Apr 19, 2013 at 7:52 AM, Kirk Pepperdine
> > <ki...@gmail.com>wrote:
> >
> >> More often abandonment is related to response time. Getting to the
> >> response time of the previous request would allow you to compare that to
> >> abandonment distribution.
> >>
> >> Regards,
> >> Kirk
> >>
> >> On 2013-04-18, at 10:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
> >>
> >>> Before attempting complicated solutions , does throughput controller not
> >>> work for you?
> >>> +Sampler1
> >>> +ThroughPutController (90 , percent executions , uncheck per user = 10%
> >>> abandon)
> >>> ++Sampler2
> >>> ++ThroughPutController (80 , percent executions , uncheck per user = 20%
> >>> more abandon at this step)
> >>> +++Sampler3
> >>> and so on
> >>>
> >>> regards
> >>> deepak
> >>>
> >>>
> >>> On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <marcelojara@hotmail.com
> >>> wrote:
> >>>
> >>>> Hmm. I can try that.
> >>>> Is there a way to stop the iteration in a beanshell post processor? I'm
> >>>> thinking of doing the following:
> >>>> 1) Have percentages set as user defined variables a)
> >> AbandonAfterSearch
> >>>> = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout =
> >> 20%
> >>>> These don't have to add up to 100% and are mutually exclusive.
> >>>> 2) Add a beanshell post processor in each sampler. In it, generate a
> >>>> random number and compare it to the Abandon rate from step 1. If it's
> >>>> lower, then continue execution. Otherwise, stop the iteration.
> >>>>
> >>>> I read an old thread (
> >>>>
> >> http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html
> >> )
> >>>> which says something like this may not work.
> >>>> Is this still the case?
> >>>>> From: aadrahtas@bluestoneinternational.com
> >>>>> To: user@jmeter.apache.org
> >>>>> Subject: RE: Adding abandonment rate to my test plan help
> >>>>> Date: Thu, 18 Apr 2013 16:44:38 +0000
> >>>>>
> >>>>> One way you can do this is create a switch controller with 4 children
> >> as
> >>>> simple controllers. The first child (the first simple controller under
> >> the
> >>>> switch controller) contains all four steps of your test 1) Searching, 2)
> >>>> Adding to Cart, 3)Checking out 4) Purchase. The second child only
> >> contains
> >>>> steps 1) to 2). The third child contains steps 1) to 3). The fourth
> >> child
> >>>> contains only step 1). For the switch controller, set the switch value
> >> to a
> >>>> variable read from a CSV file. Have 100 entries on the file with numbers
> >>>> 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
> >>>> have jmeter recycle at EOF. This way you will have the exact percentage
> >> of
> >>>> users you need to abandon on each step. For instance, a 0 would mean the
> >>>> user completes all 4 steps, a 1 would mean the user abandons before
> >>>> Checking out, etc.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Andreas Adrahtas - Analyst
> >>>>> Blue Stone International, LLC
> >>>>>
> >>>>> Mobile: +646-266-0238
> >>>>> www.bluestoneinternational.com
> >>>>>
> >>>>> E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
> >>>> and any accompanying documents may contain information that is
> >> confidential
> >>>> or otherwise protected from disclosure. If you are not the intended
> >>>> recipient of this message, or if this message has been addressed to you
> >> in
> >>>> error, please immediately alert the sender by reply e-mail and delete
> >> this
> >>>> message, including any attachment. Any dissemination, distribution or
> >> other
> >>>> use of the contents of this message by anyone other than the intended
> >>>> recipient is strictly prohibited
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Marcelo Jara [mailto:marcelojara@hotmail.com]
> >>>>> Sent: Thursday, April 18, 2013 12:12 PM
> >>>>> To: user@jmeter.apache.org
> >>>>> Subject: Adding abandonment rate to my test plan help
> >>>>>
> >>>>> I have a test plan that includes a thread group with multiple http
> >>>> samplers in it. The flow is a user making a purchase on a web site. So
> >> it
> >>>> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> >>>>> To be more realistic, I want to add abandonment rates. So I want to add
> >>>> something that would stop the iteration at either steps 1, 2, or 3. And
> >>>> this should be weighted so more people would abandon at step 3 vs step
> >> 1.
> >>>>> What's the best way to do this? Do I add an IF statement before each
> >>>> step and then based on a percentage, either perform the action or not?
> >>>>>
> >>>>> Thanks,
> >>>>> Marcelo
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> >>>>> For additional commands, e-mail: user-help@jmeter.apache.org
> >>>>>
> >>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> >> For additional commands, e-mail: user-help@jmeter.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
Re: Adding abandonment rate to my test plan help
Posted by Kirk Pepperdine <ki...@gmail.com>.
sure both cases are true...
On 2013-04-19, at 10:17 AM, Adrian Speteanu <as...@gmail.com> wrote:
> People often reach pages, by following links, miss-clicking, trying to find
> various resources, that don't relate to their needs. That also adds to
> abandonment. That brings me back to Deepak's response. You need to know
> their percentage and use that.
>
> Adrian S.
>
>
> On Fri, Apr 19, 2013 at 7:52 AM, Kirk Pepperdine
> <ki...@gmail.com>wrote:
>
>> More often abandonment is related to response time. Getting to the
>> response time of the previous request would allow you to compare that to
>> abandonment distribution.
>>
>> Regards,
>> Kirk
>>
>> On 2013-04-18, at 10:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
>>
>>> Before attempting complicated solutions , does throughput controller not
>>> work for you?
>>> +Sampler1
>>> +ThroughPutController (90 , percent executions , uncheck per user = 10%
>>> abandon)
>>> ++Sampler2
>>> ++ThroughPutController (80 , percent executions , uncheck per user = 20%
>>> more abandon at this step)
>>> +++Sampler3
>>> and so on
>>>
>>> regards
>>> deepak
>>>
>>>
>>> On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <marcelojara@hotmail.com
>>> wrote:
>>>
>>>> Hmm. I can try that.
>>>> Is there a way to stop the iteration in a beanshell post processor? I'm
>>>> thinking of doing the following:
>>>> 1) Have percentages set as user defined variables a)
>> AbandonAfterSearch
>>>> = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout =
>> 20%
>>>> These don't have to add up to 100% and are mutually exclusive.
>>>> 2) Add a beanshell post processor in each sampler. In it, generate a
>>>> random number and compare it to the Abandon rate from step 1. If it's
>>>> lower, then continue execution. Otherwise, stop the iteration.
>>>>
>>>> I read an old thread (
>>>>
>> http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html
>> )
>>>> which says something like this may not work.
>>>> Is this still the case?
>>>>> From: aadrahtas@bluestoneinternational.com
>>>>> To: user@jmeter.apache.org
>>>>> Subject: RE: Adding abandonment rate to my test plan help
>>>>> Date: Thu, 18 Apr 2013 16:44:38 +0000
>>>>>
>>>>> One way you can do this is create a switch controller with 4 children
>> as
>>>> simple controllers. The first child (the first simple controller under
>> the
>>>> switch controller) contains all four steps of your test 1) Searching, 2)
>>>> Adding to Cart, 3)Checking out 4) Purchase. The second child only
>> contains
>>>> steps 1) to 2). The third child contains steps 1) to 3). The fourth
>> child
>>>> contains only step 1). For the switch controller, set the switch value
>> to a
>>>> variable read from a CSV file. Have 100 entries on the file with numbers
>>>> 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
>>>> have jmeter recycle at EOF. This way you will have the exact percentage
>> of
>>>> users you need to abandon on each step. For instance, a 0 would mean the
>>>> user completes all 4 steps, a 1 would mean the user abandons before
>>>> Checking out, etc.
>>>>>
>>>>>
>>>>>
>>>>> Andreas Adrahtas - Analyst
>>>>> Blue Stone International, LLC
>>>>>
>>>>> Mobile: +646-266-0238
>>>>> www.bluestoneinternational.com
>>>>>
>>>>> E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
>>>> and any accompanying documents may contain information that is
>> confidential
>>>> or otherwise protected from disclosure. If you are not the intended
>>>> recipient of this message, or if this message has been addressed to you
>> in
>>>> error, please immediately alert the sender by reply e-mail and delete
>> this
>>>> message, including any attachment. Any dissemination, distribution or
>> other
>>>> use of the contents of this message by anyone other than the intended
>>>> recipient is strictly prohibited
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Marcelo Jara [mailto:marcelojara@hotmail.com]
>>>>> Sent: Thursday, April 18, 2013 12:12 PM
>>>>> To: user@jmeter.apache.org
>>>>> Subject: Adding abandonment rate to my test plan help
>>>>>
>>>>> I have a test plan that includes a thread group with multiple http
>>>> samplers in it. The flow is a user making a purchase on a web site. So
>> it
>>>> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
>>>>> To be more realistic, I want to add abandonment rates. So I want to add
>>>> something that would stop the iteration at either steps 1, 2, or 3. And
>>>> this should be weighted so more people would abandon at step 3 vs step
>> 1.
>>>>> What's the best way to do this? Do I add an IF statement before each
>>>> step and then based on a percentage, either perform the action or not?
>>>>>
>>>>> Thanks,
>>>>> Marcelo
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>>>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>>>
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Adding abandonment rate to my test plan help
Posted by Adrian Speteanu <as...@gmail.com>.
People often reach pages, by following links, miss-clicking, trying to find
various resources, that don't relate to their needs. That also adds to
abandonment. That brings me back to Deepak's response. You need to know
their percentage and use that.
Adrian S.
On Fri, Apr 19, 2013 at 7:52 AM, Kirk Pepperdine
<ki...@gmail.com>wrote:
> More often abandonment is related to response time. Getting to the
> response time of the previous request would allow you to compare that to
> abandonment distribution.
>
> Regards,
> Kirk
>
> On 2013-04-18, at 10:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
>
> > Before attempting complicated solutions , does throughput controller not
> > work for you?
> > +Sampler1
> > +ThroughPutController (90 , percent executions , uncheck per user = 10%
> > abandon)
> > ++Sampler2
> > ++ThroughPutController (80 , percent executions , uncheck per user = 20%
> > more abandon at this step)
> > +++Sampler3
> > and so on
> >
> > regards
> > deepak
> >
> >
> > On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <marcelojara@hotmail.com
> >wrote:
> >
> >> Hmm. I can try that.
> >> Is there a way to stop the iteration in a beanshell post processor? I'm
> >> thinking of doing the following:
> >> 1) Have percentages set as user defined variables a)
> AbandonAfterSearch
> >> = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout =
> 20%
> >> These don't have to add up to 100% and are mutually exclusive.
> >> 2) Add a beanshell post processor in each sampler. In it, generate a
> >> random number and compare it to the Abandon rate from step 1. If it's
> >> lower, then continue execution. Otherwise, stop the iteration.
> >>
> >> I read an old thread (
> >>
> http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html
> )
> >> which says something like this may not work.
> >> Is this still the case?
> >>> From: aadrahtas@bluestoneinternational.com
> >>> To: user@jmeter.apache.org
> >>> Subject: RE: Adding abandonment rate to my test plan help
> >>> Date: Thu, 18 Apr 2013 16:44:38 +0000
> >>>
> >>> One way you can do this is create a switch controller with 4 children
> as
> >> simple controllers. The first child (the first simple controller under
> the
> >> switch controller) contains all four steps of your test 1) Searching, 2)
> >> Adding to Cart, 3)Checking out 4) Purchase. The second child only
> contains
> >> steps 1) to 2). The third child contains steps 1) to 3). The fourth
> child
> >> contains only step 1). For the switch controller, set the switch value
> to a
> >> variable read from a CSV file. Have 100 entries on the file with numbers
> >> 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
> >> have jmeter recycle at EOF. This way you will have the exact percentage
> of
> >> users you need to abandon on each step. For instance, a 0 would mean the
> >> user completes all 4 steps, a 1 would mean the user abandons before
> >> Checking out, etc.
> >>>
> >>>
> >>>
> >>> Andreas Adrahtas - Analyst
> >>> Blue Stone International, LLC
> >>>
> >>> Mobile: +646-266-0238
> >>> www.bluestoneinternational.com
> >>>
> >>> E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
> >> and any accompanying documents may contain information that is
> confidential
> >> or otherwise protected from disclosure. If you are not the intended
> >> recipient of this message, or if this message has been addressed to you
> in
> >> error, please immediately alert the sender by reply e-mail and delete
> this
> >> message, including any attachment. Any dissemination, distribution or
> other
> >> use of the contents of this message by anyone other than the intended
> >> recipient is strictly prohibited
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Marcelo Jara [mailto:marcelojara@hotmail.com]
> >>> Sent: Thursday, April 18, 2013 12:12 PM
> >>> To: user@jmeter.apache.org
> >>> Subject: Adding abandonment rate to my test plan help
> >>>
> >>> I have a test plan that includes a thread group with multiple http
> >> samplers in it. The flow is a user making a purchase on a web site. So
> it
> >> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> >>> To be more realistic, I want to add abandonment rates. So I want to add
> >> something that would stop the iteration at either steps 1, 2, or 3. And
> >> this should be weighted so more people would abandon at step 3 vs step
> 1.
> >>> What's the best way to do this? Do I add an IF statement before each
> >> step and then based on a percentage, either perform the action or not?
> >>>
> >>> Thanks,
> >>> Marcelo
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> >>> For additional commands, e-mail: user-help@jmeter.apache.org
> >>>
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: Adding abandonment rate to my test plan help
Posted by Kirk Pepperdine <ki...@gmail.com>.
More often abandonment is related to response time. Getting to the response time of the previous request would allow you to compare that to abandonment distribution.
Regards,
Kirk
On 2013-04-18, at 10:09 PM, Deepak Shetty <sh...@gmail.com> wrote:
> Before attempting complicated solutions , does throughput controller not
> work for you?
> +Sampler1
> +ThroughPutController (90 , percent executions , uncheck per user = 10%
> abandon)
> ++Sampler2
> ++ThroughPutController (80 , percent executions , uncheck per user = 20%
> more abandon at this step)
> +++Sampler3
> and so on
>
> regards
> deepak
>
>
> On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <ma...@hotmail.com>wrote:
>
>> Hmm. I can try that.
>> Is there a way to stop the iteration in a beanshell post processor? I'm
>> thinking of doing the following:
>> 1) Have percentages set as user defined variables a) AbandonAfterSearch
>> = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout = 20%
>> These don't have to add up to 100% and are mutually exclusive.
>> 2) Add a beanshell post processor in each sampler. In it, generate a
>> random number and compare it to the Abandon rate from step 1. If it's
>> lower, then continue execution. Otherwise, stop the iteration.
>>
>> I read an old thread (
>> http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html)
>> which says something like this may not work.
>> Is this still the case?
>>> From: aadrahtas@bluestoneinternational.com
>>> To: user@jmeter.apache.org
>>> Subject: RE: Adding abandonment rate to my test plan help
>>> Date: Thu, 18 Apr 2013 16:44:38 +0000
>>>
>>> One way you can do this is create a switch controller with 4 children as
>> simple controllers. The first child (the first simple controller under the
>> switch controller) contains all four steps of your test 1) Searching, 2)
>> Adding to Cart, 3)Checking out 4) Purchase. The second child only contains
>> steps 1) to 2). The third child contains steps 1) to 3). The fourth child
>> contains only step 1). For the switch controller, set the switch value to a
>> variable read from a CSV file. Have 100 entries on the file with numbers
>> 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
>> have jmeter recycle at EOF. This way you will have the exact percentage of
>> users you need to abandon on each step. For instance, a 0 would mean the
>> user completes all 4 steps, a 1 would mean the user abandons before
>> Checking out, etc.
>>>
>>>
>>>
>>> Andreas Adrahtas - Analyst
>>> Blue Stone International, LLC
>>>
>>> Mobile: +646-266-0238
>>> www.bluestoneinternational.com
>>>
>>> E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
>> and any accompanying documents may contain information that is confidential
>> or otherwise protected from disclosure. If you are not the intended
>> recipient of this message, or if this message has been addressed to you in
>> error, please immediately alert the sender by reply e-mail and delete this
>> message, including any attachment. Any dissemination, distribution or other
>> use of the contents of this message by anyone other than the intended
>> recipient is strictly prohibited
>>>
>>>
>>> -----Original Message-----
>>> From: Marcelo Jara [mailto:marcelojara@hotmail.com]
>>> Sent: Thursday, April 18, 2013 12:12 PM
>>> To: user@jmeter.apache.org
>>> Subject: Adding abandonment rate to my test plan help
>>>
>>> I have a test plan that includes a thread group with multiple http
>> samplers in it. The flow is a user making a purchase on a web site. So it
>> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
>>> To be more realistic, I want to add abandonment rates. So I want to add
>> something that would stop the iteration at either steps 1, 2, or 3. And
>> this should be weighted so more people would abandon at step 3 vs step 1.
>>> What's the best way to do this? Do I add an IF statement before each
>> step and then based on a percentage, either perform the action or not?
>>>
>>> Thanks,
>>> Marcelo
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
RE: Adding abandonment rate to my test plan help
Posted by Marcelo Jara <ma...@hotmail.com>.
Thanks for the example! Yes, this seems to be the easiest solution.
> Date: Thu, 18 Apr 2013 13:09:08 -0700
> Subject: Re: Adding abandonment rate to my test plan help
> From: shettyd@gmail.com
> To: user@jmeter.apache.org
>
> Before attempting complicated solutions , does throughput controller not
> work for you?
> +Sampler1
> +ThroughPutController (90 , percent executions , uncheck per user = 10%
> abandon)
> ++Sampler2
> ++ThroughPutController (80 , percent executions , uncheck per user = 20%
> more abandon at this step)
> +++Sampler3
> and so on
>
> regards
> deepak
>
>
> On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <ma...@hotmail.com>wrote:
>
> > Hmm. I can try that.
> > Is there a way to stop the iteration in a beanshell post processor? I'm
> > thinking of doing the following:
> > 1) Have percentages set as user defined variables a) AbandonAfterSearch
> > = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout = 20%
> > These don't have to add up to 100% and are mutually exclusive.
> > 2) Add a beanshell post processor in each sampler. In it, generate a
> > random number and compare it to the Abandon rate from step 1. If it's
> > lower, then continue execution. Otherwise, stop the iteration.
> >
> > I read an old thread (
> > http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html)
> > which says something like this may not work.
> > Is this still the case?
> > > From: aadrahtas@bluestoneinternational.com
> > > To: user@jmeter.apache.org
> > > Subject: RE: Adding abandonment rate to my test plan help
> > > Date: Thu, 18 Apr 2013 16:44:38 +0000
> > >
> > > One way you can do this is create a switch controller with 4 children as
> > simple controllers. The first child (the first simple controller under the
> > switch controller) contains all four steps of your test 1) Searching, 2)
> > Adding to Cart, 3)Checking out 4) Purchase. The second child only contains
> > steps 1) to 2). The third child contains steps 1) to 3). The fourth child
> > contains only step 1). For the switch controller, set the switch value to a
> > variable read from a CSV file. Have 100 entries on the file with numbers
> > 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
> > have jmeter recycle at EOF. This way you will have the exact percentage of
> > users you need to abandon on each step. For instance, a 0 would mean the
> > user completes all 4 steps, a 1 would mean the user abandons before
> > Checking out, etc.
> > >
> > >
> > >
> > > Andreas Adrahtas - Analyst
> > > Blue Stone International, LLC
> > >
> > > Mobile: +646-266-0238
> > > www.bluestoneinternational.com
> > >
> > > E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
> > and any accompanying documents may contain information that is confidential
> > or otherwise protected from disclosure. If you are not the intended
> > recipient of this message, or if this message has been addressed to you in
> > error, please immediately alert the sender by reply e-mail and delete this
> > message, including any attachment. Any dissemination, distribution or other
> > use of the contents of this message by anyone other than the intended
> > recipient is strictly prohibited
> > >
> > >
> > > -----Original Message-----
> > > From: Marcelo Jara [mailto:marcelojara@hotmail.com]
> > > Sent: Thursday, April 18, 2013 12:12 PM
> > > To: user@jmeter.apache.org
> > > Subject: Adding abandonment rate to my test plan help
> > >
> > > I have a test plan that includes a thread group with multiple http
> > samplers in it. The flow is a user making a purchase on a web site. So it
> > includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> > > To be more realistic, I want to add abandonment rates. So I want to add
> > something that would stop the iteration at either steps 1, 2, or 3. And
> > this should be weighted so more people would abandon at step 3 vs step 1.
> > > What's the best way to do this? Do I add an IF statement before each
> > step and then based on a percentage, either perform the action or not?
> > >
> > > Thanks,
> > > Marcelo
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > For additional commands, e-mail: user-help@jmeter.apache.org
> > >
> >
> >
Re: Adding abandonment rate to my test plan help
Posted by Deepak Shetty <sh...@gmail.com>.
Before attempting complicated solutions , does throughput controller not
work for you?
+Sampler1
+ThroughPutController (90 , percent executions , uncheck per user = 10%
abandon)
++Sampler2
++ThroughPutController (80 , percent executions , uncheck per user = 20%
more abandon at this step)
+++Sampler3
and so on
regards
deepak
On Thu, Apr 18, 2013 at 12:55 PM, Marcelo Jara <ma...@hotmail.com>wrote:
> Hmm. I can try that.
> Is there a way to stop the iteration in a beanshell post processor? I'm
> thinking of doing the following:
> 1) Have percentages set as user defined variables a) AbandonAfterSearch
> = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout = 20%
> These don't have to add up to 100% and are mutually exclusive.
> 2) Add a beanshell post processor in each sampler. In it, generate a
> random number and compare it to the Abandon rate from step 1. If it's
> lower, then continue execution. Otherwise, stop the iteration.
>
> I read an old thread (
> http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html)
> which says something like this may not work.
> Is this still the case?
> > From: aadrahtas@bluestoneinternational.com
> > To: user@jmeter.apache.org
> > Subject: RE: Adding abandonment rate to my test plan help
> > Date: Thu, 18 Apr 2013 16:44:38 +0000
> >
> > One way you can do this is create a switch controller with 4 children as
> simple controllers. The first child (the first simple controller under the
> switch controller) contains all four steps of your test 1) Searching, 2)
> Adding to Cart, 3)Checking out 4) Purchase. The second child only contains
> steps 1) to 2). The third child contains steps 1) to 3). The fourth child
> contains only step 1). For the switch controller, set the switch value to a
> variable read from a CSV file. Have 100 entries on the file with numbers
> 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and
> have jmeter recycle at EOF. This way you will have the exact percentage of
> users you need to abandon on each step. For instance, a 0 would mean the
> user completes all 4 steps, a 1 would mean the user abandons before
> Checking out, etc.
> >
> >
> >
> > Andreas Adrahtas - Analyst
> > Blue Stone International, LLC
> >
> > Mobile: +646-266-0238
> > www.bluestoneinternational.com
> >
> > E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail
> and any accompanying documents may contain information that is confidential
> or otherwise protected from disclosure. If you are not the intended
> recipient of this message, or if this message has been addressed to you in
> error, please immediately alert the sender by reply e-mail and delete this
> message, including any attachment. Any dissemination, distribution or other
> use of the contents of this message by anyone other than the intended
> recipient is strictly prohibited
> >
> >
> > -----Original Message-----
> > From: Marcelo Jara [mailto:marcelojara@hotmail.com]
> > Sent: Thursday, April 18, 2013 12:12 PM
> > To: user@jmeter.apache.org
> > Subject: Adding abandonment rate to my test plan help
> >
> > I have a test plan that includes a thread group with multiple http
> samplers in it. The flow is a user making a purchase on a web site. So it
> includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> > To be more realistic, I want to add abandonment rates. So I want to add
> something that would stop the iteration at either steps 1, 2, or 3. And
> this should be weighted so more people would abandon at step 3 vs step 1.
> > What's the best way to do this? Do I add an IF statement before each
> step and then based on a percentage, either perform the action or not?
> >
> > Thanks,
> > Marcelo
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
>
RE: Adding abandonment rate to my test plan help
Posted by Marcelo Jara <ma...@hotmail.com>.
Hmm. I can try that.
Is there a way to stop the iteration in a beanshell post processor? I'm thinking of doing the following:
1) Have percentages set as user defined variables a) AbandonAfterSearch = 10% b) AbandonAfterAddingToCart = 10% c) AbandonAfterCheckout = 20%
These don't have to add up to 100% and are mutually exclusive.
2) Add a beanshell post processor in each sampler. In it, generate a random number and compare it to the Abandon rate from step 1. If it's lower, then continue execution. Otherwise, stop the iteration.
I read an old thread (http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-td533789.html) which says something like this may not work.
Is this still the case?
> From: aadrahtas@bluestoneinternational.com
> To: user@jmeter.apache.org
> Subject: RE: Adding abandonment rate to my test plan help
> Date: Thu, 18 Apr 2013 16:44:38 +0000
>
> One way you can do this is create a switch controller with 4 children as simple controllers. The first child (the first simple controller under the switch controller) contains all four steps of your test 1) Searching, 2) Adding to Cart, 3)Checking out 4) Purchase. The second child only contains steps 1) to 2). The third child contains steps 1) to 3). The fourth child contains only step 1). For the switch controller, set the switch value to a variable read from a CSV file. Have 100 entries on the file with numbers 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and have jmeter recycle at EOF. This way you will have the exact percentage of users you need to abandon on each step. For instance, a 0 would mean the user completes all 4 steps, a 1 would mean the user abandons before Checking out, etc.
>
>
>
> Andreas Adrahtas - Analyst
> Blue Stone International, LLC
>
> Mobile: +646-266-0238
> www.bluestoneinternational.com
>
> E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and delete this message, including any attachment. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited
>
>
> -----Original Message-----
> From: Marcelo Jara [mailto:marcelojara@hotmail.com]
> Sent: Thursday, April 18, 2013 12:12 PM
> To: user@jmeter.apache.org
> Subject: Adding abandonment rate to my test plan help
>
> I have a test plan that includes a thread group with multiple http samplers in it. The flow is a user making a purchase on a web site. So it includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
> To be more realistic, I want to add abandonment rates. So I want to add something that would stop the iteration at either steps 1, 2, or 3. And this should be weighted so more people would abandon at step 3 vs step 1.
> What's the best way to do this? Do I add an IF statement before each step and then based on a percentage, either perform the action or not?
>
> Thanks,
> Marcelo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
RE: Adding abandonment rate to my test plan help
Posted by Andreas Adrahtas <aa...@bluestoneinternational.com>.
One way you can do this is create a switch controller with 4 children as simple controllers. The first child (the first simple controller under the switch controller) contains all four steps of your test 1) Searching, 2) Adding to Cart, 3)Checking out 4) Purchase. The second child only contains steps 1) to 2). The third child contains steps 1) to 3). The fourth child contains only step 1). For the switch controller, set the switch value to a variable read from a CSV file. Have 100 entries on the file with numbers 0,1,2,3. Choose the proportion of 0,1,2,3's according to your needs and have jmeter recycle at EOF. This way you will have the exact percentage of users you need to abandon on each step. For instance, a 0 would mean the user completes all 4 steps, a 1 would mean the user abandons before Checking out, etc.
Andreas Adrahtas - Analyst
Blue Stone International, LLC
Mobile: +646-266-0238
www.bluestoneinternational.com
E-MAIL CONFIDENTIALITY NOTICE: The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and delete this message, including any attachment. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited
-----Original Message-----
From: Marcelo Jara [mailto:marcelojara@hotmail.com]
Sent: Thursday, April 18, 2013 12:12 PM
To: user@jmeter.apache.org
Subject: Adding abandonment rate to my test plan help
I have a test plan that includes a thread group with multiple http samplers in it. The flow is a user making a purchase on a web site. So it includes 1) Searching, 2) Adding to cart, 3) Checking out, 4) Purchase.
To be more realistic, I want to add abandonment rates. So I want to add something that would stop the iteration at either steps 1, 2, or 3. And this should be weighted so more people would abandon at step 3 vs step 1.
What's the best way to do this? Do I add an IF statement before each step and then based on a percentage, either perform the action or not?
Thanks,
Marcelo
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org