200 works just fine. That is, if I use the Response Assertion set to assert 200 on a request that returns 200, it behaves correctly. If I change that same assertion to 209, for example it fails as it should.
However 404 fails no matter what I set the pattern matching rules to be. this is killing me! On Tue, Nov 1, 2011 at 2:26 PM, Ed Young <[email protected]> wrote: > I have a simple HTTP get request with a View Results Tree and a Response > Assertion. Even though the request returns 404 the response assertion > fails. It seems pretty straight forward, so I can't see what I'm doing > incorrectly. > > I've tried all the HTTP Request Implementations. > > The response assertion is > Response Field to Test is > Response Code > Equals > 404 > > > The request returns > Thread Name: Component Thread Group 1-1 > Sample Start: 2011-11-01 13:39:39 MDT > Load time: 201 > Latency: 201 > Size in bytes: 302 > Headers size in bytes: 185 > Body size in bytes: 117 > Sample Count: 1 > Error Count: 1 > *Response code: 404* > Response message: Not Found > > Response headers: > HTTP/1.1 404 Not Found > Date: Tue, 01 Nov 2011 19:39:40 GMT > Content-Type: application/json;charset=UTF-8 > Keep-Alive: timeout=15 > Connection: Keep-Alive > Transfer-Encoding: chunked > > > HTTPSampleResult fields: > ContentType: application/json;charset=UTF-8 > DataEncoding: UTF-8 > > > > -- > - Ed > -- - Ed
