Ah - that's a known bug (43584) in the way Response Assertions are reported; the fixed text uses a comma. This has been fixed for the next release.
However there is always the possibiity that another field might contain the delimiter - or indeed the Assertion could be looking for the delimiter, which would then be output if the Assertion did not match. So at some stage the CSV handling needs to be improved to cope with embedded delimiters. In the meantime, the work-round is to use a delimiter that does not appear in any of the fields. On 07/11/2007, tiffany <[EMAIL PROTECTED]> wrote: > > I found that the result file, data are separated with "," prefectly in the > first few lines, but then somehow it starting to add one more field with > data 'text expected to contain /Home/' before the byte count data and that's > caused the problem. After I removed the data 'text expected to contain > /Home/' from those lines, it works prefect. > > ============= > > tiffany wrote: > > > > Hi, > > > > Are the following bugs? > > > > I am using Jmeter - jakarta-jmeter-2.3RC3 version, I configured the > > information saved with the configuration button, I checked everything > > there except "Save as XML" and "Save Encoding". After the run, I saved the > > result and then tried to open the result file(.jtl) again and get the > > following in the Jmeter.log: > > > > 2007/11/02 11:01:27 WARN - jmeter.save.OldSaveService: Error parsing > > field 'bytes' at line 5 java.lang.NumberFormatException: For input string: > > " text expected to contain /Home/" > > > > and then I unchecked the "Save as Byte Count", tried the above steps again > > and then get the following error in the Jmeter.log: > > > > 2007/11/02 11:03:29 WARN - jmeter.save.OldSaveService: Error parsing > > field 'Latency' at line 7 java.lang.NumberFormatException: For input > > string: "" > > > > and then I unchecked the "Save as Latency", tried the above steps again > > and then get the following error in the Jmeter.log: > > > > 2007/11/02 11:05:22 WARN - jmeter.save.OldSaveService: Insufficient > > columns to parse field 'Filename' at line 2 > > > > and then I unchecked the "Save as Response Filename", it works fine this > > time. > > > > Conclusion : The functionalities of saving the result of Byte Count, > > Latency and Response filename are not working. > > > > By the way, even I checked the functional test mode and save the response > > data, Jmeter couldn't save the response data in the result tree. > > > > -- > View this message in context: > http://www.nabble.com/Listener---Save-results-tf4738057.html#a13629652 > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
