e-Commerce > IBM WebSphere Commerce > WebSphere Commerce Load Testing
Introduction
Load testing of WebSphere Commerce software is a critical component to the success of the project. Load testing allows for testing of all facets of the Commerce site as well as all related interfaces and back-end systems. Load testing allows the project team to subject the WebSphere Commerce software to the anticipated traffic that that system should generate. This allows the team to identify and resolve any potential bottlenecks in the system. This can all be accomplished prior to launching the application, allowing all issues to be resolved before the go-live date.
Types of Load Testing for WebSphere Commerce
Generally, the load testing of WebSphere Commerce is conducted in two scenarios. The first is short running tests with a heavy workload. These tests are generally run for 30 minutes to a full hour. The second is longer running tests with a constant moderate workload. These tests are generally run for 4 to 8 hours, but can be run as long as 24 hours. Each approach provides different information that can be used to evaluate different components of the application. Generally, shorter tests are used to evaluate page response times, system interfaces, as well as hardware performance. Longer tests are generally used to evaluate caching strategies, to check for memory leaks, as well as to validate memory performance. Load testing can provide the project team with a general idea of how many users can access the system simultaneously while maintaining the desired level of performance.
Load Testing versus Regression testing
Load testing is not regression testing. Generally, regression testing tools simulate specific clicks on a screen, and work at the GUI object level. However, load testing simulates the user clicking the ‘Submit’ button on the page, sending data to the Web Server. This can then be done for a high volume of users simultaneously. Both types of testing are important, however, it is critical to use the right tool for the job at hand.
Our Approach to Load Testing WebSphere Commerce
Our standard approach to load testing WebSphere Commerce is to use a load testing tool to simulate site traffic, which also tests the various areas of the application. We use data from the backend systems to create load testing scripts that simulate browsing traffic. This traffic, generally, is designed to access all portions of the website. Wherever possible, we also develop scripts that generate a completed customer order within commerce applications.
Then, using a collection of reporting tools, we capture the results of these tests and place the results into charts and graphs for evaluation. The data in these reports typically point to areas of contention within the site, or the related interfaces.
For more information, see this document:
| Commerce Load Testing |
