2. Performance testing is basically understanding how well and quick the software runs. What you
are testing really depends on what your application does. Typically there is a statement of
performance requirement in the initial requirements you are trying to test for.
For example, in database you would measure number of transactions per time period. For
networking, it would be number of communication packages. For a display/monitor, how
quickly it can display images over time.
3. •
You would test performance in an unloaded (nothing else going on) system to find out what
the is best the software/system can do. You would then test in based on a typical load (other
programs running, etc.) to see how the system responds in simulated use.
•
Typically these are done over a long period of time (relative to what is being measured) so
you get an average value.
