Performance Testing | 37
‘add script code here’ facilities that you tools you no longer need expensive
ended up using more and more as you tool-specialist consultants, it is not
developed correct test scenarios. uncommon for a zero scripting tool
However, there is a new breed to pay for itself in cost savings after
of tools available that require zero just two or three test projects. A side
scripting and allow you to do all you effect of adoption of such is that
need to ensure your tests are correct.
Whether you are under
now you will spend the majority of
These are enterprise class, proven in
pressure to cut testing
your time on true QA tasks, and less
many organisations, and are being time preparing for testing – hopefully
used every day to test mission critical
timescales (and hence
something you would all welcome.
applications. All without a single line probably sacrifice what The effort and time saving, coupled
of test script!
you know is ‘correct
with the intuitive ‘prompting’ layout
These tools are aimed at you the
testing’), are adopting
of the GUIs in the new tools, delivers
testers, are much quicker to use, make a major benefit to organisations: the
it easier for you to create correct test
an agile process, or just
tests that are executed are more likely
scenarios, imitate all the user actions wish to reclaim the role to correctly simulate the real world
you need to, and simulate more
you signed up for (tester
usage of the system, and hence the
business transactions.
– not developer), there
results of testing can be used with
more confidence.
How zero scripting tools work
is now a proven option
I can only speak for the tool I know
All of the enterprise class zero that can allow you to test very well - StressTester - but it is a
scripting tools work by removing the
more often, simulate
fact that no system tested with it
script editor and replacing it with GUI
more transactions, test
has ever experienced a performance
screens that you use to configure your or scalability problem after being
simulated business transactions. In the
correctly, in shorter
released into the production
better tools, the screens are laid out
timescales, with reduced
environment (and it has been used
in an intuitive manner to prompt you
effort and less cost.
to test hundreds of well known
to think about correct testing all the mission critical financial, publishing,
time. You have access to true context manufacturing, and
sensitive in-tool help as opposed scripting tools have the flexibility to travel applications). This is not only
to having to wade through bulky be configured to do whatever you because of the tool, it is because the
reference manuals. need them to, yet you do not write a tool’s ease and speed of use allows
These tools still allow you to do all line of script code. And it goes without the testers – you and I – to focus on
you need to such as data variation, saying that configuring tests using GUI what is correct testing, simulate more
extracting data from application screens, which will prevent you from business transactions, execute more
responses, validating responses, saving incorrect information, is far tests, and hence not need to cut the
auto-correlating session variables, easier to learn and quicker to use than corners most of us are being forced
specifying alternative routes through writing test scripts for most of us. to do at present.
transactions, etc. The difference is What does that means in terms of In addition, by adopting an easy
that you are configuring using a GUI, reduced effort? Well as the head of to learn and use tool in the
as opposed to programming in a script performance testing at a major UK development teams, without the
editor. testing consultancy stated: “A job that need for QA environments or data,
Take a look at an average would take 10 days to prepare using developers can quickly and easily
performance test script – how many LoadRunner, takes two or three days spot the majority of the application
lines are actually making application using StressTester - a leading zero performance and scalability problems.
requests? Very few when compared scripting tool.” These can then be corrected much
to all of those that are initialising and Remember that on average 70 earlier in the development process,
updating variables, extracting response percent of the performance tester’s which will again shorten the overall
data, looping, forking, etc. It is no effort is spent on scripting. On a four project delivery time.
wonder that scripting takes so much week testing project with two testers,
effort and that even the best and this would equate to 28 days of Less effort, less cost
most conscientious testers can make scripting effort. Using a zero scripting Whether you are under pressure to
(programming) mistakes. tool, this could be reduced to under cut testing timescales (and hence
six days – saving 22 man days – over probably sacrifice what you know is
Zero scripting benefits half the test project’s total effort! ‘correct testing’), are adopting an agile
What benefit do these new Undoubtedly this also reduces the process, or just wish to reclaim the
tools deliver to the professional overall duration of the testing project, role you signed up for (tester – not
performance tester who wishes to and adopters of zero scripting tools developer), there is now a proven
focus on correctly testing applications report that this reduction is usually option that can allow you to test more
to ensure they can be released with over 50 percent. often, simulate more transactions,
Graham Parsons
Performance consultant
confidence? Due to these significant savings, test correctly, in shorter timescales,
Reflective Solutions
www.reflective.com
The obvious benefit is that zero and the fact that with zero scripting with reduced effort and less cost.
T.E.S.T | June 09 June 09 | T.E.S.T
Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52