Configurable results file proposal

[kc...@360commerce.com]

I propose having a properties file to let the user choose which data he'd like
to save.  Initially, there will be a single project-wide file, although at some
later time, we may choose to have a finer-grained sollution.  This file would be
in org/apache/jmeter/resources/saveservice.properties.

The contents of the properties file would look something like:

   # legitimate values: xml, csv, db.  Only xml is currently supported.
   jmeter.save.saveservice.output_format=xml

   # true when field should be saved; false otherwise

   jmeter.save.saveservice.data_type=true
   jmeter.save.saveservice.label=true
   jmeter.save.saveservice.response_code=true
   jmeter.save.saveservice.response_message=true
   jmeter.save.saveservice.successful=true
   jmeter.save.saveservice.thread_name=true
   jmeter.save.saveservice.time=true

   # legitimate values: none, ms, or a format suitable for DateFormat
   jmeter.save.saveservice.time_stamp=ms

   # legitimate values: none, first, all
   jmeter.save.saveservice.assertion_results=none

The default properties file would be consistent with how results are curently
saved.  Initially, there will be no corresponding UI; however, some time in the
near future, we should probably create an editor accessible from the UI.

Any suggestions are welcome.  I hope to implement something like this relatively
soon.

Thanks,
Keith



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Configurable results file proposal

[Jordi Salvat i Alabart <js...@atg.com>]

How about separating the Viewer functionality form the Logger 
functionality (in different components, I mean) and having all these 
config parameters in the GUI?

Salut,

Jordi.


kcassell@360commerce.com wrote:
> 
> I propose having a properties file to let the user choose which data he'd like
> to save.  Initially, there will be a single project-wide file, although at some
> later time, we may choose to have a finer-grained sollution.  This file would be
> in org/apache/jmeter/resources/saveservice.properties.
> 
> The contents of the properties file would look something like:
> 
>    # legitimate values: xml, csv, db.  Only xml is currently supported.
>    jmeter.save.saveservice.output_format=xml
> 
>    # true when field should be saved; false otherwise
> 
>    jmeter.save.saveservice.data_type=true
>    jmeter.save.saveservice.label=true
>    jmeter.save.saveservice.response_code=true
>    jmeter.save.saveservice.response_message=true
>    jmeter.save.saveservice.successful=true
>    jmeter.save.saveservice.thread_name=true
>    jmeter.save.saveservice.time=true
> 
>    # legitimate values: none, ms, or a format suitable for DateFormat
>    jmeter.save.saveservice.time_stamp=ms
> 
>    # legitimate values: none, first, all
>    jmeter.save.saveservice.assertion_results=none
> 
> The default properties file would be consistent with how results are curently
> saved.  Initially, there will be no corresponding UI; however, some time in the
> near future, we should probably create an editor accessible from the UI.
> 
> Any suggestions are welcome.  I hope to implement something like this relatively
> soon.
> 
> Thanks,
> Keith
> 
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 
> 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Configurable results file proposal

[Mike Stover <ms...@apache.org>]

I've liked this idea all along, and I think you suggest a practical way to move in that direction.  I 
know Michal is working on some of these things as well, so we should probably get his input.  
It would also be nice if Michal could check in some of the stuff he's been working on - it's 
been too long in isolation, I think.  Others might have valuable input into what you are doing, 
can help, etc.

Response Data seems to be missing from your list, however.  That is the big chunk too.

-Mike

On 27 Jan 2003 at 11:11, kcassell@360commerce.com wrote:

> 
> 
> I propose having a properties file to let the user choose which data he'd like
> to save.  Initially, there will be a single project-wide file, although at some
> later time, we may choose to have a finer-grained sollution.  This file would be
> in org/apache/jmeter/resources/saveservice.properties.
> 
> The contents of the properties file would look something like:
> 
>    # legitimate values: xml, csv, db.  Only xml is currently supported.
>    jmeter.save.saveservice.output_format=xml
> 
>    # true when field should be saved; false otherwise
> 
>    jmeter.save.saveservice.data_type=true
>    jmeter.save.saveservice.label=true
>    jmeter.save.saveservice.response_code=true
>    jmeter.save.saveservice.response_message=true
>    jmeter.save.saveservice.successful=true
>    jmeter.save.saveservice.thread_name=true
>    jmeter.save.saveservice.time=true
> 
>    # legitimate values: none, ms, or a format suitable for DateFormat
>    jmeter.save.saveservice.time_stamp=ms
> 
>    # legitimate values: none, first, all
>    jmeter.save.saveservice.assertion_results=none
> 
> The default properties file would be consistent with how results are curently
> saved.  Initially, there will be no corresponding UI; however, some time in the
> near future, we should probably create an editor accessible from the UI.
> 
> Any suggestions are welcome.  I hope to implement something like this relatively
> soon.
> 
> Thanks,
> Keith
> 
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 



--
Michael Stover
mstover1@apache.org
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>