>Hey. Stop ripping stuff like that out of context ;p Sorry, not intentional , but people tend not to use assertions to check for correctness. >very nice, elaborate and precise protocol of all requests and responses in my loadbalancer log. A lot of apps return a status code of 200 with a user friendly error message - i suppose your app is different , but in general I dont think this would work. Anyway thanks for the discussion :)
On Fri, Sep 17, 2010 at 12:09 AM, Felix Frank <[email protected]> wrote: > On 09/17/2010 08:41 AM, Deepak Shetty wrote: > > So I guess here is where we agree to disagree. However > >> I don't really care for the response code. > > Correctness is almost always a prerequisite for a performance test. > > But yes , to each, his own ! > > Hey. Stop ripping stuff like that out of context ;p > > I can have Jmeter disregard the response code *only* because I have a > very nice, elaborate and precise protocol of all requests and responses > in my loadbalancer log. > > In other setups, I'd have to rely on Jmeter's notion of response > correctness or correlate web server logs to get an idea of what's going on. > > Cheers, > Felix > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
