[Webtest] Re: [webtest][JIRA] Created: (WT-61) Do not create resultpath, if saveresponse is disabled

[Dierk Koenig]

Hi Paul,

> -----Original Message-----
> From: webtest-admin@lists.canoo.com
>..
> When saveresponse is set to true, WebTest writes a file with a default
> name-prefix and a timestamp into the resultpath directory (if =
specified).
> The save parameter (on clickButton, clickLink, followFrame, invoke
> and appletRunnerStep) allows the default name-prefix to be overridden.
>=20
> If saveresponse is set to false, WebTest won't normally write any =
results
> but will do so if save is set.
>=20
> Is this the intended behaviour?=20

Well, yes. 'save' has higher precedence since it is local.
It denotes something that is always saved regardless of general =
settings,
e.g. some critical output.
Tests often have some 'final' result and a lot of 'intermediary'=20
results.

Even if we change the current behaviour, we should support some
'save-anyway' :-) feature.

> Also, clickElement, selectWindow and setSelectField which all=20
> have the ability
> to potentially cause a new lastResponse but have no way to set a=20
> non-default
> name. Perhaps this should change too (plus the saveResponse=20
> parameter if we go
> ahead with that).

I think they should also support save.=20

cheers
Mittie