Bookshelf v7.5: Performance Automation

Testing Siebel eBusiness Applications > Develop Tests > Test Case Automation >

Performance Automation

Automation is necessary to conduct a successful performance test. Performance testing tools virtualize real users, allowing you to simulate thousands of users. In addition, these virtual users are less expensive, more precise, and more tolerant than actual users. The process of performance testing and tuning is iterative, so it is expected that a test case will be run multiple times to first identify performance issues and then verify that any tuning changes have corrected observed performance issues.

Performance testing tools virtualize real users by simulating the HTTP requests made by the client for the given scenario. The Siebel 7 Smart Web Architecture separates the client-to-server communication into two channels, one for layout and one for data. The protocol for the data channel communication is highly specialized; therefore Siebel Systems has worked closely with leading test vendors to provide their support for Siebel 7. Since the communication protocol is highly specialized and subject to change, it is strongly recommended that you use a validated tool.

At a high level, the process of developing automated test scripts for performance testing has four steps. Please refer to the instructions provided by your selected tool vendor for details:

Record scripts for each of the defined user types. Use the automation tool's recording capability to record the scenario documented in the test case for each user. Keep in mind the multi-iteration versus single-iteration distinction between user types. Many tools automatically record user think times; modify these values, if necessary, to make sure that the recorded values accurately reflect what was defined in the user type scenario.

Insert Parameterization. Typically the recorded script must be modified for parameterization. Parameterization allows you to pass in data values for each running instance of the script. Since each virtual user runs in parallel, this is important for segmenting data and avoiding uniqueness constraints.

Insert Dynamic Variables. Dynamic variables are generated based on data returned in a prior response. Dynamic variables allow your script to intelligently build requests that accurately reflect the server state. For example, if you execute a query, your next request should be based on a record returned in the query result set. Examples of dynamic variables in Siebel 7 include session ids, row ids, and timestamps. All validated load test tool vendors provide details on how dynamic variables can be used in their product.

Script Verification. After you have recorded and enhanced your scripts, you should run each script with a single user to verify that it functions as expected.

Siebel Systems offers testing services that can help you design, build, and execute performance tests if you need assistance.

Best Practice

Test Automation. Using test automation tools can reduce the effort required to execute tests, and allows a project team to achieve greater test coverage. Test Automation is critical for Performance testing, as it provides an accurate way to simulate large numbers of users.