Performance Testing

From CitconWiki
Revision as of 16:49, 29 June 2008 by 165.228.165.178 (talk)
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Testing response times throughout the project lifecycle can help as an early indicator of performance issues.

Production-like environments are expensive to use - this can lead to limited load testing, and the resultant risks.

When benchmarking performance testing, don't change the codebase and the environment/infrastructure at the same time - freeze one whilst modifying the other.

Stress testing - finding where the app breaks. Load testing - testing how the app deals with a typical/estimated load

A degree of performance testing can be done at each CI build cycle, but not always to the degree that will show system-level performance issues.

Note: Stuart Moncrieff will put up his slidepack on Agile Performance Testing sometime soon.