jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fitzpatrick, Adrian" <>
Subject RE: HTTP response assertion apparantly not working
Date Thu, 05 Mar 2009 13:10:08 GMT

This may help, from a previous post (response from sebb) -

On 12/01/2009, George Barnett <> wrote:
> Hi,
>  I've got a test suite that tests for missing pages as we have a custom 404
> handler which needs perf testing.
>  I check the response to ensure the response code matches 404 however
> seems to unconditionally mark 404 responses as failed.
>  Is there a workaround for this?

"Ignore Status" will allow such responses to be checked.

Also, think your assertion might be the wrong way round - i.e. "not"
shouldn't be ticked if you don't want 301 to be an error

-----Original Message-----
From: wicky_boy []
Sent: 05 March 2009 13:02
Subject: HTTP response assertion apparantly not working


This e-mail has been received by the Revenue Internet e-mail service. (IP)



Need a sanity check.

I have an HTTP request which I don't want to appear as an error in my test

The returned code and message is '301' and 'Moved Permanently' respectively.

I have setup the response assertion:

Response Field to Test = Response Code
Pattern Matching Results = Matches
Pattern to Test = 301

The repsponse message is:

Thread Name: Thread Group 1-1
Sample Start: 2009-03-05 07:55:37 EST
Load time: 3
Latency: 0
Size in bytes: 0
Sample Count: 1
Error Count: 1
Response code: 301
Response message: Moved Permanently

After putting in the assertion the step still appears in the view results
tree as an error?

Is there something obvious I'm missing?

View this message in context:
Sent from the JMeter - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:


This message has been delivered to the Internet by the Revenue Internet e-mail service (OP)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message