Hi a. First you have to understand how your application works - i.e. how does it detect that the browser doesnt support javascript (there are some ways to do this - e.g. set a cookie in javascript or make an ajax call that dumps a value into session or generate a token in javascript etc) b. Then you simulate the same in JMeter.
You usually debug this by running through the same steps on the browser but using a recording tool like fiddler/live http headers or whatever that captures the request and response headers. Then you compare the request and response in JMeter's view result tree. So if for e,g. a fresh(no cache) browser is sending some cookie (but there was no set-cookie , then its likely set from javascript and if your corresponding JMeter step doesn't send a cookie then you know where the issue is (note just an example - it depends on what your actual problem is) bottom line -You need to compare request / response of browser v/s Jmeter On Tue, Jun 11, 2013 at 12:40 PM, nmq <nmq0...@gmail.com> wrote: > Hi everyone > > I have run into an issue running my basic login script for the AUT. It was > working fine till we got a new build this week. > > Now, I have been a functional tester my whole career. My company wanted me > to do some performance test for them and I figured why the heck not. I'll > learn along the way, so basically I'm a newbie in this area. > > Since JMeter is an open-source (translated: free of cost) tool that is > supposedly powerful, we decided to use it (stupidly, without finding out > its limitations). I've invested quite some time in learning the tool so I'm > not ready to give up or switch to another. I'm also not a programmer and > don't have much info on java or javascript. > > Anyways, getting back to the point..... I looked at the response in > ResultsTree in HTML format and this is the message I'm getting on the Login > page: > > "This website requires JavaScript > Please activate JavaScript and press F5" > > HELP!! > > Regards > Sam >
