CustomExtension

You use the CustomExtension keyword to run a custom extension JAR file by entering the requisite ClassName and inputs to it, and providing the output variables for the return values from the program. To abort the test script, use the Abort-on-Fail end action. The default end action is Continue-on-Fail.

Signature

The CustomExtension keyword supports the following signature:

CustomExtension(ClassName,Input Values/Output Variables,Abort-on-Fail/Continue-on-Fail)

Note the following about the CustomExtension signature inputs and closing actions.

  • Target Object. Provide a fully qualified Custom Class Name.

  • Inputs. The following inputs are required:

    • NULL or a comma separated list of input values; and

    • NULL or a comma separated list of output variable names.

  • Closing Action. The closing action for the Custom Class Name (or the target object) can be:

    • Abort-on-Fail (that is, abort test script execution).

    • Continue-on-Fail (that is, continue with the next step).

      Continue-on-Fail is the default.

Note: Make sure to backup your extensions folder during a DISA upgrade, install, or uninstall process. For more information on how to build and deploy a custom extension JAR file, see Extending Keyword Automation Capabilities.

Desktop and Mobile Examples

The following table describes how to use the CustomExtension keyword in desktop and mobile applications.

Target Object Inputs Closing Action Comments

com.siebel.customobject

value1;@outvalue1;IPH3

Abort-on-Fail

ClassName with no input/output variables

com.siebel.login

value1;@outvar1;IPH3

Abort-on-Fail

ClassName with one value

com.siebel.objclick

value1,value2;@outvar1,@outvar2;IPH3

Continue-on-Fail

ClassName with one or more values

com.siebel.linkclick

@var1,@var2;NULL;IPH3

Continue-on-Fail

ClassName with variables

Handling SSO using CustomExtension:

  • Similar to PortalApplication, SSO reserved word is supported in Launch Keyword. If SSO is used launch Keyword will only launch the application but will not perform login.

    SSO User Id and Passwords can be provided in Parameters applet of Test Execution. Automatic variables with same names as Parameters and initialized with respective Values are created by framework.

  • Implement program to perform SSO login, and invoke via CustomExtension keyword. Pass the SSO credentials to program using variables automatically created from Parameters applet.

Test Step Sequence Description Action Target Object Inputs End Action

1

Launch without login

Launch

N/A

Siebel Universal Agent;SSO;Y

Test Step form applet:

Component Alias: Siebel Universal Agent

User Name: SSO

Clear Browser: Y

N/A

2

Login steps

CustomExtension

Fully qualified Java class name

Example: com.mycompany.automation..mySSOLogin

@SSOUser,@SSOPwd;@out1;IPH3

Test Step form applet:

Class : Siebel Universal Agent

Continue-on-Fail