Hi Willi, do you mean that WebTest shouldn't care of this but HtmlUnit should do?
In fact it makes sense to have the possibility to set values will length > maxlength: because you can simply remove the maxlength check in a normal browser it makes sense to be able to test how your webapp reacts when maxlength isn't respected. This may be handled in WebTest or in HtmlUnit, it doesn't matter. Cheers, Marc. -- Blog: http://mguillem.wordpress.com Willi Kuhnis wrote: > Hi Marc, > > thanks for your feedback. > you says, maybe it would make sense, when setInputField could > (optionally) respect the maxlength. > > But I still dont understand: > I think, setInputField must not handle this -> the webpage (and in the > webpage the used edit field ) should handle this. > After I entered a string with the length of 41 in a edit field with > maxlength of 40, I am not able to read or see a text in this edit field > with more > than 40 characters. So I dont understand, how Webtest can read a text > with 41 characters out of this edit field. Thats my problem. > > Do you understand? > > > -- > Willi Kuhnis > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
