15 messages in com.canoo.lists.webtestRE: [Webtest] Problem to submit form ...
FromSent OnAttachments
Xavier MOGHRABI12 Oct 2004 01:02 
dier...@mail.canoo.com12 Oct 2004 04:55 
Xavier MOGHRABI12 Oct 2004 09:44 
Xavier MOGHRABI13 Oct 2004 09:48 
Dierk Koenig14 Oct 2004 00:45 
Xavier MOGHRABI14 Oct 2004 06:57 
Dierk Koenig15 Oct 2004 01:01 
Xavier MOGHRABI15 Oct 2004 01:13 
Dierk Koenig15 Oct 2004 07:52 
Xavier MOGHRABI18 Oct 2004 00:50 
Dierk Koenig18 Oct 2004 01:58 
Xavier MOGHRABI18 Oct 2004 02:48 
Dierk Koenig18 Oct 2004 04:35 
Xavier MOGHRABI18 Oct 2004 06:06 
Dierk Koenig18 Oct 2004 06:26 
Subject:RE: [Webtest] Problem to submit form with <BUTTON>
From:Dierk Koenig (dier@canoo.com)
Date:10/18/2004 01:58:07 AM
List:com.canoo.lists.webtest

Hi Xavier,

1. The Button element can have the attributes name and value. The value attribute is sent to the server when submitted. So we should add an other for relating to the content between the button tags. That content is displayed. I've chosen the name text for relating to the content because HTTPUNIT 1.6 relates to it with text too.

I understand. I was more concerned with getting "what the user sees" close to "what the webtest looks like". If text is given, it appears as the button label. If text is not given but value, the value appears as label. If neither is given, some default appears depending on type. I'm not so much concerned with what actually gets submitted as this makes no difference to the user (neither to webtest). Also the appropriate mapping to the httpunit methods can all be done behind the scenes.

I agree that the above makes the mapping of html attributes to httpunit method calls less obvious.

There also is the issue of locating the proper button. Here the availability of both "text" and "value" would allow one more information for distinction.

For my personal taste the pro "ease of use" would weigh out the cons "ease of mapping" and "one more locating option". What is your rating?

cheers Mittie