PeopleSoft Test Framework automates Application System Testing for Functional Users. It reduces the cost of Test Development with simple “Record and Playback” feature, requires no Coding and all the Tests and Test Cases are put together in a easy to use GUI environment
3. 3
Introduction
Target readers
PeopleSoft Functional and Technical Users
Keywords
PeopleSoft Test Framework, Functional Testing
Introduction
PeopleSoft Test Framework automates Application System Testing for Functional Users.
It reduces the cost of Test Development with simple “Record and Playback” feature, requires no Coding and all the Tests and
Test Cases are put together in a easy to use GUI environment.
On a high level, the presentation covers the below topics
• Configuration & Setup of PTF
• Walkthrough of the PTF
• Best Practices Involved
• Provide Illustrative Examples for Quick Reference
Reference(s):
1.PeopleBook : PeopleSoft Test Framework
http://docs.oracle.com/cd/E18377_01/psft/acrobat/pt851tptf-b0810.pdf
8. Integration Broker – Node Configuration
• Note: Here we have only one database connection to the web server.
Else, we have to specify the Node Name as shown below.
8
14. Installing PTF Client
• Locate the setup.exe in the PS_HOME>setupPsTestFramework and Install the same.
• Check for Microsoft .NET Framework and Internet Explorer Security Settings
• Common Error while installing PTF within Infosys is given below.
• Solution :
• 1)Create the corresponding folders as mentioned in the path
• 2)Copy the Configuration XML files provided in the attachments
• 3)Try logging in again and edit as per your settings
14
16. Log into PTF
Just an alias name, preferably the name of the database
Server Name and Secure Port number
Integration Broker Node ID.
Leave BLANK to refer to the default Node ID.
New/Previous – To browse through the list of
saved connections
16
17. Local Options
• Proceed with the Default options
• Consider changing the Output Folder and format
17
18. Execution Options
• Update the Execution Options
• Fill in the URL Details, Username and Password
• Select the default Process Server and specify Date Format
• Note: URL need not be HTTPS
• Update the PSHome Tools Path and other details in the PeopleTools tab
• You can use Insert to connect and configure to multiple Instances
18
19. PeopleSoft Test Framework Client
Connection Alias Name
Database Name
User ID
myFolder : Store tests that you
do not want to share with others
Folder
Tests
19
20. Tests , Test Cases and Logs
Logs : Displays the Status of the previous
runs with the help of flags
Test Cases: DEFAULT is the base Test Case
that is automatically created.
We can create Multiple Test Cases by
associating different sets of data to a test
• PTF Explorer provides a Tree Structure View
• Open ,Create, Delete, Copy and Move Folders and Test
Assets
20
21. Sample Test Case
Record the Test Case
Run Existing Test Case
Various Debug Options :
Break Point, Step by Step Processing
21
22. Getting Started
Click on the Home Icon to Activate the Internet Browser
And Open the PeopleSoft Login Page
Click on the IExplorer Icon
Drag the IExplorer Icon on to the Internet Explorer Browser
Click on the Record Icon
Click on the Stop Recording Icon
Recording has been completed . Now, go back to PTF Explorer
And identify and review the Individual Steps
22
23. Test Steps
• Every User Action will be captured as a Test Step
• Example : A User Entering the UserID Field will get Translated to a Test Case as a Step
23
24. Test Object Properties
Drag and Point the Icon to display the Object Properties
• Make Use of the Object Properties to further refine the Test Case
24
30. PTF Best Practices
• Record First
• Try to Record Each and Every Step.
• Even if some of the values are defaulting on the page, Blank them out and re-enter the value
• Run through the Test Case once it is completed and Activate or Inactivate any Step if required to suit your scenario.
• Use the Debugging Mode
• Also, you can start and stop recording at any step that you require instead of manually editing or creating a Test Step.
• Document tests
• Use proper Naming Convention
• No Duplicate Test Case names
• Create Folders by Module or Functional Classification
• Please fill in Test description, Test properties ,Test case description ,Test case properties
• Use Log Message wherever appropriate
30
31. PTF Best Practices . . . ( Contd.)
• Clean up tests
• Immediately after Recording, Review the Test and Perform Corrective Action by removing unnecessary clicks, Incorrect
Data Entry etc.
• Use execution options
• Logon Information can be Stored under Execution Option.
• Also, If you want to avoid saving or running processes, use the Skip PageSave/RunRequest functionality
• Ex: Avoid new Vouchers being created each time you run the Test Case
• Use page prompting
• Avoid unnecessary steps for navigation
• Navigate directly to the Page . Type = Page, Action = Prompt/ PromptOK
31
32. PTF Best Practices . . . ( Contd.)
• Use of Process Object Type
• Use Process.Run step to directly run a process
• Make Tests Dynamic
• Logical Variables
• Conditional logic
• Scroll handling
• Reserved Words like #TODAY
• Finally – Some Caution
• Generally, some of the input fields will have some values which are already defaulted. However, we must explicitly
enter or set that value when using the recording feature.
• While recording a date field that has a calendar object, you must enter the date explicitly. Also, you must not use the
calendar to select a date. Hint: Use #TODAY if the field has to be dynamic.
• Scroll Handling requires a bit of programmatic approach and additional effort
32
34. When to Use PTF
• Flexible and Useful for New Implementations / Upgrades / Bundle Applications
• Less Dependency on Functional Resources
• Limited Time and Highly Customized Application
• Accelerates Testing when it has to be performed in Multiple Environments – DEV, QA, CRP1, CRP2, UAT
• Simplifies Impact Analysis when regularly applying Patches / Fixes
• Supports Data Mover and Query
Difference in Approach – Savings in Cost and Time
34
35. PTF Limitations
• Not Designed for Load / Performance Testing
• Not Designed for Running Concurrent Tests and simulate Multi User Scenarios
• Works with Internet Explorer Only
• Works only with PeopleSoft Objects.
• Cannot work with Flash/Flex, External Objects, data in HTML Regions, etc.
• Cannot validate images or relative positioning of data and online objects.
• Cannot simulate drag and drop
35
36. Calling Tests
The Test that we are calling should be a Library Test
Test Name in Recognition and Test Case Name in Value
36