Contributions always welcome - please open a Bugzilla enhancement
request with the details, and patches can be added to that (diff -u
format or use Eclipse).
It won't be trivial...
From memory, the classes are:
SaveService
OldSaveService
SaveConfiguration
The Listeners don't actually handle the saving/loading of data; their
only involvement is to define what fields are to be saved via the
config gui, and to provide the file name.
The tricky bits are:
- details need to be provided in jmeter.properties so that the -l flag
works in non-GUI mode
- it should work in CSV and XML mode
- need to ensure that the XML and CSV files can be read back in. This
should be trivial for CSV (just ignore the extra columns). May be
tricky for XML
- should not cause problems for existing XSL stylesheets.
I think the simplest would be to provide a list of variable names as
the value of a property in jmeter.properties.
If this property is defined, then save the value of each variable.
For CSV, the names should be added to the header line
For XML, I think there needs to be a new tag, with the name of the
variable as an attribute. Not sure if there needs to be an enclosing
group tag as well.
It might be easy to create a new Listener with a field to define the
variable names - or perhaps the common Filename panel could be
extended to add a variable name box; in which cases the property would
not be used.
Otherwise, perhaps extend the SaveConfig GUI to add a check-box
whether or not to save the extra fields, and take the field names from
the property.
On 21/08/06, Eric Dalquist <[EMAIL PROTECTED]> wrote:
I'm currently doing the label trick but that then requires extra
processing in my reporting tool. Would you be open to a contribution
that would add the capability to persist variables to the Simple Data
Writer (or some clone of it)? If so do you have any quick pointers on
which classes I would be looking at tweaking?
-Eric
sebb wrote:
> Not directly.
>
> However, you can create a Java Request sampler and include the
> variables in that; attach the SDW as a child of the Java Request
> Sampler.
>
> Or you can add a BeanShell Post-processor or perhaps a Listener, and
> write some code to write the values to a file.
>
> Or you can pass the host name in as a property, rather than via a CSV
> file, and use a command script to save the value outside the test.
>
> It's not currently possible to add any optional variables to either
> the CSV or XML output formats, but you can always try including the
> host-name as part of the sampler labels.
>
> S.
> On 21/08/06, Eric Dalquist <[EMAIL PROTECTED]> wrote:
>> Is there a way to get the Simple Data Writer to save arbitrary variables
>> I have set in my test with each result? As an example I have a test that
>> can run against multiple hosts which is specified by a ${host} variable
>> being read from a CSV. Is there a way with the XML persistence option to
>> save that variable for each result so I can do reporting based on hosts?
>>
>> -Eric
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
