Hi!
In fact it is nice to be able to test the application that is "behind"
the inputfield. But on the other hand a user can not enter values in the
input field that exceed the maximum length. Even using "copy & paste"
does not work (at least with firefox / IE) and "maxlength" is also part
of the W3C specification.
Perhaps an optional parameter "useMaxlength=true|false" (with default
"false") for the setInputfield step would be nice. But certainly there a
more important things to be done and if really necessary a workaround
with storeXPath (to get the value of "maxlength") should be possible.
Daniel
Marc Guillemot schrieb:
Hi Daniel,
I don't think that the maxlength value is intentionally ignored but
rather than nobody thought to it.
I don't know what to think about it: on the one hand you're right,
browser don't allow (without ruse) to set longer strings but on the
other hand it is handy to test how the application reacts when the
client side "protection" has be ignored...
Marc.
Daniel Brenner wrote:
Hi!
First the scenario:
I have a page containig an inputfield. The test should set the
inputfield with different values and then submits the value and checks
wether the value was succesful stored. The inputfield "contains" the
maxlenght attribute which limits the length of the input to a certain
value. In a browser (i.e. Firefox / IE) the input is limited to a String
with length <= maxlength.
Now the problem:
webtest allows to set the inputfield withs strings with length >
maxlength without making the setinputfield fail. Is the setinputfield
intended to work this way?
Best regards,
Daniel
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
