[Webtest] Re: WebTest digest

[Stefan Ruff]

Dear Christopher 

We fully agree with you. 

The html code is even worse then you imagine. There is not one 
mulitselectfield with same values; there are a few selectfields with the 
same html name tag! 

We know this a long time ago. But while the application was running fine, 
there was no reason to change it.
Thanks WebTest we have to correct  this nasty code :-). 

Stefan, Joël 

Christopher Painter-Wakefield writes: 

> I don't know if webtest is sorting, or why (it would really be HttpUnit,
> anyway, I imagine).  However, I don't think the HTML standard says anything
> about the order in which parameters are listed in the request from the
> client, and in my experience it is a mistake to expect them to arrive in a
> particular order, at least on large POST forms.  It is better to code your
> form in such a way as to remove any dependency on order. 
> 
> I'm wondering why you have a multiselect field with multiple identical
> values, those are surely indistinguishable when you get the request? 
> 
> -Christopher 
> 
>  
> 
> 
> Message: 7
> From: "Stefan Ruff" <sruff@limmat.ch>
> To: "WebTest" <webtest@lists.canoo.com>
> Date: Tue, 07 Oct 2003 07:28:03 +0200
> Subject: [Webtest] setselectfield with multiselect
> Reply-To: webtest@lists.canoo.com 
> 
> Hi all, 
> 
> We use in our web test the following code snippet: 
> 
>                                                  <setselectfield
>                                                              stepid="Bitte
> auswählen" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="1" 
> 
> multiselect="true"
>                                                  />
>                                                  <setselectfield 
> 
> stepid="Provider akzeptieren" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="99" 
> 
> multiselect="true"
>                                                  />
>                                                  <setselectfield
>                                                              stepid="Bitte
> auswählen" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="0" 
> 
> multiselect="true"
>                                                  />
>                                                  <setselectfield
>                                                              stepid="Bitte
> auswählen" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="0" 
> 
> multiselect="true"
>                                                  />
>                                                  <setselectfield
>                                                              stepid="Bitte
> auswählen" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="0" 
> 
> multiselect="true"
>                                                  />
>                                                  <setselectfield
>                                                              stepid="Bitte
> auswählen" 
> 
> name="providerUebersteuerungsgrund"
>                                                              value="0" 
> 
> multiselect="true"
>                                                  /> 
> 
> When we get the parameter from the request we expected an array of the
> following form: [1,99,0,0,0,0]. 
> 
> WebTest delivers an array in the form of [0,0,0,0,1,99]. 
> 
> We presume WebTest is sorting the list of values. Is there a good reason
> doing this? 
> 
> Our application needs the values in the correct order, as shown in the
> template. 
> 
> Best regards,
> Stefan, Chris & Joël 
> 
>  
> 
> 
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest