| Article Index |
|---|
| A Road Map For Performance Testing: Asses The Problem Space |
| Page 2 |
| Page 3 |
| Page 4 |
| All Pages |
This
three-part series of articles on testing for performance outlines how you might
approach
performance
testing. The series is broken into the following articles which will be posted in coming days:
* Assess the problem space: Understand
your content and the system, and figure out where to
start
* Build out the test assets: Stage the
environments, identify data, build out the scripts, and
calibrate your tests
* Provide information: Run your tests,
analyze results, make them meaningful to the team, and
work through the tuning process
Depending
on your project's context, you may find yourself doing everything at the same
time.
In other
contexts, you might take more of a phased approach. Breaking the content out
into
those
topics gave me a useful framework for talking to my developer friend.
Throughout this series,
we will
look at possible activities that may take place, as well as possible artifacts
that one might
produce.
In this
first article, we will look at assessing the initial problem space so that we
can move forward
with the
first round of performance testing. This can include developing an
understanding of the
goals of
your testing, understanding the system(s) from various perspectives,
understanding how
the
system(s) will be used, and developing the initial scope for your tests.
Depending
on your project's context, you may find yourself doing everything at the same
time. In
other
contexts, you might take more of a phased approach. Breaking the content out
into those
topics
gave me a useful framework for talking to my developer friend. Throughout this
series, we
will look
at possible activities that may take place, as well as possible artifacts that
one might
produce.
In this
first article, we will look at assessing the initial problem space so that we
can move
forward
with the first round of performance testing. This can include developing an
understanding
of the
goals of your testing, understanding the system(s) from various perspectives,
understanding
how the system(s) will be used, and developing the initial scope for your
tests.
| < Prev | Next > |
|---|
