[Webtest] Name of step: emulateSetHiddenInputField
Sat, 20 May 2006 09:55:49 +1000
Dierk Koenig wrote:
> maybe a 'force' attribute?
That would make sense if every test step we are thinking of
had both direct user and indirect forced modes of operation.
I don't think there would ever be a direct user mode for:
In both these cases the direct user mode is something else
trying to bypass. I think it is worth making it obvious that
we are reaching behind the normal browser user interface and
tweaking state information inside our browser emulator.
>> -----Original Message-----
>> From: email@example.com
>> [mailto:firstname.lastname@example.org]On Behalf Of Paul King
>> Sent: Freitag, 19. Mai 2006 14:47
>> To: email@example.com
>> Subject: Re: [Webtest] Name of step: emulateSetHiddenInputField
>> Dierk Koenig wrote:
>>> yes, but isn't that already covered by the word 'hidden'?
>> Possibly in this case it might be enough but then what to name:
>> forceClickButton if we wanted to allow users to click a disabled button
>> forceSetField if we wanted to allow the user to change a read-only field
>>>> Except that all other setXXX, clickXXX steps correspond to the user
>>>> clicking on a link, button, checkbox, or typing in some text, etc.
>>>> There is NOTHING that the user could ever do to force changing
>>>> the hidden field directly. Nothing to click, type, no menu option etc.
>>> They can only do it indirectly when they eventually tricker some whacky
>>> I see your point, though.
>>> Hm, don't know. I'm too tired and need to go to the next session.
>>> WebTest mailing list
>> WebTest mailing list
> WebTest mailing list