Hi, I have verified that the Mail Visualiser triggers an email when associated with a Java Request when the Status field in the sampler is set <> OK. I am using Web Service requests and there is no apparent equivalent of the Status field for these requests. So can the Mail Visualiser work with Web Service requests? Regards, David Schulberg
Object Consulting | Senior Consultant email: [EMAIL PROTECTED] ---------------------------------------------------------------- consulting | development | training | support our experience makes the difference ________________________________ From: sebb [mailto:[EMAIL PROTECTED] Sent: Tue 14/08/2007 12:26 AM To: JMeter Users List Subject: Re: Mail Visualizer The status is displayed in the Listeners, which run after the assertions. The Mail Visualiser is a Listener, so will see the same status as the other Listeners. I've tested it and it works OK for me. On 13/08/07, David Schulberg <[EMAIL PROTECTED]> wrote: > Hi Sebb, > > No sign of anything in the JMeter log. > Where should I be able to see status change? > > David Schulberg > > Object Consulting | Senior Consultant > switch: + 61 3 8615 4500 fax: +61 3 8615 4501 > mobile: 0402 006 291 > email: [EMAIL PROTECTED] > ---------------------------------------------------------------- > consulting | development | training | support > our experience makes the difference > > ________________________________ > > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Fri 10/08/2007 7:30 PM > To: JMeter Users List > Subject: Re: Mail Visualizer > > > > I've looked at the code (and run a test) and found that although the > Mailer Visualiser only looks at the SampleResult status, this is > actually changed when the assertions are run, so it should work OK. > > Have you checked the jmeter log file for errors? > > On 09/08/07, sebb <[EMAIL PROTECTED]> wrote: > > Yes, the Mailer Visualiser only seems to look at the SampleResult > > status, not the AssertionResult or Sample class used by the Listeners. > > > > This needs looking into further... not sure if there is a work-round at > > present. > > > > Perhaps you could file a bug report for this? > > > > On 03/08/07, David Schulberg <[EMAIL PROTECTED]> wrote: > > > Hi All, > > > > > > OK it would appear that failures are classified only in terms of HTTP > > > response codes so I can't use a Mailer Visualizer to trigger emails based > > > on 'failed' response assertions. Any suggestions on how to send email > > > notifications if assertions fail? It appears to me that I probably need > > > something like a BeanShell listener. > > > > > > David Schulberg > > > > > > Object Consulting | Senior Consultant > > > email: [EMAIL PROTECTED] > > > ---------------------------------------------------------------- > > > consulting | development | training | support > > > our experience makes the difference > > > > > > ________________________________ > > > > > > From: David Schulberg [mailto:[EMAIL PROTECTED] > > > Sent: Thu 2/08/2007 5:52 PM > > > To: JMeter Users List > > > Subject: Mail Visualizer > > > > > > > > > > > > Hi All, > > > > > > Have set up a Mail Visualizer which tests OK. > > > When I run a script where I have a failed assertion I thought the Mail > > > Visualizer would send an email because it is set to respond when > > > Failures=1 but it doesn't. > > > > > > I have > > > o - Request > > > | - Response Assertion > > > | - Assertion Results > > > --Mail Visualizer > > > > > > It won't work if I have my Mail Visualizer tailed off my Assertion > > > Results either. > > > > > > Can I have my Mail Visualizer tailed off multiple requests? > > > Can I use variables in the Failure Subject field to report which > > > particular request(s) have failed? > > > > > > > > > Regards, > > > David Schulberg > > > > > > Object Consulting | Senior Consultant > > > email: [EMAIL PROTECTED] > > > ---------------------------------------------------------------- > > > consulting | development | training | support > > > our experience makes the difference > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > --------------------------------------------------------------------- > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
