Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 86767 invoked from network); 18 Aug 2008 09:48:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Aug 2008 09:48:08 -0000 Received: (qmail 82767 invoked by uid 500); 18 Aug 2008 09:48:00 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 82736 invoked by uid 500); 18 Aug 2008 09:48:00 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 82725 invoked by uid 99); 18 Aug 2008 09:48:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Aug 2008 02:48:00 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 72.14.220.159 as permitted sender) Received: from [72.14.220.159] (HELO fg-out-1718.google.com) (72.14.220.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Aug 2008 09:47:04 +0000 Received: by fg-out-1718.google.com with SMTP id 22so1497969fge.1 for ; Mon, 18 Aug 2008 02:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=IWSBhASJxTg1l2StBCuIaxQV+CPnBwE87+xUWffkhG8=; b=fs5LNEXTLcx18DDEsLLtpripK42OeEl7BRovKg9yMgMS7lz19v2zSkGhtOptLm28wL tVGboMnC9OhlfrlCiNMm6bBlZ3OUzilc+3EP0RjS/2JnHKk1J98Xle7U1iGlLB6VKmb0 xwWw0sxnF5NXmP3oXS6opPb4PvIbFJ6qdh5ns= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RK9I2fDRCgieYK9QZNWIgvevMJc5Luv/l0uImMyF146G5Tg8PKSB1/4koizksLfz0b U+/jx9HLmytpfBRHMXqPG7W1AvZ8GT+3cWS0En2J3c3DeDqmcFlz0c1TzEMMhC9+nKJh 9jvcss3mXSlChLShlRS9hne+FefJdTRHK4HhA= Received: by 10.86.60.14 with SMTP id i14mr4354411fga.75.1219052852056; Mon, 18 Aug 2008 02:47:32 -0700 (PDT) Received: by 10.86.57.13 with HTTP; Mon, 18 Aug 2008 02:47:31 -0700 (PDT) Message-ID: <25aac9fc0808180247v73f28924me939119c92541f10@mail.gmail.com> Date: Mon, 18 Aug 2008 10:47:31 +0100 From: sebb To: "JMeter Users List" Subject: Re: Queries | How Can I save assertions results in CSV output? In-Reply-To: <6ea7516d0808180056l2c55f04dya8a2dfd9aa370736@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6ea7516d0808180056l2c55f04dya8a2dfd9aa370736@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 18/08/2008, Mohamed Niyas wrote: > Dear Team, > > I have seen a couple of mails regarding the CSV output from JMeter. I > understood that if i make it CSV output, it would save memory resources. I > am running my scripts in Non-GUI mode. > > The problem is that my scripts contains with assertions in some of the > samplers. Those assertions are mandatory for to check out the > proper output. If i enable xml ouput, i am getting the assertion results. > But in a long run i will be running many concurrent users that time > this would take much time & would create a huge size output file. > > *Questions:* > > 1) If i enable the CSV output, those assertions results are not included. So > obviously i am missing some valuable data whether > it has succeeded or not? The status will be set to fail if the assertion fails. > Can we make a CSV output to save the requests > query string & Assertions results? Not the request string, but you can save the Assertion message. See: http://jakarta.apache.org/jmeter/usermanual/listeners.html and http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Sample_Result_Save_Configuration > 2) If i enabled xml output, how can i save the request? I meant the > complete request query string. I have tested with the > Jmeter.Properties file by enabling some parameters & running the tests > again. But none was carrying this information. > We can see the request query string if we are running from Jmeter GUI. > > 3) Can we have a sample perl scripts which converts the JTL output to CSV > output? (if we can not save the assertions in CSV output.) I don't know of any existing script. > Please share your thoughts on this? > > > -- > Regards, > Mohamed Niyas M > Mobile: 98804 59080 > niyas.mohd@gmail.com > to_niyas@yahoo.co.in > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org