PeopleSoft Test Framework

1. PeopleSoft Test Framework Presented by : Eddie Urenda Head of Accelerator & Technology Productization

2. Agenda Hexaware Overview: Key Facts PTF Overview Creating and Executing Tests Best Practices for Optimizing Tests New Features in PTF 8.53 beta

3. PeopleSoft Test Framework Overview

4. PeopleSoft Test Framework • Record and Playback tool • Automates Functional testing within PeopleSoft Application • More tests - Greater Accuracy- Shorter time • Stored in Database as App Designer Objects • Included in PT 8.51 & above

5. Record and Playback • PTF works by replicating the actions of a single user executing functional tests against the PeopleSoft browser-based application • Users can record manual test procedures and save them within the framework • Users can execute those tests against the application to verify whether the application still behaves as expected

6. PeopleTools Metadata • When PTF records a test, it recognizes the metadata, the actual name of a field rather than the position of that field on a page • If the field is moved in a subsequent revision, PTF is still able to locate it when the test is executed

7. Developing Tests Robust Test Development Platform PTF EDITOR PTF EXPLORER

8. Interface with Other PeopleTools Process Scheduler PTF P S Query DataMover • PTF tests can run processes and reports through Process Scheduler, as well as queries and Data Mover programs

9. Where PTF is Used

10. Typical Usage in PS Projects • PTF can be used in • New Implementation projects • Limited / No existing testing documentation • Limited functional resources to participate in testing • Highly customized environment • Significant ongoing development projects • Routinely deploying patches and fixes • Savings on cost to buy a separate test automation software

11. Features Test Assets Are Stored in the Database • As test assets are stored in the database they are readily accessible to anyone with authorized access • Tests and test cases (test data) are PeopleTools managed objects • They can be included in upgrade projects along with other managed objects and moved to a new database as part of the upgrade process.

12. Features Facilitate Maintenance Due to Upgrades • The PTF test maintenance process drastically reduces the expense and risk in testing upgrades • Provides reports that tell you what changes in the upgrade affect which tests in your test library.

13. Integrated Maintenance Reports A Test Maintenance Report shows which objects were changed in an upgrade and which tests are affected by each change. Navigation Create Test Maintenance Report - Manual Tasks Select PeopleTools, Lifecycle Tools, Test Framework, Create Maintenance Reports

14. Benefits of PTF • Automated testing • Consistent across environments • Functional testing • Speeds testing • Reduces testing time and resources • Easy to migrate

15. Creating and Executing Test Cases

16. PTF PeopleSoft Test Framework

17. PTF Architecture

18. Configuring PTF Clients Creating a Connection to a PTF Environment Selecting a PTF Environment

19. Execution Options Navigation Select PTF menu, Execution Options.

20. Local Options Navigation Select PTF menu, Local Options.

21. Creating Tests Using PeopleSoft Test Framework Explorer

22. Recording Tests Launching the Test Recorder Recording a Test To record a test: 1. Open a test. 2. Launch the test recorder. 3. Hook a browser. 4. Start recording. 5. Perform the test steps in the PeopleSoft application. 6. Stop recording. 7. Close the rest recorder. 8. Save the test. Test Recorder Toolbar

23. Executing Tests & Reviewing Logs Executing a Test 1. With a test open in PTF, select Test, Run. 2. PTF opens the PeopleSoft application specified in Execution Options and executes the test steps. 3. After the test executes, PTF opens the test log in the Log Viewer. Using the Log Viewer

24. Reviewing Execution Logs Logs Folder Log Icons

25. Cleaning Up Tests • Removing Unneeded Steps • When you record a test you often record unneeded steps. • Correcting Typos • To change a value, click in the Value column and retype or edit the text. • Modifying the steps • Modifying the steps to meet the actual requirement. • Adding Steps Manually • Some steps which cannot be recorded can be added by giving insert step.

26. Best Practices

27. Page Prompting & Process Run • Page Prompting • Testers should record all PTF tests using Page Prompting by default, • PTF administrator can update this setting at the database level in PIA at PeopleTools > Lifecycle Tools > Test Framework > Define Configuration Options. • Process Run • Use Process Run Feature to run a process in process scheduler.

28. Scroll handling, Libraries & Using Test Cases • Scroll handling • PTF tests should use scroll handling whenever test data residing in a scroll or grid could change between executions • Libraries • Whenever testers find that they are coding the same sequence of PTF steps multiple times, they should try to isolate that sequence of steps in a library • Library is a special type of PTF test that can then be called by another test • Parameter feature provides the user with flexibility in passing values to the library • Using Test Cases • Testers should clone a unique test case specific to the functionality being entered from the default test case using the test case save as feature

29. Comments fields Comments fields PTF supports comments at the Test, Test Case, and Test Step levels. Comments must be used to clearly document the functional testware being automated

30. Types Of Variables • System Variables, Global Variables, and Reserved Words • Use these when the value of an object being set or verified is not known prior to run time • Document the usage in the appropriate comment field (usually best at the test step level) • Persistent Variables • Testers should use persistent variables when they need a test to refer to the value of a global variable that was set during a previous execution of PTF • Persistent variables are saved to the PTF database rather than in temporary computer memory • .

31. Log Messages & Conditional Logic Log Messages Use of log messages (Log.Fail, Log.Message, Log.Pass, etc.) is strongly recommended to help users executing PTF tests to interpret execution log results. Conditional and Looping Logic Use PTF’s conditional steps (Conditional.If_Then, .Else, and .End_If) and looping steps (Loop.Do, .For, and .While) to design custom logic not provided by other delivered steps and features.

32. PTF Tool Limitations • PTF Limitations: • Unable to do mass testing • Manually updating data for each test case in PTF environment • Running Multiple iterations of test data for one test case • PTF Sequencer Tool has been designed to overcome three major limitations of PTF • To do mass testing through Process Scheduler • To update the test data in PTF tables through a spreadsheet. • Running multiple iterations of test data for one test case

33. Hexaware - PTF Sequencer Tool Technical Process Fetch data from Excel file to Staging table by CI Passing required Parameter to run the PTF Data moved from Staging table to state record Update the PTF Table data by state record value • Benefits: • Automatically updates the data for the required test case from the flat file • Automatically run the updated test case by calling PTF executable file through • Application Engine Program • User can activate the required sequence test and run the same in the Shell Test program • No need to open the PTF environment to change the data or run the test case, it will automatically run through PIA

34. New Features added in PTF 8.53 beta • Syntax Check • Process Run Recognition in recorder settings • HTML getcellindex & getcellvalue in the recorder toolbar • Prompt for values in the recognition field for complex action types in thePTF editor • All strings are recognized only if enclosed within quotes

35. Time for Questions

36. Thank Yousupport@hexaware.com