jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Default value for parameters
Date Tue, 24 May 2016 14:46:46 GMT
On 24 May 2016 at 15:37, Antonio Gomes Rodrigues <ra0077@gmail.com> wrote:
> Hi Sebb,
>
> Thanks to your answer
>
> My answer in your mail
>
>
> 2016-05-24 16:24 GMT+02:00 sebb <sebbaz@gmail.com>:
>
>> On 24 May 2016 at 12:18, Antonio Gomes Rodrigues <ra0077@gmail.com> wrote:
>> >  Hi,
>> >
>> >
>> > In this issue : *Bug 59152*
>> > <https://bz.apache.org/bugzilla/show_bug.cgi?id=59152> - Thread Group:
>> > Change "Action to be taken after a Sample Error" value from "Continue" to
>> > "Start Next thread loop"
>> >
>> > I have modified default value in "Thread Group" component.
>> >
>> > Like I have said in the issue, for me the right default value is "Start
>> > Next thread loop" to :
>> >
>> >    - avoid raising too much exception in application and slow it
>> >    - be more realist (for example if a user failed to login and/or failed
>> >    to fill out a form, he will stop the "iteration" and not avoid the
>> error
>> >    and try to execute next action)
>>
>> Surely it would be more sensible to stop the entire thread/test in this
>> case?
>>
> It depends
> If all of you dataset is faulty, yes
> If it's only a small part of your dataset which is faulty, no.

That was my argument here: it's not possible to choose the 'right'
on-error behaviour.

>
>
>
>>
>> > It's why I think the majority of JMeter users use like it (or not because
>> > they don't know this feature)
>> >
>> >
>> > What do you think ?
>> >
>>
>> We already discussed this and decided against it.
>>
>
> Ok
>
> If you think that mainstream test case is to "continue on errors", I have
> nothing to say
>
> I can still use template functionality for my use to avoid extra work to
> modify this value.
>

That's the best idea.

You can even publish your templates if you think they will help others.

>
>>
>> It only makes sense to skip the rest of the samples in a loop if each
>> is dependent on the previous one completing successfully.
>> And only if subsequent loops are independent of previous loops,
>> otherwise it makes more sense to stop the thread or even the entire
>> test.
>>
>> That may be true for some test plans but by no means all.
>>
>> The change would produce unexpected behaviour for existing users.
>>
>> > There another default value I think it needs to be changed.
>>
>> Please use separate e-mails for separate issues.
>>
>> > For example, to "HTTP Cache Manager", I think, "Clear cache each
>> > Iteration?" must be true and not false like actually
>> >
>> > But it's only my opinion and before to check all default value and modify
>> > them I would like to know the process to avoid wasting your and my time
>> >
>> >
>> > Do you have a process?
>>
>> People get used to a particular behaviour, and moving things around or
>> changing defaults causes problems for existing users when creating
>> test plans.
>>
>
>> Imagine how you would feel if the default were changed to Stop Test.
>> (as noted above, it's a reasonable choice)
>>
>> So defaults should only be changed if there is a pressing need to do so.
>>
>> If you think there is a compelling case for changing the behaviour of
>> JMeter, it should be discussed on this list.
>>
>
> No problem, what I would like to know is if there is a process and you
> answer me
>
>
> Before modify a default value, I will ask it before in this list.
>
>>
>> But UI compatibility is very important, especially for defaults where
>> the user is not forced to choose.
>>
>> But even where choices have to be made, consistency is important.
>> Imagine how awkward it would be if the Yes No Cancel buttons were
>> presented in a different order.
>>
>> >
>> > Thanks,
>> >
>> > Antonio
>>

Mime
View raw message