Customizing a script template

Rational® Functional Tester uses its default script templates to format and provide basic information when you create a script. You can customize the information and format by customizing the script templates.

About this task

To customize a script template, use the Rational® Functional Tester Script Templates Property Page. In Rational® Functional Tester, Eclipse Integration, you can also use the Java editor, which provides simple formatting of the template and help with the Java syntax. In Rational® Functional Tester, Microsoft Visual Studio .NET Integration, you can use the Code editor.

Procedure

  1. Right-click a functional test project in the Projects view, click Properties > Rational® Functional Tester Script Templates from the pop-up menu.
    The Rational® Functional Tester Script Templates Property page is displayed.
  2. In the Select template type list, click the script template to customize.
  3. Edit the script template from the Functional Test Script Templates Property page:
    1. Edit the script template using the appropriate placeholder. For information about placeholders, see Customizing Script Templates related topic.
    2. Optionally, click Apply to save your edits as you work or when you finish changes to one script template.
    3. Click OK to save all edits to all script templates.
    4. If you use ClearCase®, you must check out the script template(s) by checking out the Functional Test project. When you click Apply or OK, the ClearCase® Check Out dialog box opens to check out the file before you save it. In the Check Out dialog box, click Finish to check out the script template. Click Apply to save your edits as you work or when you finish changes to one script template or click OK to save all edits to all script templates.

    You can also edit a script template with the Java editor in Rational® Functional Tester, Eclipse Integration or the Code Editor in Rational® Functional Tester, Microsoft Visual Studio .NET Integration. Click Open current template in Editor to open the template in the appropriate editor.

    Tip: To omit associated punctuation for any null properties, enclose the placeholder in a pair of carets (^). For example:
    ^%map:contextComment%^