Prepared by:

Session ID:

PTF for the PS Admin

Kyle BensonPeopleSoft AdministratorHennepin County@kbenson @psa_io

A PTF Overview for the PeopleSoft Administrator

100470

Presenter

• Kyle Benson

• PeopleSoft for 10 years

• Developer > Sys Admin > Jr. DBA > DevOps Dude > ?

• Help run psadmin.io and PeopleSoft Administrator Podcast

@psa_io

Hennepin County

• Largest county in MN

• Minneapolis county seat

• ~8,000 employees

• Budget $1.9 billion

• PeopleSoft

• PeopleTools 8.54 > 8.55 in progress

• FSCM, HCM, ELM 9.2, Interaction Hub Image 4 in progress

@psa_io

Agenda

• PTF Technical Overview

• Tips for Deploying and Maintaining PTF

• Going the extra mile

• Put your PTF on Phire

• PTF pie in the sky

@psa_io

PTF Technical Overview

@psa_io

PTF Technical Overview

@psa_io

Selenium

PTF Technical Overview

@psa_io

PTF Technical Overview

• Set up Integration Broker

• Set up Security

• Set up Web Profile

• Define PTF Configuration Options

@psa_io

PTF Technical Overview - IB

• Normal Gateway setup

• Include PTF asset database node

• ANONYMOUS node default user needs PTF User role

• Make sure all PTTST* service operations are active and working.

@psa_io

PTF Technical Overview - Security

@psa_io

PTF Technical Overview – Web Profile

@psa_io

PTF Technical Overview - Config

@psa_io

@psa_io

Deploying - Client

• Don’t use primary desktops for Client install

• VM with Terminal Services

• VDI

• Dedicated testing machines

@psa_io

Deploying - Client

• Install name changed in 8.55.08

• PS_HOME/setup/PsTestFramework/installTestFramework.exe

• Install from command line

cd %PS_HOME%\setup\PsTestFramework.

installTestFramework.exe /s /f1"%PS_HOME%\setup\PsTestFramework\response-file.txt”

• Uninstall from command line

installTestFramework.exe /s /f1"%PS_HOME%\setup\PsTestFramework\uninstall-silent-response.txt"

• Uninstall and Install a new instance of PTF

setup.bat

@psa_io

Deploying - Client

• PIA address needs to be in browser trusted zone

@psa_io

Deploying - SSL

• Client will always try and use `https`

• To turn off validation, activate Service Operation `PTTST_CONFIG_NO_SSL`

• Issues behind load balancer and SSL termination

• Issues in lower environments with no SSL

@psa_io

Deploying - SSL

• Manually set all `PTTST_*` service operations

• Create an ACM Plugin?

@psa_io

Deploying – Dedicated DB

• Use a dedicated database to store PTF assets

• Phire

• SYS DB Interaction Hub

• We are using a single DB

• PTF development life cycle is managed via folders

• Use the same database for Performance and Usage monitor data

• We use a centralized development IB gateway

@psa_io

Maintaining - Migration

• For the most part, not needed

• App Designer/Phire can migrate some assets

• Tests

• Test Cases

• DMS or ADS needed for others

• Execution Options

• Logs

@psa_io

Maintaining - Migration

Manage AD projects from PTF Client

• Create new Application Designer projects.

• Open existing Application Designer projects.

• Insert tests into Application Designer projects.

• Remove tests from Application Designer projects.

• Set the upgrade action type within Application Designer projects.

@psa_io

Maintaining - App Maintenance

• Tests will need reworking

• Use Maintenance Report to identify post applying Change Packages

• Upload test data into Test Repository on PUM Dashboard

@psa_io

Maintaining – Test Repository

• It is not necessary to use PTF in order to use the test repository.

• Test impact is calculated based on components.

• PTF Tests

• CA identifies all Components associated with Test

• Components

• Create Projects that contain Components. “Test name” is the

Project name.

@psa_io

Maintaining - Tools Maintenance

• If using dedicated DB, need to match tools release

• Start with this environment when patching, upgrading

• Don’t forget about IB gateway you are using, as well.

• Test assets will be upgraded via Client automatically

@psa_io

@psa_io

Extra - Usage Monitor

• By default, PTF only tracks PT object usage of type:

• Menu, Component, Page, Record, Field

• For PeopleCode, etc you will need Usage Monitor

@psa_io

Extra - Usage Monitor

• Start recording• In the browser, select Usage Monitoring • The Test Data page appears

• Enter Test Name and Test Case.• Click Start test.• Record the test steps.• When finished, return to the Usage Monitoring page and select Stop Test.• In the PTF Recorder click the Stop Recording icon.

Note: Your PTF environment and the application you are testing must be on the same databaseNote: The manual steps of starting and stopping the Usage Monitor are included here during the recording process to capture them in the PTF test. PTF does not have to be in record mode to generate Usage Monitor data.

@psa_io

Extra - Usage Monitor

@psa_io

Extra - Usage Monitor

• Can we add Usage Monitor capturing after the fact?

• My idea

• Record the Usage Monitor “Start Test” and “Stop Test” tasks as a Library

Test

• Insert these into existing Tests and pass the Test and Test Case names

as variables.

@psa_io

Extra - Batch Runs

• Run Test from command line

@psa_io

PsTestFw -CS=rtdc79637vmc:8643 -CNO=PT_LOCAL -PS=ProxyServer:2345 -

PU=mydomain\username -PP=pwd123 -CO=VP1 -CP=VP1 -TST=TEST_CMD_LINE -

TC=DEFAULT -PFX=Prefix -EXO=QE851_No_Folder -LOG=my_run_log

Extra - Batch Runs

• Can we schedule a batch of Tests to be run, versus manually running them?

• Create a script to accept a list of tests, then kick off individually

• Use Scheduled Tasks to run scripts

https://github.com/psadmin-io/PSPsftTestFramework

https://github.com/psadmin-io/PSPsftTestFramework/tree/master/Examples

@psa_io

Extra - Reports

• Custom Reports

• Upload data into PUM

@psa_io

Extra – Repeatable Tests

• Query Based Tests

• Manually done 8.55 and below

• Delivered method in 8.56

• “Oracle” Method

• A “staged” testing environment to refresh from

• Create copy of DB > Run PTF Scripts > Review > Destroy DB

• Snapshot(Dataguard) Method

• Standby DB > Snapshot > Run PTF Scripts > Review > Revert to Physical

@psa_io

@psa_io

PTF on Phire

• Use Phire as your PTF database

• Put Phire node in your Gateway

• Connect to Phire at PTF Client login

• All PTF assets will be stored in Phire

• Don’t worry about refreshes

• Leverage Phire version control for assets

@psa_io

PTF on Phire

• Create coverage report based off of Change Requests

• Delivered coverage report compares against Project items

• Clone delivered and replace Project items with CR items

• Need a view to cross walk Project item type with CR item type

• Would work best if assets in Phire, but possible with Phire DB links?

@psa_io

PTF on Phire

• Create Test Plan tab on CR component

@psa_io

Execute Test Plan

@psa_io

PTF pie in the sky

Use Phire as PTF Environment

Fully configure Usage Monitor

Create “Usage Monitor” Library Test, add to all Tests

Implement PTF PowerShell module

Setup Scheduled and Adhoc Batch runs

Create Phire CR coverage report

Create Test Plan tab on Phire CRs

Show coverage

Execute Adhoc Batch runs

@psa_io

Session ID:Please complete the session evaluation

100470

@psa_io