Performance Testing
From bemoko developer wiki
Contents |
New Documentation
This article has been superseded by the article in the bemokoLive product documentation site - please visit this page for more up-to-date information
Introduction
Performance testing is an often overlooked and/or poorly executed activity. A standard part of any project implementation is to test the system under load – often this is the first time the code has been tested in such a way and it highlights major problems which should have been found in the QA cycle.
Whilst all situations and loads cannot be catered for, there should be a standard test suite so that the performance of new releases can be checked and compared to previous releases. A new release with lots of fancy features should not be slower than the previous release!
We Do as We Say
At bemoko, we use our own website as the test application[1]. This provides us with a benchmark to test all our releases.
We test for performance and memory leaks using the excellent Apache JMeter to generate the load. We have a file containing all the URL’s on the website and another file which contains various user agents to run against the site. We can then simulate any number of users continually accessing the pages on different devices.
References
- ↑ bemoko blog on performance testing - http://blog.bemoko.com/2009/02/06/performance-testing/