PTF FasTest Test Strategy


Reality has changed in the long term management of your PeopleSoft investment. The last major upgrade you’re likely to undergo is the transition to application version 9.2; from their you can say goodbye to the monolithic transitions from one version to another. The new reality is incremental change packages made available from Oracle. Colloquially referred to as PUM, these updates come in manageable increments while also allowing the enterprise flexibility in adoption, modification, and acceptance time frames. Now, let us guide you through this new reality and the options and choices available to you while utilizing the PeopleSoft Update Manager.

1. PeopleSoft Update Manager (PUM)

1.1 PUM Overview:

PeopleSoft Update Manager (PUM) is a lifecycle management process that is used with the PeopleSoft Update Manager application, which runs on the PeopleSoft Image database. The PeopleSoft Image is delivered via Oracle VirtualBox virtual machines containing PeopleSoft product updates, fixes and new features for customers to consume as per their need. A paid Oracle maintenance agreement is required to access and use PUM images.

The PUM Schedule is published by Oracle describing the approximate release date of PUM images for each PeopleSoft application pillar, such as FSCM. The PUM Image, released periodically according to the PUM schedule posted on the PeopleSoft Update Manager Home Page, is the master source environment from which you will pull the updated objects, create a custom change package, and apply updates to your environment.

1.2 What’s in PUM

The PUM Image for your application is cumulative so you will download the most current PeopleSoft Image and get all of the updates that you need. Each new PUM image contains fixes for previously identified bugs AND new features released by Oracle for PeopleSoft V9.2 applications.

2. Strategies for Consuming PUM

Customers can choose from one of the following three options:

2.1 Complete

This option requires downloading and applying the chosen PUM Image in its entirety. Upon doing so, the PeopleSoft instance to which the PUM image is applied will contain all the cumulative fixes and new features available in that PUM image.

Pros Cons
Simpler to apply than the other two options. instead of having selective fixes Have to apply all fixes and new features in one package, including those to modules where you may not need need fixes or new features at the time
Create a single change package using the PUM image and deploy contents of the entire PUM as a single update to your PeopleSoft instance as opposed to selecting individual fixes or features. Could be a large package of changed objects depending on the PUM image as its cumulative.
All modules will contain the same level of updates. All modules will get fixes and features, as a result all modules have to be tested. (All modules refers to all modules implemented only)
All modules will be tested together with your baseline FasTest/PTF regression library. Testing all modules and all features may be a bit more time consuming that testing selective updates.
Keep up with the latest feature like Fluid UI that are only delivered through PUM images Have plan to deploy new features, test them and validate them
Predictable schedule and effort, costs and timelines can be aligned as part of annual project planning effort Business will have to wait for that one time a year to get their hands on new features.
2.2 Selective

This option requires downloading the entire PUM image first and then creating custom change packages by selecting individual or sets of fixes and or new features depending on your need. Change Assistant will take care of identifying the pre and post requisites associated with the custom fixes or features selected to create a complete package of change that can be applied. Upon applying this selective change package, only those fixes and or features selected by you will be applied to your PeopleSoft instance.

Pros Cons
Only apply fixes as needed for bugs that impact your current implementation. ptions. instead of having selective fixes. No pre-requisite to analyze the individual fixes to identify dependencies. The process of selecting individual fixes, creating change packages and deploying selectively can be time consuming. he time
Consume new features only when you are ready to use them. Each PUM has several new or enhanced features that could bring improvement and optimize your current implementation. Not applying and consuming them on a regular basis could mean that you are losing out on the latest features that and the improvements they deliver.
Each module could be at a different “fix level” as opposed to having the same level which you get in the Complete option. All modules will get fixes and features, as a result all modules have to be tested. (All modules refers to all modules implemented only)
Testing can be concentrated only on those fixes or features consumed as opposed to the whole image. Creating a regression library from your baseline FasTest/PTF library for the change package created in the Selective method could be time consuming.
Scheduling could be erratic and could interfere with other in-flight projects
2.3 Hybrid

This option gives customers the flexibility to apply a Complete Image one or more times a year and apply Selective updates at other times depending on need.

Pros Cons
Applying the Complete PUM Image on or more times gets you “caught up” with PeopleSoft releases and gives you new features and fixes across the board for all implemented modules. The process of selecting individual fixes, creating change packages and deploying selectively can be time consuming. he time
Flexibility to apply individual fixes for critical bugs or new features aligned with overall application strategy. Each time you apply a fix or feature selectively, you have to create a change package, deploy it and regression test it.
Each module could be at a different “fix level” when you apply selective fixes, but you would get “caught up” at least once a year with a full PUM image applied. Regression testing for complete PUM and selective updates both.
Best of both worlds – get the latest features and fixes when you need them and keep relatively current with PUM on an annual basis Could introduce fatigue within IT and Business teams when applying multiple updates in a year.
Predictable schedule for annual PUM update, Selective updates can be driven by project need or business need and can be prioritized. In some cases these two can be merged

Add Your Comment