|Bookshelf Home | Contents | Index | PDF|
In addition to these tips, you should also read and understand Execute Performance Tests.
A Siebel application that contains a list applet can return one or more records in response to a query. It can also return zero records. Both of these can be expected outcomes. When conducting load tests on a Siebel application that contains a list applet, make sure that the expected state of the list (either with records or without records) is the same during the recording session as it will be during the execution of the test. Failure to do so will result in a test error. If necessary, you can add a record before recording the test.
Where possible, break scenarios into several smaller scenarios to focus the tests. Make sure transaction definitions are granular enough to be able to pinpoint performance issues to specific GUI actions.
Eliminate HTTP traffic related to the message bar from transactions. Put message bar requests into your script outside of transaction blocks. Put one message bar request into your test script after every 120 seconds of wait time.
When setting up repeatable or iterative actions, make sure to leave the application in a base state from where the next iteration can pick up and complete successfully. Home page is a good example of such a base state.
It is also important to maintain the number of rows displayed in a list applet, or the number of controls displayed in a form applet. If Show More is clicked during the test, then Show Less must also be clicked before the end of the test.
An iterative action has to be self-sufficient in that all the correlations have to originate and end within the action. Values for correlated variables should not come from a previous action (which may or may not be iterative).
Make sure that user key fields are parameterized. Parameterize dates, especially variable dates (such as today's date or tomorrow's date). Parameterize time zones. If you do not parameterize time zone values, your script will fail for virtual users who are not set up to use the time zone in which the test was recorded.
Set up your data value parameters to be specific for each virtual user (for example, User1 logs in and searches for Contact1 while User2 logs in and searches for Contact2). Each virtual user should have its own subset of the data in the database.
Siebel applications restrict a user's ability to perform actions based on the roles and positions associated with the user. Make sure that the roles and positions of the users are compatible and allow the user to perform the required actions.
|Testing Siebel Business Applications|