Bug 43584 - Assertion Failure Message contains a comma that is also used as the delimiter for CSV files
Summary: Assertion Failure Message contains a comma that is also used as the delimiter...
Status: RESOLVED FIXED
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.3
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-10 04:53 UTC by Ali El Gamal
Modified: 2007-10-10 14:38 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ali El Gamal 2007-10-10 04:53:41 UTC
1- Create a new test plan that includes a sampler
2- Add an assertion that you are sure is going to fail when you run the test.
3- Add a Simple Data Writer listener and make sure you set it to save in CSV
format and to show the assertion failure message
4- Run the test

The assertion failure message starts with "Test failed, " which includes a
comma. Commas are used as the delimiter for the CSV file so the resulting CSV
file will contain an extra field.
Comment 1 Sebb 2007-10-10 07:30:04 UTC
This is a general problem with the CSV format - for example, a label can 
contain a comma. However it's trivial to fix this case (and the user has no 
control over it), so I'll replace the comma as a work-round.
Comment 2 Sebb 2007-10-10 07:41:53 UTC
r583492 in trunk.

Will create new bug for general CSV enhancement.
Comment 3 Sebb 2007-10-10 14:38:08 UTC
Forgot to add - in the meantime, a work-round would be to use a different 
delimiter. For example, use tab. This can be set in the jmeter.properties file 
as follows:

jmeter.save.saveservice.default_delimiter=\<tab>

where <tab> is a tab character - not the characters < t a b >

The next version of JMeter will allow \t as well to make it easier.
Comment 4 The ASF infrastructure team 2022-09-24 20:37:40 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2032