Differences between Siebel tests and HTTP tests

Siebel tests precisely designate datapool candidates, include an additional type of data source, and store variables in a proprietary data structure. In addition, page names are created during test generation to help you find pages of interest.
The primary difference between a Siebel test and a standard HTTP test is in how dynamic data is stored and substituted during a test run:
  • In a standard HTTP test, a data source (datapool variable, custom code, or a reference) is linked to a test value that is replaced at run time. Siebel tests support standard HTTP data sources and substitution. Datapools, which are explained in Providing tests with variable data, work the same way in Siebel tests as in standard HTTP tests, but the datapool candidates in Siebel tests are more precisely designated than in standard HTTP tests. In many cases, datapool substitutions are the only changes that you need to make to a Siebel test.
  • In a Siebel test, an additional type of data source, which is called a built-in data source, contains variables that you can use to replace a test value.

    These variables can be substituted for dates (in defined formats), time stamps, and counters throughout tests. In some cases, SWE Unique Value can be used as an alternative to a datapool; for example, to supply variable account names. For detailed instructions, see Correlating a request value with a built-in Siebel variable.

Siebel variables are stored in a proprietary data structure called a star array. A star array stores both strings and their length in hexadecimal format (length_string) or integer format (length*string). Siebel substituters have a method for substituting data and recomputing the length. You can substitute from a value in a star array (highlight a length_string or length*string format value, right-click, and then click Substitute). You are then asked whether you want a Siebel substitution or a standard HTTP substitution. You typically select Siebel data correlation.

Siebel tests are organized inside the test editor much like standard HTTP tests, but with some differences for pages:
  • The first page of a Siebel test is named Message Bar, which emulates the ticker-tape message that Siebel application pages display.
  • Page names are created during test generation to help you find pages of interest. For example, a typical change to make to a test before running it is to replace the user name and password that you typed during recording with values in a datapool. As shown in the example, the page from which you logged into the Siebel server is named Login - Send UserName/Password, to help you find this page quickly.