Skip to Main Content
Return to Navigation

Configuring Execution Options in PTF Client

You can define execution options either in the PTF client or using the Define Execution Options page in the PeopleSoft Internet Architecture.

This section describes how to define execution options in the PTF client.

Image: Execution Options dialog – Options tab

This example illustrates the fields and controls on the Execution Options dialog – Options tab. You can find definitions for the fields and controls later on this page.

Execution Options Dialog - Options tab

In the PTF client, available execution options are listed in the left pane of the Execution Options dialog. The settings for the selected execution option are in the right pane.

These buttons are available on the toolbar:

Insert

Click to add a new execution option.

Delete

Click to remove an execution option from the list.

Accept

Click to save changes and close the dialog box.

Cancel

Click to close the dialog box without saving changes.

The following fields are on the Options tab:

Name

Enter a name for this execution option. You can use any name.

Prompt for Options

Specify whether the Execution Options dialog box should appear when a user executes a test.

Application

URL

Enter the URL for the PeopleSoft application to be tested.

User

Enter a valid user name for the application database.

Password

Enter the login password for the user.

Process Server

Select a process server from the drop-down list. This list is populated by the Process Server List field in the Configuration Options page.

See Defining Configuration Options.

Date Format

Select a date format.

Output

LogFolder

Select or enter the folder name to which logs will be written. If the folder does not exist it will be created.

Verbose

Specify whether to use verbose logging.

Select Yes to log a detail line in the log for each step executed in the test.

Select No to log only the test rollup status (Pass or Fail) at the test level and to log a detail line for failed steps.

Debugging

Skip PageSave

Select Yes to prevent a test from executing a save. You would, for instance, select this option to avoid duplicate values in the application database if you plan to run a test repeatedly.

Skip RunRequest

Select Yes to prevent the test from executing process requests.

Advanced Options Tab

This example shows the Execution Options dialog - Advanced Options tab in the PTF client:

Image: Execution Options dialog – Advanced Options tab

This example illustrates the fields and controls on the Execution Options dialog – Advanced Options tab. You can find definitions for the fields and controls later on this page.

Execution Options dialog - Advanced Options tab

The Advanced Options tab supplies the information required to connect to multiple portal URLs and to enable persistent variables.

The Portal URL is used to access the component when there is a step in the test to set the browser url (Browser.Set_URL). See Set_URL. To add a portal URL, use the Add link. To remove a portal URL use the remove link.

The following fields are on the Advanced Options tab:

Portal Name

Enter a valid portal name or select from a list of previously added portal names.

Note: The URL Type is saved in upper case.

URL

Enter the portal URL.

The portal URL is entered in the following format:

http://webserver/psp/domain/portalname/node

For example: http://myserver.us.oracle.com:8010/psp/ps/EMPLOYEE/QE_LOCAL/

Note: The ending backslash / is optional

Enable Persistent Variables

Select to enable saving and using persistent variables. Selecting this option enables the other fields in this group.

See Using Persistent Variables

By Execution Option Name

Persistent variables are stored in the database keyed by execution option name. Persistent variables can also be keyed by User ID, machine name or both.

By User ID

Select to store and retrieve persistent variables by PTF user ID.

By Machine Name Used for Playback

Select to store and retrieve persistent variables by machine name.

PeopleTools Tab

This example shows the Execution Options dialog - PeopleTools tab in the PTF client:

Image: Execution Options dialog – PeopleTools tab

This example illustrates the fields and controls on the Execution Options dialog – PeopleTools tab. You can find definitions for the fields and controls later on this page.

Execution Options dialog - PeopleTools tab

The PeopleTools tab supplies the information required to connect to DataMover.

The following fields are on the PeopleTools tab:

Tools Path (PsHome)

Enter the path to PS_HOME for this environment.

Connection Type

Select the connection type.

Server Name

Enter the name of the database server.

The Server Name field is enabled only for Sybase and Informix platforms.

Database Name

Enter the name of the database for this environment.

User ID

Enter a valid database user name.

Password

Enter the password for this user.

DMS Input Path

Enter the Datamover input path.

DMS Output Path

Enter the Datamover output path.

DMS Working Path

Enter the Datamover working path.

Log Export

This example shows the Execution Options dialog - Log Export tab in the PTF client:

Image: Execution Options dialog - Log Export tab

This example illustrates the fields and controls on the Execution Options dialog - Log Export tab. You can find definitions for the fields and controls later on this page.

Execution Options dialog - Log Export tab

The Log Export tab allows you to archive the result logs to a file system in XML + XSL format at the end of each test execution. This option provides the following:

  • Log is accessible from any browser.

  • PTF client is not required to verify test results.

  • Logs will be available even after the environment or database is brought down or upgraded.

  • Since the log is in XML format, you can write customized utilities to parse or interpret the logs as needed.

Use Export Log

Select Yes to activate the export log functionality.

Path

Specify the shared drive to store the log files.

Note: Ensure that the shared drive path allows users full read/write access. The path can be customized using existing system variables. See System Variables

Style Sheet File

(Optional) Specify the path to the stylesheet. If specified, the exported XML log will be saved with the stylesheet.

You can create your own stylesheet to format the XML. If this field is left blank, the XML will not be saved with a stylesheet.

Note: Ensure that the shared drive path allows users full read/write access. The path can be customized using existing system variables. See System Variables

Add Time Stamp

If set to Yes the XML filename will be appended with the Time Stamp in the below format:

<TEST_NAME>-<LOG_ID>-T<YYYYMMDD>_<HHMMSS>

Example: FSCM_INS_VER-LOG5-T20121128_163649.XML

Export Images

If set to Yes the Image will be saved in the same Log folder as the XML Log in the format below:

<TEST_NAME>-<LOG_ID>-<OPTIONAL_TIME_STAMP>-<LINE_NUMBER_AS_SHOWN_IN_LOG>

Example: FSCM_INS_VER-LOG5-T20121128_163649-Line30.JPEG

This is an example of a formatted log opened in the browser:

Image: Sample export log displayed in the browser

This example illustrates a sample export log displayed in the browser.

Sample export log displayed in the browser

Default Execution Option

When a user clicks the Accept button in the Execution Options dialog box, PTF stores the name of the selected execution option and uses it, by default, in subsequent test recordings and executions. A link in the lower right corner of the PTF application window displays the name of the default execution option. You can click the link to open the Execution Options dialog box.

Overriding the Default Execution Option

Use an Execution step with a Set_Options action in a shell test to override the default execution option.

See Execution.