1. Prepared by: Session ID: Using PeopleSoft Test Framework During Development Matt Shimel Principal Applications Systems Analyst/Developer University of Arizona shimel@email.arizona.edu 103080

2. Your Presenter 1998: “Business Analyst” on legacy system 2004: Developer on legacy system 2008: PeopleSoft HCM Developer 2014: Technical Lead - PeopleSoft Enterprise Learning Management (ELM) Matt Shimel Principal Applications Systems Developer/Analyst University of Arizona shimel@email.arizona.edu

3. University of Arizona Public Land Grant Institution established in 1885 Total Students: 42,200 Academic Programs: 364 Employee FTE: 12,480 PeopleSoft Products: Campus Solutions 9.0 Human Capital Management 9.2 Enterprise Learning Management 9.2 PeopleTools 8.53.15 > PeopleTools 8.55.04

4. Agenda PeopleSoft Test Framework (PTF) Overview PTF Development Cycle Examples/Demonstrations PTF Tips & Tricks

5. PeopleSoft Test Framework (PTF) Overview

6. PTF Overview – What It Is Record/playback client tool Designed primarily for functional testing Stores test assets in database Originally an internal Oracle tool, now included with PeopleSoft license

7. PTF Overview – What It Isn’t PTF works well for testing fields, records, pages and components, but: Not useful for load/performance testing Cannot validate images Cannot replicate drag and drop actions Will not work with third-party or external applications

8. PTF Overview – Benefits Aspects of PTF that will help the developer quickly create test scripts: Time savings Learning curve Documentation Designed to work with PeopleSoft

9. PTF Overview – Drawbacks Factors that will decrease productivity: Additional overhead Learning curve Functional unfamiliarity

10. PTF Development Cycle

11. Map out test Find/create a general test case Record test in PIA Optimize test in PTF client

12. PTF Development Cycle Add test case(s) based on requirement from specification document Develop solution for that requirement Run PTF test with that test case Repeat with next requirement

13. Examples/Demonstrations

14. Two Examples: Preferred Name Change “Reports To” Sync

15. Preferred Name Change: Overview Modification to add a custom component to Employee Self Service to allow employee to add/modify their preferred name

16. Preferred Name Change: Requirements Allow user to add Preferred Name (Name Type “PRF”) to Names table through new custom component in Employee Self Service Pre-populate name fields with Preferred Name if it already exists. If not, use Primary Name Allow User to enter freeform Preferred Name: What if field(s) blank? What if special characters are used? What if unconventional/offensive, etc? Sync Preferred Name to Campus Solutions and ELM

17. Preferred Name Change: PTF Test Flow Log into PIA Verify Results Navigate to Component Perform Action Set Variables

18. Preferred Name Change: Test Script

19. Preferred Name Change: Demo

20. “Reports To” Sync: Overview Initially disabled, we enabled part of this Position Management functionality so that Job rows were created when the “Reports To” fields was updated on a Position: Partially go back to “Vanilla” New Job row inserted when change made on Position Allow Managers in ELM to see and manage learning for those that report to them

21. “Reports To” Sync: Requirements Long list of requirements: Remove part of modification to allow a Job row to be inserted for the corresponding incumbent when a position is modified: Non-pooled Position (Max Head Count =1) Action Reason is UPD or SUP Reports To value is changed Modified through delivered Position Data component, or Modified through custom Approval Workflow Engine (AWE) Manager Self-Service transaction

22. “Reports To” Sync: PTF Test #1 Flow Shell Test Set Execution Options Set Variables Call Position Data Insert Test Call Job Data Verification Test Position Data Insert Test Add new row Verify values Job Data Verification Test Retrieve Job row Verify values

23. “Reports To” Sync: PTF Test #1 Position Data Shell Test:

24. “Reports To” Sync: PTF Test #1 Position Data Row Insert:

25. “Reports To” Sync: PTF Test #1 Job Data Verification Test:

26. “Reports To” Sync: PTF Test #1 Demo

27. “Reports To” Sync: AWE Flow Submitter HCM Final Approval Approvals

28. “Reports To” Sync: PTF Test #2 Flow Shell Test Set Execution Options Set Variables Call AWE Submission Test Set Execution Options Call AWE Approval Test(s) Set Execution Options Call AWE Final Approval Test Call Job Data Verification Test AWE Submission Test Job Data Verification Test Retrieve Job row Verify values AWE Approval Test(s) AWE Final Approval Test

29. “Reports To” Sync: PTF Test #2 AWE Position Management Shell Test:

30. “Reports To” Sync: PTF Test #2 AWE Submission Test:

31. “Reports To” Sync: PTF Test #2 AWE Approval Test:

32. “Reports To” Sync: PTF Test #2 Job Data Verification Test:

33. “Reports To” Sync: PTF Test #2 Demo

34. PTF Tips & Tricks

35. Development Best Practices: Make test scripts as generic/simple as possible Use shell tests and test cases to extend functionality and value of scripts Shell Test Test 1 Test 2 Test Cases

36. PTF Tips & Tricks More Development Best Practices: Clone actual users and use with Execution Options: Use PTF “Shortcut” Types/Actions: Page/Prompt Process/Run

37. PTF Tips & Tricks Syntax Checking: Context Sensitive Help: On Demand Syntax Check:

38. PTF Tips & Tricks Debugging:

39. PTF Tips & Tricks Message Tool: Drag and Drop to get more information Alternative to App Designer for Business Analysts No need to record PTF test to use

40. Questions Matt Shimel Principal Applications Systems Developer/Analyst University of Arizona shimel@email.arizona.edu

41. Session ID: Please complete the session evaluation 103080