POC process in Load testing

[satyabang]

Hi,

Please give me some idea how to carry out the POC in Load testing.

Kindly give me sample templates if available.

Thanks in advance,
Satya

[James Pulley]

Amazing. This is the third forum this question has appeared in within t

Hi,

Thanks in advance,
Satya

--
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

[James Pulley]

Ooops...Fat fingered that one. This question seems to be very popular of
late in multiple forums.

Let's see, a POC. Well, as this is a testing tool I think it is only
natural that you begin with a set of requirements for what the tool must be
able to accomplish in your environment with your application.

Next, contact each of the vendors involved with your requirements for a
performance testing tool. Indicate your timeline for purchase. They will
inquire about your budget to gauge your level of seriousness.

Next comes the evaluation. As you don't know the tool it is in your best
interest to work directly with the systems engineer assigned to your
evaluation by the vendors under evaluation. You will likely have to
incorporate some analog components in your evaluation criteria. While an
answer to particular criteria may be 'Yes' to capability, the skills
required may be totally absent within your organization and will either have
to be acquired or built. Be sure and print out the license agreement and
fully understand what you are able to do within the license and compare this
with how you plan to deploy the product. You may need a different license
or different product to accommodate your deployment needs from the default
license or default product configuration.

Finally comes the acquisition and deployment. Cut the PO. Include
standardized product training in the acquisition costs. Include the cost
of having a mentor work with you (minimally) for your first two gigs
following training. Ideally this should be for three gigs. Your level
of efficiency at a given point after deployment with the tool is directly
related to the number of shortcuts you will try to take here related to
training and mentoring. Less training and mentoring equals less efficient.

'Pulley

-----Original Message-----
From: lr-loa...@googlegroups.com [mailto:lr-loa...@googlegroups.com]
On Behalf Of satyabang
Sent: Tuesday, February 23, 2010 9:37 AM
To: LoadRunner
Subject: POC process in Load testing

Hi,

Thanks in advance,
Satya

--

[John Crunk]

I'm not biting

John Crunk Ph.D ABD
Sent from my iPhone

[Jeff Leonard]

carry it out in a bag...oh, wait you mean. ..

[Kevyland]

First get rid of abbreviations and cutie nerdy buzz letters.
I had no idea what POC was (Proof of Concept or Plan of Correction)
and thats the NaCl (get it "salt").

POC = Proof of Concept which can be used to facilitate a go or no go
decision. In your case it appears to be a product purchase decision.
Create a check list of what your trying to do so you can evaluate the
product. What makes up the check list? Lots of stuff!
1. The POC needs to expose the end-to-end development lifecycle -
design, development, test/debug, deployment and execution (monitoring
and management).
2. Purchase cost and maintenance costs need to be addressed over the
lifespan of the product.
3. Make sure that the evaluation consists of a standard test
demonstration by the vendors - (of something you want tested not what
the vendor shows you). Bells and whistles dont mean much if you cant
compare apples to apples and a special feature of your application
cant be tested or requires a special purchase.
4. Consider training, followup training and how easy it would be to
find skilled people in your local job market. Why by a tool when
there's no local job market with any of those skills?