Utilizing PeopleSoft PeopleTools' Test Framework to Automate Testing and Lower Costs

2. Utilizing PeopleSoft PeopleTools' Test Framework to Automate Testing and Lower Costs Doug RedingerSenior QA Manager

3. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

4. Program Agenda • Incorporating automation into an organization • Skill / aptitude profile of automation resources • Types and categories of tests that automate well • Software considerations • Preparing for a PTF implementation

5. Incorporating automation into an organization • Defining automation strategy at the organization level • Should all testers spend X percent of their time developing automating orshould X percent of testers spend all of their time developing automating? • What percent of test time / effort should be spent on automation development?

6. Incorporating automation into an organization • PeopleSoft applications testing • Automation team works full time on automation development, maintenance, and execution • Automation engineers represent approx. 25% of applications testers

7. Incorporating automation into an organization • Benefits of the central approach • Less automation “spoilage” • Adherence to best practices and common standards • Results in cost / effort savings by focusing on building automation that is: • Repeatable • Maintainable • Leverages functional libraries and commonly used tests

8. Incorporating automation into an organization • Anecdotal customer experience • Success with automation projects focused on specific products rather than across all products

9. Skill / aptitude profile of theAutomation engineer • Defining automation strategy at the individual resource level • Technical aptitude? • Programming experience? • Who makes a better automation developer, a functional tester or an applications developer?

10. Skill / aptitude profile of the Automation engineer • PeopleSoft applications testing • Opportunity to automate full time attracted individuals with technical abilities and interests from the broader population of functional testers • Programming education or experience • Macro guys and Excel gurus • Interest in automation development (good opportunity for resources who were looking for a change from functional testing) • Not a hobby or holiday from primary role

11. Skill / aptitude profile of theAutomation engineer • The personnel decision • Consider the scenario where one person is your best functional and technical resource • Because false defects are expensive and irritating; troubleshooting automation errors is a key skill, e.g.: • The application is broken • Test instructions are out of date or incorrect • Automation tool or script is out of date or behaving unexpectedly

12. Types / categories of tests that automate well • Identifying tests that yield the greatest automation ROI • Focus on functional tests (not performance, accessibility, etc.) • Target mature products and features • Emphasize frequency of execution over “priority” • Target repeatable tests • Avoid run-away development time • Key an eye on total lines of code

13. Preparing for a PTF implementation • Identifying tests that yield the greatest automation ROI • Design – and document – a test before automating it!

14. Preparing for a PTF implementation Factors in calculating Automation ROI • Development • Maintenance • Execution

15. Software Considerations • Client specifications (generally aligns with PeopleTools end-user specs • Does require an install from \SETUP • Windows / Internet explorer • .NET (4.0 for PTF 8.54) • Server specifications • Integration Broker running • Users require IB “listener” URL to log in via PTF client

16. Preparing for a PTF implementation • Study generally-accepted best practices of automation • Keep your desktop simple • Adopt consistent folder and test naming conventions • Record rather than code from scratch • Clean up tests • Document your tests

17. Preparing for a PTF implementation • Get acquainted with PIA-centric features of PTF / • Challenge common misconceptions about limits of automation • Use execution options • Use page prompting • Use scroll handling • Use message recognition • Use the Process.Run step

18. PeopleTools Sessions of Interest Tuesday

19. PeopleTools Sessions of Interest Wednesday

20. PeopleTools Sessions of Interest Thursday

21. For More Information The PeopleSoft Information Portal • All your PeopleSoft information and training resources in one convenient location. www.peoplesoft92.com or www.peoplesoftinfo.com

24. PTF and Hexaware Solutions:An End-to-End PS Testing Solution Eddie Urenda Head of Accelerator and Technology Productization Quality Assurance and Testing Services (QATS)

25. Agenda • How Does A PTF Implementation Work? • What do we do first? Next? • How much is automation going to cost / save us ? • Does testing work on copies of production? • Does PTF work for automating batch products? • Best Practices around Testing FAQs • Hexaware-specific offerings • HexaCompare – Easing Data Migration Testing • Performance Testing: HexaJAWS Overview • Hexaware PS Testing Metrics Framework

26. What do we do first? • Good automation starts with good test instructions, but customers are often unable to point to strong test ware. Base of the automation testing is the Manual Test cases, covering all the functionality of the applications. • All test cases related to critical processes are documented properly. • Reusable functional test case / test steps to be identified that will be created as reusable modules. • All test steps need to be documented properly in the test cases along with expected results • Documentation will help scope the automation development process • Hexaware Solution • Model test script content allows customers any degree of help and flexibility they need to make their test repository well-documented, from emulating best documentation practices all the way to borrowing entire test scenarios • Test Case Design & Selection + PTF + Model Test Scripts = Greater Test Coverage and diminished risks in production

27. Sample Test Case Document

28. What do we do next? • Automate a complete End–to-End business process • Identify the critical Business Processes [BP] to cover the testing, based on • Impact Analysis • BPs identified by Hexaware based on vast previous experience • PTAK will provide critical BPs across modules. • Hexaware Value-Add: • Rich set of Functional E2E PTF Automated Script Repository available across all PS Modules. • PTF Maintenance / Coverage Report and above PTF Repo. will ease identify customization. • PTF Customization will help in executing multiple iterations of data for same test script and effective test data management. • Some of the Sample BPs flow were explained in the next slides… • *PTAK – PeopleSoft Test Automation Kit (Rich set of functional End 2 End manual scripts)

29. Sample E2E Scenario

30. Sample E2E Scenario – HCM

31. Sample E2E Scenario – Payroll

32. Best Practices for Optimizing PTF Tests Hexaware can provide sample scripts that not only automate the manual steps but that also cover all the PIA-centric best practices recommended by Oracle: • Page Prompting • Process Run • Scroll handling • Libraries • Log Messages • Conditional and Looping Logic

33. How much is automation going to Cost / Save? Sample ROI Calculation is explained below for automating 2000 Manual Test Cases and comparing the same across Manual, Traditional Automation and PTF Approach. Hexaware' s experience partnering with Oracle on Rel. 9.2 gives practical experience to scope and analyze PTF Script Design / Development and ROI Estimates.

34. Does testing work on copies of production? • Yes! - PTF supports dynamic constructs and useful bulk data validation tools like Query, Process Run, Scroll Handling • Best Practices discussed earlier will help make tests dynamic with common code and libraries • E2E PTF Scripts Repo. available that helps to quickly retrofit as per client customization • Hexaware’ s PTF Customization augments native test data functionality.

35. Does PTF work for automating batch products? • Yes - PTF supports batch products through Process, Run and Query • Hexaware experience with PIA centric aspects of PTF and previous experience on Tax Updates, Full Upgrades and New Implementations, which involves high volume of Batch Processing.

36. When do we know we're done? • PTF test data is meta data, including logs.   • This info can be queried and exported like any other data • Hexaware delivered Metrics will help in consolidating the test performance • Test Results can be exported in XML format

37. Hexaware: Preferred PTF Implementation Partner Hexaware has been a Co-Development Partner and has invested extensively in developing test automation scripts around PeopleSoft 9.2 Application Suite leveraging PTF (PeopleSoft Testing Framework). These scripts are exclusively available only through Hexaware and will help customers cut down the testing time significantly during any PeopleSoft 9.2 upgrade engagement. Oracle September 2013

38. End-to-End Testing for PS Quality Lifecycle

39. Q & A-Doug Redinger – Oracle -Balaji D. V. – Hexaware QATS – PS-Eddie Urenda – Hexaware QATS

40. Thank You info@hexaware.com