Professional Documents
Culture Documents
PeopleSoft Test Framework 8.53 Self Study Guide
PeopleSoft Test Framework 8.53 Self Study Guide
PeopleSoft Test Framework 8.53 Self Study Guide
Table of Contents
DEVELOPING TESTS ........................................................................................................... 24
Understanding the PTF Test Structure ...................................................................................... 24
Understanding the PTF Test Language ...................................................................................... 26
Working with Get_Property Action and the Message Tool ................................................. 27
The Log Type and the #LIST# Reserved Word ...................................................................... 30
OPTIMIZING TESTS ............................................................................................................ 31
Understanding Calling and Creating Tests ............................................................................... 31
Library Tests ....................................................................................................................................... 32
Shell Tests ............................................................................................................................................ 33
Using Conditional Logic ................................................................................................................... 34
Adding Page Prompting to a Test ................................................................................................ 35
Page ii
PeopleSoft Test Framework 8.53 Self Study Guide
Page iii
PeopleSoft Test Framework 8.53 Self Study Guide
The document describes PTF technology and its features and benefits. It
also describes the following processes:
Installing and configuring PTF.
Creating tests and test cases.
Developing tests.
Optimizing tests.
Incorporating scroll handling.
Identifying change impacts.
You can use PTF with most types of tests. A testing strategy provides the
basis for understanding how you will test the upgrade application. Your
organization may or may not require all of the testing stages listed for
your upgrade; that is determined by your testing strategy.
You can take more than one approach and method for testing your
upgrade. There are no standardized rules existing for testing. Several
types of testing can be used to determine whether an application is
functioning correctly after the upgrade. Testing types do not necessarily
run systematically, one after another; different test conditions can
sometimes run in parallel.
Page 1
PeopleSoft Test Framework 8.53 Self Study Guide
The terminology for types of testing can vary between different people
and organizations. Therefore, within your organization, especially within
the upgrade project team, everyone needs to understand the terms and
definitions of the testing that you will be performing.
Unit Test
System Test
Integration Test
Page 2
PeopleSoft Test Framework 8.53 Self Study Guide
Parallel Test
Acceptance Test
Regression Test
Page 3
PeopleSoft Test Framework 8.53 Self Study Guide
The test assets are stored in the database and they are readily accessible
to anyone with authorized access, which facilitates collaboration.
Also, tests and test cases (test data) are PeopleTools managed objects, so
they can be included in upgrade projects along with other managed
objects and moved to a new database as part of the upgrade process.
Enhanced Security
Test data is stored in the database, so it has the same level of security as
application data. Data can be accessed and updated only through
PeopleSoft Pure Internet Architecture and web services.
In addition, the PTF client, which is the program that you use to create
and execute tests, is secured by PeopleSoft user IDs and roles.
Maintenance Report to show the changes in the upgrade that effect the tests
Page 4
PeopleSoft Test Framework 8.53 Self Study Guide
PeopleTools Metadata
Page 5
PeopleSoft Test Framework 8.53 Self Study Guide
This method for capturing and executing tests is often called the record
and playback approach to automation.
PTF tests can run processes and reports through Process Scheduler, as
well as queries and DataMover programs.
Page 6
PeopleSoft Test Framework 8.53 Self Study Guide
Note: The PeopleSoft application database where test assets are stored
and the PeopleSoft application that is to be tested are not required to be
on the same database, but Oracle strongly recommends that you use the
same database for both.
When configuring an environment for PTF, there are several parts you
must set or verify:
Page 7
PeopleSoft Test Framework 8.53 Self Study Guide
Note: As a PTF user or administrator, you are not expected to set up and
configure Integration Broker. The information provided in these topics
regarding Integration Broker is presented only for the purpose of
identifying potential problems. If there is any problem with Integration
Broker, you should contact your Integration Broker administrator.
Page 8
PeopleSoft Test Framework 8.53 Self Study Guide
Gateways page
Page 9
PeopleSoft Test Framework 8.53 Self Study Guide
Setting Up Security
The Default User ID for the ANONYMOUS node must have, at a minimum,
a PTF User role. Other acceptable roles are PTF Editor and PTF
Administrator.
You can verify the default user ID for the ANONYMOUS node using the
Node Definitions page.
In the following steps PTFTRN user is assigned the PTF User role to setup
security:
1. Click Main Menu, PeopleTools, Integration Broker,
Integration Setup, Nodes.
2. Search for the Anonymous user.
3. Click the ANONYMOUS link.
4. Use the Node Definitions page to specify information about nodes
(such as authentication and user data).
Notice that the Default User ID for the ANONYMOUS node is
PTFTRN shown in the example below.
Page 10
PeopleSoft Test Framework 8.53 Self Study Guide
5. To ensure that the PTFTRN user has, at minimum, the PTF user
role. Click the PeopleTools, Security, User Profiles, User
Profiles.
6. Search and open the user id PTFTRN from the User Profiles search
page.
7. Use the User Profiles - Roles page to specify the user roles to
which a specified person has access. Note that the PTFTRN user
does have the PTF Administrator role, which includes the PTF User
role's privileges, so it is not necessary in this case to add the PTF
User role. You will add it to review the process for adding a role.
Roles page
Page 11
PeopleSoft Test Framework 8.53 Self Study Guide
Select the Generate HTML for Testing and the Show Connection &
Sys Info check boxes on the Debugging page of the Web Profile
Configuration component to configure the PeopleSoft application for
testing.
Note: You must restart the web server for changes to the web profile to
take effect.
Page 12
PeopleSoft Test Framework 8.53 Self Study Guide
Debugging page
Run the PTF client to create a connection to the PTF environment. Click
the New button if you are creating a new connection. The following
example shows the login screen for a new connection in PTF:
Page 13
PeopleSoft Test Framework 8.53 Self Study Guide
Page 14
PeopleSoft Test Framework 8.53 Self Study Guide
From the PTF window (the PTF window is labeled with the name of the
current PTF environment), you can access the Execution Options dialog
box where you can configure settings for the PeopleSoft applications that
you test with PTF.
You can also access the Execution Options dialog box by clicking the
execution option link in the lower right corner of the PTF application
window. The execution option link is labeled with the name of the default
execution option.
When you click 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. To configure the
execution options:
1. Click @PTF Course DB, Execution Options. The Execution
Options dialog box appears to configure the options you use with
PTF.
Page 15
PeopleSoft Test Framework 8.53 Self Study Guide
Local options settings are used when PTF runs processes or executes
queries.
You use the Local Options window to configure timeouts for processes
launched from a PTF test. The following example shows the Local
Options… dialog box:
Page 16
PeopleSoft Test Framework 8.53 Self Study Guide
Local options are specific to the machine on which the PTF client is
installed. The local options settings are stored in the localoptions.xml
file in the PTF data directory (C:\Documents and
Settings\<User>\Application Data\PeopleSoft\PeopleSoft Test Framework
by default).
Page 17
PeopleSoft Test Framework 8.53 Self Study Guide
Recording a Test
Page 18
PeopleSoft Test Framework 8.53 Self Study Guide
Page 19
PeopleSoft Test Framework 8.53 Self Study Guide
Best Practices
The following best practices are recommended when recording tests:
Record first, and record whenever possible to drive as much
information as possible, including PeopleTools metadata, into the
recorded test. If you need to add a new step to a test, select the
spot in the test where the new step will occur and record the step
at the insertion point.
Assertively record every test step from the test. Even if input fields
are already set to the expected value, you must explicitly enter or
set that value when recording. The recorder only captures actions
that you take against objects during record time. If you skip an
object during recording because it is already set to the desired
value, then the test will ignore it and fail if the default value of the
same object is different during execution.
You may need to repeat some actions to record the desired step.
For instance, if the test instructions say to select a check box but
the check box is already selected, you will need to deselect it first
and then reselect it. After recording is complete, delete the extra
step in your test.
When you record a date field that includes a calendar object, which
enables the user to select a date, you must explicitly enter the date
value in the edit box. Do not use the calendar to select a date.
In this topic, you will record a simple test, deliberately including
some errors that you will clean up in a subsequent topic.
Whenever you run a test, PTF creates an execution log entry. The log is
located in PTF Explorer under the test name, in the log folder specified in
Execution Options dialog box.
After you run a test, PTF automatically displays the log in the Log
Viewer. You can also view a log by opening it from PTF Explorer.
Typically, the Log Viewer includes one high-level entry for each step in the
test. Entries for complex steps appear in collapsible sections that you can
expand to view additional details.
An icon or shaded label appears next to each log entry, indicating the
success state of the associated step.
You can change the appearance of the icons by selecting Log, Change
Log View.
Page 20
PeopleSoft Test Framework 8.53 Self Study Guide
Logs tree
Page 21
PeopleSoft Test Framework 8.53 Self Study Guide
Left Pane
Right Pane
Bottom Pane
When you create or open a test, test case, or shell test, it opens in the
Test Editor.
Page 22
PeopleSoft Test Framework 8.53 Self Study Guide
Often, you will want to run the same test multiple times using different
values in the Value column. Test cases enable you to associate different
sets of data with a test.
You can view and edit both the test and test case in a single unified
window.
You can run a test case by selecting the test case and running the test.
You can also run multiple test cases by calling them from another test or a
shell test.
The test case associated with the original test is named DEFAULT.
Page 23
PeopleSoft Test Framework 8.53 Self Study Guide
Developing Tests
PTF uses a specific structure and test language to describe each step in a
test.
A step is made up of a set of eight fields. The PTF test language focuses
primarily on the following four fields (the exception is the Scroll action,
which also uses Scroll ID):
Type: The type of object being acted upon or the type of action to be
taken.
Action: The action to be taken in relation to the selected Type.
Recognition: Use this field primarily to identify the target object in an
application. Some actions use this field for other purposes as well.
Value: Use this field primarily to supply the value that is being set or
verified in the target application. Some actions use this field for other
purposes as well.
When you record a test, PTF automatically inserts a step for every action
you take and populates the Type, Action, Recognition, and Value
fields. An example of a test case is shown below:
Page 24
PeopleSoft Test Framework 8.53 Self Study Guide
Test case-TRN_09_TEST_DEV_VERIFY
Each type has a set of actions that is associated with it. The Action drop-
down list lists the actions available for a selected type. Examples of an
action include clicking a button or link, setting a particular value in a field,
selecting a check box or combo box, or logging in.
As you develop tests you may need to modify the recorded steps or create
new steps. For example, you can change the Start action to Start_Login
for the Browser type. In some cases, you will need to manually insert
types that cannot be recorded or that are more convenient to insert
manually.
Recognition
The Recognition field is used primarily to identify the specific target object
to be acted upon.
In the example displayed above, the TRN_09_TEST_DEV_VERIFY test,
several objects are included with the Name=<value> format, such as
Page 25
PeopleSoft Test Framework 8.53 Self Study Guide
Value Field
The Value field contains the value to which the specified object is to be set
in the test. When you record the test, PTF identifies the correct format for
the value and includes it in this field; for example, the label on a radio
button option might be Technical but the actual value in the database is T.
You can change a value by selecting it and typing a new value in the field,
but it is generally best practice to re-record whenever possible to ensure
that PTF is picking up the correct values.
Scroll ID
The Scroll ID field is only used for a particular type of action called a Scroll
action.
Seq
The Seq (Sequence) is the order in which the steps occur in the test. This
sequence number can change; for example, if at some future time you
add a step between steps 1 and 2, the new step is given the Seq number
2 and the remaining steps are renumbered accordingly.
The ID is the unique identifier for the row. This number never changes,
even if this or other rows are moved or deleted. Though the numbers in
this example are sequential, they can appear out of order if steps are
added or deleted after the test was initially recorded.
Page 26
PeopleSoft Test Framework 8.53 Self Study Guide
You use reserved words to supply information that is not known until a
test executes. Prefix reserved words with a pound sign (#) and use them
in the Value field of a test to verify a condition, change the value in an
application field, or both.
For example, the #TODAY reserved word sets the Start Date field to the
current date and the expression #TODAY+5 sets the End Date field to
five days from today.
For a complete list, refer to the "Test Language Reference" topic in the
PeopleSoft Test Framework Online Help.
Page 27
PeopleSoft Test Framework 8.53 Self Study Guide
A new line is added to the test. Because you want to use this line to get a
value rather than verify one, you need to make a change to the Action
field.
1. Click the Action cell.
2. Click the Get_Property list item.
To use Get_Property, you need to know:
a. The type of the object.
b. The identifier of the object (Name, Comment, ID, and so on).
c. The name of the object.
d. The property you want to return.
The following example shows by recording a Verify step, the
requirements got captured:
a. The type of the object: Span
b. The identifier of the object: ID
c. The name of the object:
PSU_STUDENT_TBL_STUDENT_ID
Page 28
PeopleSoft Test Framework 8.53 Self Study Guide
Get_Property action
Only the property you want to return is required for which you use the
Message tool.
1. Select Tools, Message. The Message tool appears. The Message
tool shows details about an object in the application, including
name, object type, and value. The following example shows the
Message tool.
Message Tool
Page 29
PeopleSoft Test Framework 8.53 Self Study Guide
Log actions create entries in the execution log. They are useful for
debugging as well as documenting test results.
The Log.Message action writes the text in the Recognition field to the
execution log with a status of Info, replacing the variable with the value
in the variable.
To include a message in the log file:
Page 30
PeopleSoft Test Framework 8.53 Self Study Guide
1. Open a test and insert a new step above a row. Right click the
Seq*. Click the Insert Step, Insert Step Above. A new row is
inserted.
2. Click Type.
3. Select Log from the drop down list.
4. Click Action.
5. Select Message from the drop down list.
6. Click Recognition cell.
7. Enter the message.
8. Save and run the test.
9. The message is displayed in the log file.
To use the #LIST# reserved word to set the value in a list of values, and
verify that the correct value has been set:
1. Select ComboBox from Type drop down list.
2. Select Set_Value from Action drop down list.
3. Enter value in Recognition cell.
4. Use the #LIST# reserved word in the Value field to verify the
values in the Project Role list, and identify the one to which you
want to set it.
Optimizing Tests
PTF includes several features that enable you to create tests that are
efficient and reusable.
Page 31
PeopleSoft Test Framework 8.53 Self Study Guide
Doing so enables you to call the steps repeatedly and also make them
available to other tests that use the same sequence of steps.
You can use the Test.Exec action to call any other test, but you may be
able to manage and identify the relationships between calling and called
tests more easily in the PeopleSoft Test Framework (PTF) Explorer tree if
you use library tests and shell tests.
Library Tests
Page 32
PeopleSoft Test Framework 8.53 Self Study Guide
4. Save the test as a Library test. Notice that the name is modified.
5. Define a test to call the library test:
a. Save another copy of the original test file.
b. Delete the lines included in the library test and save it with a
new name.
c. Add a line to the calling test that will call the library test.
For this line, the type is Test and the action is Exec. The
Recognition field should contain the name of the library test
you want to call.
6. Add few new test cases to the Test.
7. Define a shell script that will call your test cases.
Note: Remember that each test case calls the library test that you
defined. So as the current structure is defined, running the shell
script will call each of the created test cases, and each test case will
in turn call the same library test.
Shell Tests
A shell test is a type of test that you use primarily to call other tests. For
this reason, a shell test only supports these actions:
Test.Exec - calling other tests.
DataMover.Exec - calling data mover scripts.
Query.Exec - running queries.
Variable.Set_Value - manipulating variables.
Page 33
PeopleSoft Test Framework 8.53 Self Study Guide
To create a shell test using the Test.Exec action to call some other tests:
1. Open the test that will call the library test.
2. Use the PTF Test Editor to view and edit information about your
test.
3. Edit the information and click Test Case Save As… to save few
test cases.
4. Click Create, Shell Test. The Shell: NewShellTest! window
displays.
Page 34
PeopleSoft Test Framework 8.53 Self Study Guide
This test checks whether the address is changed when the Same address
as Customer check box is selected. The PeopleCode only executes when
the value of the check box changes; therefore, if the value of the field is
already Y, then the test must select the check box to change it to N and
then select it again to change the value to Y.
Page prompting functions replace explicit navigation in the test and take
the user directly to the component search page by URL manipulation. A
test with the navigation explicitly defined can break when the navigation
changes, even though the application is working fine. Page prompting
avoids this problem.
In the Value field, you must provide an action. Valid values are:
Add.
Add update.
Add correct.
Update.
Update all.
Correction.
If the component has a search page, use one or more Set_Value steps,
as needed, to specify the search key and use the Page.PromptOk step to
close the search page.
Page 35
PeopleSoft Test Framework 8.53 Self Study Guide
You can implement a scroll as a scroll area or a grid. In scroll areas, the
fields appear on the page in a freeform manner. In scroll grids, fields
appear as columns similar to those on a spreadsheet. Individual rows of
data within a scroll or grid are uniquely identified by a set of one or more
fields, or keys.
An example of a scroll area and a scroll grid is shown below:
Scroll Grid
Scroll Area
Page 36
PeopleSoft Test Framework 8.53 Self Study Guide
When you record a test that references a scroll, PTF generates a step
similar to the one shown in the image below:
The step in the above example uses two elements in the Name=
parameter in the Recognition column to reference the Role Name
field:
Page 37
PeopleSoft Test Framework 8.53 Self Study Guide
To avoid the problem of test failure due to the inability to locate scroll
items referenced by absolute locations, you can incorporate scroll
handling into your tests by using dynamic position index variables.
Rows 11, 12, and 13 (by Seq number) in the above example show how
the previous example can be changed so that it will be able to find the
item regardless of its location. We will go over the example step by step.
To create a dynamic position index variable:
1. Create one or more Key_Set steps.
a. Create one Key_Set step for each field in a scroll key.
b. If the key consists of three fields, create three Key_Set
steps and specify key values for each of the three fields.
c. Key_Set requires two parameters in the Recognition
column: Type= and Name=.
You can get these values by recording a step with the PTF
recorder and then manually modifying the recorded step or
by copying the information from the application using the
Message tool and pasting into a step.
d. Specify the field value in the Value column.
e. You can use the PTF Recorder or Message tool to get the
field value as well.
f. The Key_Set step defines the key value, but PTF does not
take an explicit action on the page based on the key until it
executes an Action step.
In the above image, row 11 is an example of a Key_Set step. In
the example, this step locates the row where the Skill field
(PSU_STUDENT_EXP_SKILL) contains PT. Key_Set requires two
parameters in the Recognition column: Type= and Name=.
Page 38
PeopleSoft Test Framework 8.53 Self Study Guide
The following steps describe how to add scroll handling to a test that
enters details on Education and Skills of a user:
Create a new test:
1. Start by changing the Browser.Start action to
Browser.Start_Login in Seq 1 Action cell. The example below
illustrates it:
2. Begin recording the steps in the test. Click the Show Test Recorder
button. The Test Recorder window opens.
Page 39
PeopleSoft Test Framework 8.53 Self Study Guide
4. Complete the steps and stop the recorder. Close the Test Recorder
window.
The test appears. Notice that the test specifies that the
PSU_STUDENT_EXP_PROFICIENCY value in position $3 (the
fourth item in the grid) will be set to L.
5. Click Save and Run. The test runs successfully and the log file is
displayed.
6. Close the log file.
7. Save another test case with changed value for the Student ID and
proficiency level as follows:
Student ID (Seq 7 value field): 2224
Proficiency (Seq 11 value field): H
8. Save and Run the test case.
Notice that the test case fails in the following example:
Page 40
PeopleSoft Test Framework 8.53 Self Study Guide
The failure is due to the fact that PTF could not find the object
referenced for the student with Student ID 2224.
Looking at Student ID 2224's Education and Skills page, we see
that Florence Paul has only three skills listed, and the PeopleTools
skill is listed in position $2 (that is, the third row of the grid).
Because the test explicitly refers to the value in position $3 (the
fourth row in the grid, which does not exist for Student ID 2224),
the test will fail.
To change the test and its test cases so that scroll handling is
accomplished correctly:
1. Remove the row that explicitly references a specific position.
Replace that with rows to perform scroll handling. Right-click and
Delete the Seq 11 row header.
2. Start by adding a Scroll ID to identify that all the actions are to be
performed on the same scroll item.
Click the Seq * Scroll ID cell. Enter following:
Scroll ID: 1
Type: Scroll
Action: Key_Set
Recognition: Type=Text; Name=PSU_STUDENT_EXP_SKILL
Value: PT
3. The next row refers to the same scroll ID. The action will return the
row identified in the Key_Set action; in this example, the row
containing the value PT. Enter following:
Scroll ID: 1
Type: Scroll
Action: Action
Recognition: Ret=&SkillRow
Value: sel
Page 41
PeopleSoft Test Framework 8.53 Self Study Guide
5. Save and Run the test cases. The test cases will run successfully.
Test developers must identify and update every step in each test that is
affected by a change.
Page 42
PeopleSoft Test Framework 8.53 Self Study Guide
One way to identify the effects on tests is to run each test against the new
application and note where the test fails. This manual process is time-
consuming, expensive, and prone to errors. It also fails to identify those
areas in the new application that are not covered by existing tests.
Because PTF test assets are PeopleTools metadata and because PTF tests
incorporate references to PeopleTools metadata—that is, menus,
components, pages, records, and fields—PTF is able to automate the
process of correlating metadata changes with existing tests.
PeopleSoft Test Framework delivers several tools that help test developers
determine the effect of changes. The tools you can use to help in
determining the effect of changes:
Test Maintenance Report.
Test Coverage Report.
You use the Create Test Maintenance Report wizard to go through the
steps needed to generate a Test Maintenance Report. You will learn how
to do this in the next topic.
Another tool that helps test developers to determine the effect of changes
is the Test Coverage Report.
A test coverage report correlates PeopleTools project data with PTF test
metadata to identify components, menus, pages, records, and fields that
are referenced in PTF tests.
• PSPTTSTMAINTRPT
This PTF table contains the data that is used to create the Test
Maintenance report.
• PSPTTSTCOVRGRPT
This PTF table contains the data that is used to create the Test Coverage
report.
Page 43
PeopleSoft Test Framework 8.53 Self Study Guide
The first step in creating a test maintenance report comprises five manual
tasks that you will complete in Application Designer to create a compare
report that PTF uses as a basis for the maintenance report.
Page 44
PeopleSoft Test Framework 8.53 Self Study Guide
Note: For the example in this topic, the tasks for Step 1 only need to be
executed once.
This tracking is done according to user ID. This means that if two users
share the same user ID, the second user may not enter the first page
when accessing the wizard. The wizard will take the second user to where
the previous user left it.
If two different users with different user IDs work on the same project,
the wizard does not track the state for the second user. For instance, if
the first user completed the tasks for Step 1, the second user needs to
check the five tasks on Step 1 to bypass that step.
The step 1 has five tasks:
Task 1: Import only the project definition for the change project.
Open Application Designer and click Tools, Copy Project, From File…
In Copy From File: Select Project window, select PO_PROJ_UPGRADE in
Select Project From the List Below section.
The Copy From File window shows the PO_PROJ_UPGRADE project,
like in the example below. Click Deselect All.
Click Copy.
Page 45
PeopleSoft Test Framework 8.53 Self Study Guide
Page 46
PeopleSoft Test Framework 8.53 Self Study Guide
Page 47
PeopleSoft Test Framework 8.53 Self Study Guide
Step 2 of 4:
To generate the Test Maintenance Report, open the PIA:
1. Click Main Menu, PeopleTools, Lifecycle Tools, Test
Framework, Create Test Maintenance Report.
2. Select all the check boxes in Step 1 of 4.
3. Click Next to open step 2 of 4 where you select a report to
analyze.
4. A project name can appear more than once in the list because
the Compare Output to Table feature stores data by both
project name and compare date and time. The most recent
compare will appear first in the list.
Step 3 of 4:
Use the Create Test Maintenance Report - Step 3 of 4 page to select an
analyzed project for generating your report. Sets of compare data are
listed by project name, the date and time the compare was generated,
and the date and time the analysis was run. The following example shows
step 3 of 4.
Step 4 of 4:
Page 48
PeopleSoft Test Framework 8.53 Self Study Guide
Use the Create Test Maintenance Report - Step 4 of 4 page to specify which
PTF tests to include in the maintenance report, and the report format (PIA or
BI Publisher). Then generate the report. The following example displays step
4 of 4.
Page 49
PeopleSoft Test Framework 8.53 Self Study Guide
1. The Test Name field displays the name of the test that is
affected by a change. A test maintenance report is sorted by
test name. Within each test name grouping, the report items are
sorted by priority according to the values specified on the
Define Analysis Rules page.
2. This column shows the category to which the change belongs, in
this case Medium. The information is gathered from the Define
Analysis Rules page.
3. This column lists the type of definition that was changed.
Definitions include:
Menu.
Component.
Page.
Record.
Field.
4. The Step ID is a unique and unchanging identifier for a step in a
test. Each step has a Step ID and a Sequence Number, but
the Sequence Number, unlike the Step ID, changes when test
steps are added or deleted.
5. The Seq. Nbr (Sequence Number) of a test step reflects the
relative run order position of the step within the test.
6. Status indicates whether, within the test, the step is active or
inactive.
7. Indicates whether the object was:
a. Changed.
b. Added.
c. Deleted.
8. Pre Object Value and Post Object Value indicate what the
value was before and after the change was made.
Page 50
PeopleSoft Test Framework 8.53 Self Study Guide
The above example is the XML report, the same in the browser will have
same fields but arrangement may differ. Following example shows the
same Test Maintenance Report in the PIA.
Notice also that the Market field appears in the PIA report, but not in the
XML report. This is because, for this particular report, the column does not
contain a value. The Market field, when present (for components) includes
the market (for instance, GBL). To the extreme right an additional column
for Description is also present.
Page 51
PeopleSoft Test Framework 8.53 Self Study Guide
You use the Create Test Coverage Report page to select a project for
which to generate a report and specify report options.
PTF generates a coverage report based on a change project. All the
projects in the database are listed, sorted with most recent first. You can
click the column headings to change the sort order.
In this example, you select the project that you want to use to generate
the report.
Page 52
PeopleSoft Test Framework 8.53 Self Study Guide
Page 53
PeopleSoft Test Framework 8.53 Self Study Guide
Report
After you run the Test Coverage Report to determine which areas are not
included in test coverage, you can edit your tests to make sure that these
areas are covered.
The Test Coverage Report that is generated in the above section has
several items listed as having no test coverage. The first of these is the
Page 54
PeopleSoft Test Framework 8.53 Self Study Guide
You can edit the PO_VENDORS test to supply a value for one of the fields
on the Vendors page that was left out of the initial test. You will do this
by recording a new step using the Test Recorder.
Test
1. Start the web client. Navigate to the page from where information
is missing. In this case, the page that displays the Vendor
Information page for Matsui Supply Co. This is where you want to
begin recording your step. You can see in the below example the
Address 2 is missing:
Page 55
PeopleSoft Test Framework 8.53 Self Study Guide
1. Click the Start Recording button. Enter Address 2 and click the
Stop Recording button.
2. Close the recorder and click Yes when prompted to save the
recorded action.
The test reappears with the new row that has the newly recorded
action.
3. Save the test. Next time the test coverage report is run, the
Address 2 field will not be included in the list of fields that have no
test coverage.
Page 56