In this follow up post, we will take a look at the configurations we need to do once the PTF client is installed.
Once the application is launched, the Local options and the Execution options need to be configured.
Configuring Local Options
Once the application is launched, the Local options and the Execution options need to be configured.
Configuring Local Options
Local Options and Execution options can be
accessed by clicking the database name with a '@' symbol prefixed to it on the
top left corner of the PTF client.
The local options are specific to the machine
where the PTF client is installed. The process run options define the settings
for timeout for each process status. With the configuration below, if a process
invoked by PTF is in queued or posting status for 1 min, then the test will log
a warning message.
Similarly, the output folder and the output
format can be defined if PSQuery is run from PTF.
Configuring
Execution Options
Unlike Local options which are specific to a machine where it is installed, execution options once defined – are stored in the application database, and are available for anyone who logins to that application database to create, modify test assets. Only the administrator (who has PTF Administrator role) can configure the execution options for a database.
An execution option is for a specific application – so if two applications are to be tested from the same PTF client, then we would require two execution options, one for each application.
Basic Options
Under the basic options tab, the URL for the
application needs to be given along with the default user ID and password. This
URL is used to launch the application when a recorded test is played back.
The process server and the date format can
also be defined in this section.
Skip PageSave will skip the step in the test
case which attempts to save the component.
Advanced Options
Advanced Options tab provides the option to
enable persistent variables in the environment. Persistent variables store
information that can be accessed whenever the application database is used in
PTF client. They are similar to registry variables.
PeopleTools Options
It is in PeopleTools Options tab, we provide
the database user ID and password. This is very important – as this information
is used to retrieve test assets already stored in the database.
In this tab, we define where the log files
generated by the test cases are to be posted. A test case log can also have
snapshots of the PeopleSoft screens, and 'Export Images' option in this tab
will export the screenshots as images in the log export file.
Contributed by Karthik and Swetanshu
Cool stuff guys !
ReplyDelete