Presented by: State of Indiana, Office of Information Technology  

Session ID 101560, Presented at COLLABORATE17

This is a follow-up to my presentation from Collaborate 2015. In late 2013, State of Indiana chose to pursue PTF as an automated testing solution. The initial goal was to use automation for improving our cumbersome End-To-End (E2E) testing process.  We contracted development of PTF tests for all Financials modules. Unfortunately, resource shortages kept the planned debut of our newly created PTF tests from being implemented during our 2015 Oracle database conversion testing. Then more misfortune when our PeopleTools upgrade disabled our unwieldy collection of PTF tests and our burgeoning PTF skillset was stifled in repairing them. 2016 brought a reboot of our Oracle conversion project and also allowed us time to master the PTF tool and to repair our tests. In Q4 2016, our PTF tests will be going head-to-head against a nearly identical manual testing of our E2E process. I will describe our path to \”mastery\” of PTF and compare/contrast PTF’s results to our manual E2E testing process.

• At the time of my Collaborate 15 presentation, our PTF tests had been created but not yet used in a testing cycle. Attendees from my talk asked me to return with updates on how well our strategy succeeds.
• As first-timers utilizing the investment we made in PTF development – cite pitfalls, learning trials, and the correct/incorrect assumptions we made going into our first PTF venture.  Discuss how our staff development around PTF support has evolved.
• Did PTF automated E2E really ease resources during integration testing; provide a more accurate testing execution; and enable us to utilize our valuable E2E testing process in new ways such as first-pass analysis and regression testing?