Difference between revisions of "Performance Testing"
From CitconWiki
Jump to navigationJump to search (New page: 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 ...) |
|||
| Line 9: | Line 9: | ||
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. | 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.'' | ||
Revision as of 15:49, 29 June 2008
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.
