Response Assertion assumes 4XX is unsucessful
I'm using JMeter to do some negative testing on my webapp, but when I add a Response Assertion which (correctly) expects that the response code will be 404, the result is always a fail.
I looked through the source code and it appears in HTTPSamplerBase, that JMeter will only check the response assertion for codes 200-399 inclusive; otherwise it assumes it's a failure.
To me this is a bug in JMeter as it prevents one from executing negative testing. Perhaps if a response assertion was omitted, then it would be logical to assume that a 4XX would be a failure, but when I've specified that I expect a 4XX shouldn't it be honoured?
Does any one know of a way to get around this problem? I'd appreciate any feedback on this issue.
Re: Response Assertion assumes 4XX is unsucessful
Looks like I missed something when I "read the FM"; setting the "ignore status" checkbox in Response assertion solves my problem.