Hi
You can record and replay a script and expect it to work only if your
application doesn't use anything dynamic - i.e. a parameter that can
potentially change values with time . This might take on a variety of
things like
a, Security Form tokens (for e.g to prevent request forgeries)
b. timestamps
c. Encrypted values that are used for Single sign on
d. Session ids if your application is using url rewriting
etc.
An easy way to identify this is record the same script twice and check for
differences - Parameters that are changing values are dynamic
(Alternately understand how your application works from a dev)

Once you identify the parameters , then you have to use a Post processor to
extract values from the response that has these dynamic values into a
variable and then use ${variableName}. The only exception to that is
session id which can *usually* be handled by a cookie manager (assuming
your application supports it) . In rare cases , it is some javascript
executing on your page that is creating the dynamic values - in which case
you have to simulate the same in JMeter.

And you have to use assertions to know if your script is working as
expected or not.

regards
deepak



On Tue, Mar 15, 2016 at 6:11 AM, Vikash kumar <[email protected]>
wrote:

> Hi,
>
> I've recorded some scenarios  including "Login" to my application scenario
>  from Jmeter, but while playing the recorded scripts from Jmeter i am
> seeing that the user hasn't logged in and is still present at the landing
> page only. I have used a 'Tree Listener' and navigated to the request and
> opened the "Response Data" tab,  seeing the HTML response of the request
> sent and received by JMeter. I've used only one user/thread for my
> execution.
>
> Any idea why it's showing like this in the HTML response of "Response Data"
> tab in the  'Tree Listener'  listener. Do i need to tweak any change or
> something.
>
> Earliest reply is deeply appreciable.
>
> Regards,
> Vikash
>

Reply via email to