load runner issues with parameterization

[gajee]

hey i have recorded my actions in vu generator and i have paramerized
my data but still i am not getting actual results and also not getting
any error message also.

what i am doing is .
Login in to the website and enter some text in search field and click
on go button..now click the search results and again do the same
things for different data continuously with only one user..

[James Pulley]

Correlate

--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

[prasenjit dutta]

u r not correlating ur script.....try to find out in ur script which data u can correlate.....correlate those data .....ur script will start working......
;-)

--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

--
Prasenjit

[Jatin Chaturvedi]

First check if you have done the correct parameterization or not? For that run few (say 3-4) iterations of script and see runtime data for your parameterized values. Check if it is according to what you was expecting or not? If everything goes fine than u need to correlate ur script.

 

And ya one suggestion for u. ALWAYS record signout when you record sign-in otherwise when you run load test with multiple users, there may b a chance that multiple session will open up but not getting close during whole scenario run and that may create problem later on. KILL THE SESSION

 

Thanks,

Jatin

[Floris Kraak]

On Thu, Dec 24, 2009 at 10:56 AM, Jatin Chaturvedi <jcha...@gmail.com> wrote:
> And ya one suggestion for u. ALWAYS record signout when you
> record sign-in otherwise when you run load test with multiple users, there
> may b a chance that multiple session will open up but not getting close
> during whole scenario run and that may create problem later on. KILL THE
> SESSION
>

Is that really wise? How many people actually use that logout button
in real life?
Sure, us IT professionals might be well behaved but .. I know tons of
people just close the browser and forget about it.

Regards,
Floris
---
'What does it mean to say that one is 48% slower? That's like saying
that a squirrel is 48% juicier than an orange - maybe it's true, but
anybody who puts the two in a blender to compare them is kind of
sick.'
--- Linus Torvalds

[SaiKiran Cheemakurthi]

Did you noticed how script got generated when you perform the operations on search results. Post script from entering some text in search field on with comments. I am help you

Sai

[Jatin Chaturvedi]

But we IT Professionals need to do our work wisely as we are getting paid for it. :)

 

Thanks,

Jatin

--

[LoadTestGuy]

create a script with logout and another script without logout...
run both the scripts..
REAL TIME SCENARIO

[Jatin Chaturvedi]

But your load test result is prone to fail

Intentionally

Thanks,

Jatin

[Floris Kraak]

On Thu, Dec 24, 2009 at 1:37 PM, LoadTestGuy <loadt...@gmail.com> wrote:
> create a script with logout and another script without logout...
> run both the scripts..
> REAL TIME SCENARIO
>

The better way to do that:
Right click on the group, choose Run time settings -> Run logic.
There, add a block, set it to random percentage. Within add a Logout
action and a "DoNothing" action. Set both to 50%. Done.

[Floris Kraak]

On Thu, Dec 24, 2009 at 2:05 PM, Jatin Chaturvedi <jcha...@gmail.com> wrote:
> But your load test result is prone to fail
>
> Intentionally
>

The test won't fail. The application you are testing might. But is
that not the point of testing?

[gajee]

thanks a lot i will try today........

On Dec 23, 8:47 pm, prasenjit dutta <prasenjit...@gmail.com> wrote:
> u r not correlating ur script.....try to find out in ur script which data u
> can correlate.....correlate those data .....ur script will start
> working......
> ;-)
>
>
>
>
>
> On Tue, Dec 22, 2009 at 2:21 PM, gajee <gajendr...@gmail.com> wrote:
> > hey i have recorded my actions in vu generator and i have paramerized
> > my data but still i am not getting actual results and also not getting
> > any error message also.
>
> > what i am doing is .
> > Login in to the website and  enter some text in search field and click
> > on go button..now click the search results and again do the same
> > things for different data continuously  with only one user..
>
> > --
> > You received this message because you are subscribed to the Google
> > "LoadRunner" group.
> > To post to this group, send email to LR-Loa...@googlegroups.com
> > To unsubscribe from this group, send email to

> > LR-LoadRunne...@googlegroups.com<LR-LoadRunner%2Bunsubscribe@goog legroups.com>

[prasenjit dutta]

I have tested few application where there was no logout button......it was like once u r done with all ur action close the browser.........it worked fine.
tell me one thing what will happen in a scenario like, an application is being used by 100 people and all the people closing the browser without logging out and the application can handle 101 concurrent session, wiil this application crash after a certain period of time??

--
Prasenjit

[Floris Kraak]

On Sat, Dec 26, 2009 at 4:29 PM, prasenjit dutta <prasen...@gmail.com> wrote:
> I have tested few application where there was no logout button......it was
> like once u r done with all ur action close the browser.........it worked
> fine.

That could easily happen. It might have had no sessions at all
(stateless code) or simply delete sessions based on a short time to
live. (see below.)

> tell me one thing what will happen in a scenario like, an application is
> being used by 100 people and all the people closing the browser without
> logging out and the application can handle 101 concurrent session, wiil this
> application crash after a certain period of time??

It might crash if memory runs out due to having to much session state in memory.

But it really depends on what the application does and how much
session management is needed. If there is very little state to store
in a session then the application might be able to cope with huge
amounts of sessions.
Some apps even do without sessions at all (stateless).

Having little session state doesn't necessarily mean it is a high
quality piece of code though - I've seen applications attempt to be
'stateless' when that model was really inappropriate for the problem
at hand, resulting in monstrous web apps that carry all their state in
things like ViewState variables or tons of barely tested impossible to
debug javascript ;-)

The other thing that has to be kept in mind is how long the sessions
are kept around in memory - how long is the TTL (time to live) of the
sessions? Every session will consume some memory. Even with small
sessions, if sessions are never deleted and the associated memory
freed then sooner or later the application will consume all available
memory - with predictable results.

What you also sometimes see is the case where an application has large
sessions and long TTL settings. More often than not the logout button
does not remove these sessions - all it does is remove the cookie that
was set in the browser, not delete the associated sessions. Whether
the users logged out or not does not make an iota of difference to the
application's memory use in this case.
When the users log out and log in again they would just create another
long lived session for the application's memory space to handle.

To be honest though session size is rarely a real problem for web
apps. With today's hardware with multiple gigabytes of memory the
session management problem would need to be quite bad for it to cause
problems. Usually other things cause problems first ;-)