On 5/30/05, Sonam Chauhan <[EMAIL PROTECTED]> wrote:
> > > I added this property to CVS HEAD recently:
> > >
> > > jmeter.save.saveservice.response_data.on_error
> > >
> > > I think that does what you want.
> > >
> > > S.
>
> Seb: I just checked out the 20050528 nightly build. I had some comments and
> questions below (comparing to the venerable JMeter 1.9.1):
>
> 1. In the new build, if I set a logfile with the '-l' parameter, it is
> only created if the test runs in non-GUI mode (i.e. with the '-n' parameter
> as well). The same behavior exists in 1.9 too. Is this by design?
I don't know for sure. The -l parameter is certainly intended for use
with non-GUI runs, but it may make sense to allow it for GUI runs too.
It's not essential, as one can always add a simple data writer to the
GUI...
> 2. Is there a DTD or schema for the XML log format? (The attribute
> names are a lot more brief compared to 1.9.)
No DTD that I know of.
But you can revert to the previous format using one or more of the
file_format properties - see jmeter.properties.
> 3. Ticking 'Functional mode' in the test plan no longer saves response
> data in the JMeter log. To do that, I had to explicitly set the property you
> mentioned:
> -Jjmeter.save.saveservice.response_data.on_error=true
Oh. That is supposed to work. Was that a non-GUI run?
Also, this should work:
-Jjmeter.save.saveservice.response_data=true
> 4. The corresponding *request* data is not stored.
> In 1.9, 'functional test mode' stores the request URL (though it would be
> better to store the entire HTTP request data)
>
> Storing request data is especially needed if the request is derived from an
> earlier response. It would be good to have a property like:
> jmeter.save.saveservice.request_data.on_error
Seems a good idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
