Testing Siebel eBusiness Applications > Automating Functional Tests > Using Siebel Test Automation for Functional Testing >

Hand-Scripting Components That Are Not in the Test Object Repository

One method of test script development involves using a third-party test automation tool to record the actions that you perform in the Siebel application. However, you also can write scripts by hand (without the use of a recorder). If you write the script by hand, the necessary test automation objects might not exist in the test tool's object repository. Therefore, you must insert special arguments to call the test automation object directly. For example:

SiebText("micclass:=SiebText", "repositoryname:=lastname")

The value for micclass is the object type from the automation object model (in this case, "SiebText"), and the value for repositoryname is the name of the object in the Siebel repository. For automation objects that do not have a matching representation in the Siebel repository, use the automation object type for both micclass and repositoryname. For example:

SiebPDQ("micclass:=SiebPDQ", "repositoryname:=SiebPDQ")

Using these special arguments, you can reference container objects and objects that execute test actions. This allows you to author test scripts without having to record test steps manually. See Functional Test Object Reference for more information on object types and repository names. For more tips on preparing test scripts, see Best Practices for Functional Test Script Development.