[Webtest] Problem with new_setcheckbox

Marc Guillemot webtest@lists.canoo.com
Mon, 09 Aug 2004 15:57:53 +0200

Hi Lisa,

the dynamic properties in the value attribute weren't expanded, this is now fixed and shouldwork the way you want. Sorry 
for the disconvenience.

Nevertheless I guess that in your case it would work with just checked="true" and no value specified what is shorter and 
more readable.


Lisa Crispin wrote:
> Oops - I had left the 'checked="true"' off when I left off the value.  With no 'value' and with 'checked', it works.  However, does this mean you can't use 'value' with new_setcheckbox?  I'm still confused, can anyone clear it up for me?
> thanks,
> Lisa
> -------------- Original message from lisa.crispin@att.net (Lisa Crispin): -------------- 
>>I'm trying to use the new_setxxx stuff so I won't be caught short when they are 
>>made the default. Also they seem to work better in general. But I'm having a 
>>problem with the new_setcheckbox. 
>>Here's the WebTest script code; I'm capturing a check number and then trying to 
>>check a setbox with that check number. 
>>>text=".*input name="check([0-9]+)"" 
>>value="#{checkNbr}" /> 
>>Here is the HTML: 
>>Here is the error message I get. It works fine with the old setcheckbox. 
>>I thought maybe I could just leave off the value parm, but when I do that, it 
>>doesn't select the check (it passes, but no check is really selected). 
>>Unexpected exception caught: 
>>com.meterware.httpunit.FormParameter$UnusedParameterValueException: Attempted to 
>>assign to parameter 'check36789' the extraneous value '#{checkNbr}'. 
>>WebTest mailing list 
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest