I actually just wrote an ant task for running jmeter, and was just about to start working on a report for the assertion failures.
All I did was set jmeter.save.saveservice.assertion_results=all in jmeter.properties (everything else is default). I got the assertion failures in the output file running from the command line as well as from my ant task. BTW: I am using 1.8.1 release. Joe > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, March 03, 2003 11:57 AM > To: JMeter Users List > Subject: Re: Non-gui mode not reporting the details of > assertion failure > > > > > > We are trying to setup JMeter 1.8.1(build 02142003) to run > functional > > tests in > non-gui mode from ant. > > We have created an ant task for launching JMeter and are > seeing that > > some > reporting options that > > work in gui mode don't work in non-gui mode. Specifically we would > > like to > see the text of assertions that failed. > > > > I have been unable to recreate this problem using the source > from 02/27/2003. I get the assertionResults in both GUI and > nonGUI mode. I am not using ant, however. > > Offhand, I can't think of why GUI mode and nonGUI mode would > differ in terms of result reporting. The report code that > I've seen doesn't distinguish between them. > > > > > Swavek Lorenc > > > > --------------------------------------------------------------------- > 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]
