Web Add-in Extensibility Planning Checklist

Use this checklist to plan the support for your custom control.

Custom Control Support Planning Checklist

Specify in Toolkit XML?

Support by JavaScript function?

q

The sources for this custom control are located in:
  

n/a

n/a

q

Specify the Web test object base class that the new test object class extends: (Default—WebElement)
  

n/a

n/a

q

Is the base test object class WebElement?
Yes/No

If No, is there a base element (an element that matches the base test object class)?
Yes/No

If there is a base element, do you need a JavaScript function to return it?    Yes/No

Yes/No

Yes/No

q

Specify the New Web test object class details:

  • Test object class name:

  • Generic type (optional):

  • Icon file location (optional):

  • Identification properties for description:

  • Default test object method:

  • Help file location:

n/a

n/a

q

Specify the basis for identifying the test object class to use for the control (consider different browsers):
  

Yes/No

Yes/No

q

Specify the basis for naming the test object:
  

n/a

Yes

q

List the identification properties to support. Mark which should be available for checkpoints and output values (and which should be selected by default in checkpoints) and which (if any) should be used for Smart Identification:
  

Yes/No

Yes/No

q

List the test object methods to support (if required, include arguments, return values, Help file location and Help ID):
  

  

Yes/No

Yes/No

q

Provide a dynamic list of values for any test object method arguments?
Yes/No (default)

If so, list the arguments:
  

n/a

Yes/No

q

Specify the types of children that UFT should learn with the control:
  

Yes/No

Yes/No

q

Display test objects of this class in the Object Spy?
Yes (default)/No

Yes/No

n/a

q

Provide support for recording?
Yes/No

If so, list the events that should trigger recording:

  

Yes/No

Yes/No