Jmeter does not look for a specific outcome on a page. I gather from your narrative that you're not looking for anything in particular on any page you retrieve. If you request the next page without logging in, your application probably just returns a login page again. Jmeter will see that as a "correct" result, because the web server did not respond with an error.
If you run your script with the login disabled and then click on the first http client request in your results tree listener, you can see what was returned in the response tab over on the right. I bet it's a login screen. I would also consider that to be a "Correct" response -- if you request the next page without logging in and it just gives you the next page, that would be a pretty serious problem with your application. So what you need to do is verify the results of the page that was returned to you. You could add an XPath assertion to your httpclient request and tell the assertion to look for something unique that you're looking for on the page you get back from your application. In the case you mentioned where you sent the wrong user name, the application probably responds with an authentication error and the login page again. So you could use Xpath assertions to verify that the error text shows up on the returned page, and that you're being prompted to log in again. Then if you get any other page, jmeter will show a failure at that point. You can test this by leaving the assertion in place and supplying the correct login and password. When you go to the next page, the assertion will look for the error text, not find it and cause a test failure. -- Bruce Ide flyingrhenqu...@gmail.com
