Choosing "functional testing" causes everything to be dumped into the jtl files. The problem is, it's a huge performance hit.
I thought Michal was working on changing the way results are saved. Maybe I was wrong in that assumption. The whole thing needs to be changed to save the info in a less heavy file format (XML is too slow for this work). And then, yeah, it probably would make sense for there to be a config file that allowed more complete control over what is saved in the JTL's. -Mike On 22 Jan 2003 at 8:24, [EMAIL PROTECTED] wrote: > > > Currently, the test results (JTL) files capture a subset of the information > contained in the SampleResult class. For some of the work I'm doing, it would > be nice to have additional information captured in the JTL files, for instance, > the cause of an assertion failure. > > As far as I can tell, there is no way to configure which of the SampleResult > data gets put into the files. It seems to be something that we should add. > Because I'm not all that familiar with the organization of the code yet, I'm > open to advice about where such results file configuration information should be > put to be consistent within JMeter and with other Apache projects. > > I would hope that giving the option of adding information to the results file > would be no big deal. Is there any compelling reason we shouldn't? > > Thanks for your input, > Keith > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
