That makes sense. I was hoping there was a property to make response assertions ignore the transaction controllers.
Thanks for the info! --- sebb <[EMAIL PROTECTED]> wrote: > In 04/10/2007, John Dempsey <[EMAIL PROTECTED]> > wrote: > > Hi Guys, > > > > I'm putting a response assertion at testplan level > to > > check if any of the sample responses contained the > > word error. > > My http request samplers are grouped under > transaction > > controllers that generate a parent sample. > > The samplers pass the assertion but the > transaction > > controller fails with the message below. > > > > Assertion error: false > > Assertion failure: true > > Assertion failure message : Response was null > > That's because a TC does not have any response data. > It would not make sense; one cannot aggregate > response fields, only > the time and bytes. > > > Is there a way around this? > > Move the Assertion ... > > > And is it a bad idea to have an assertion at the > > testplan level? > > Only if there are some samples to which it does not > apply. > > For example, the response time assertion would be OK > in this situation. > > > Thanks! > > John. > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.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] > > Send instant messages to your online friends http://uk.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
