The PeopleSoft Test Framework (PTF) is an automation tool delivered as a part of PeopleSoft application that can help in developing test scripts for critical business processes that reduces overall testing efforts and ensures that the work gets done quickly. Moreover, human errors can also be avoided for all the transactions done by system administrators, business analysts and developers during the testing phase.
Rackspace is always on the lookout for new advanced features when released by Oracle. This is normally done by going through the new features training posted on Oracle universities, reading documentation, and getting hands dirty in a lab environment before proposing this to customers. This helps customers in leveraging new features and improves efficiency.
PTF was first introduced in PeopleTools 8.51 but with new advancements in technology, new features are have been added to the PTF framework that makes it a more powerful tool. Rackspace has been working with customers in installing/administering the PTF framework so that customers can develop/record the test cases for critical business transactions. Recorded test cases can be executed a multiple times to test new code enhancements and features. It makes the SDLC process simpler and removes dependency on manual testing.
In this blog, I have covered about PeopleSoft Test Framework, benefits, and steps to configure/administer.
With the introduction of PTF, all the critical business processes can be tested within a few clicks. The PTF tests cases are recorded by recording the transactions done through PIA in an environment and then replaying it multiple times during major/minor Go-lives to ensure that the functionality is working as expected. PeopleSoft administrators can also prepare the PTF jobs and schedule to run it daily to perform sanity checks of their environment to email reports for any abnormal behavior. This is helpful not only during patching but to perform daily health checks for your Production environment. Other than recording the transaction, PTF developer can provide the success and fail scenarios for every test case and perform many functions like taking screenshots, creating reports etc.
The PTF stores your test scripts into a repository database which should basically be a PeopleTools only database. One can use their development environment for holding the test cases or can create a standalone database that will store your test cases. As all the test scripts are stored in the PeopleSoft database as application designer objects. The following are two different ways of maintaining it:
1. Migrate the test scripts using application designer from DEV > TST > UAT > PROD and execute the reports.
2. Use a repository database and use it to connect to all the different environments and execute the test from that repository database only.
Test scripts once developed can be migrated to any environment and used for automating the testing efforts. Even during major upgrades, these test assets require minor modifications and helps in streamlining your testing efforts.
In this section, I have explained different components of PTF and how to install/configure it.
The diagram below explains the same
One needs to complete the following tasks to configure an environment to run the PTF tests:
The users that need to run and record the test cases should have one of the following roles as per their job role:
• PTF User
• PTF Editor
• PTF Administrator
PTF configuration option can be defined from application by navigating to PeopleTools > Lifecycle Tools >Test Framework >Define Configuration Options. This page enables to:
• Specify execution options.
• Configure external command processing
PTF requires SSL certificates to be installed on your Load balancer and web server for connecting with the target application. If PeopleSoft environment does not have SSL certificates installed, login to PTF console will throw an error message that PTF does not allow unsecured connections. However, like any other config option, this can be overridden by PeopleSoft administrators by activating
PTTST_CONFIG_NO_SSL web service to enable HTTP URLs to establish connection using PTF. You will still be displayed with a warning message, but this won’t stop you to login to PTF console.
Following are the steps required to activate
PTTST_CONFIG_NO_SSL web service:
Regenerate Any-to-Local check box.
PTF can be installed using:
• PeopleTools DPK.
• Silent mode using batch file.
• When you click on PTF client, you can see below signon dialog.
• Create a new environment using the New button and specify values for all the Fields.
Execution options lets you define the default settings that the developed cases will use on execution against a target environment. These options can be defined for each environment and generally includes environment specific details like URL, Login credentials, browser details etc. PeopleSoft administrators can define the default execution option in PTF client, or this can be defined in the target database PIA under “Define Configuration Options”.
The following screenshot shows the settings that can be defined using a PTF client:
PTF Explorer lets you access the test cases developed by you to enable you to manage and run against the target environment. You can establish the success and failure criteria for all your test cases.
• Create scripts for test scenarios
• Segregate test scripts inside different folders.
• Allows to Edit/Delete exisiting tests and folders.
• Execute test against a target database.
Test editor allows you to record a new test case or modify an existing one. You can add/delete/update your test scenarios using test editor, and can also run it to see if desired results are being achieved or not.
PTF recorder opens a browser window for the URL defined in the execution options and records all the user actions including the manual inputs as well on any search pages. Once the recording is done, developer can review the steps and modify those inputs. They can also add steps to Verify, Log, and Conditional to determine the Success/failure criteria for the test scenario.
Below image is for Test Recorder toolbar:
This section discusses on the steps needed to administer the PTF environment.
PTF administrators needs to perform regular housekeeping for the log files generated as a part of test cases execution by development/testing team.
To configure Log manager, Navigate to Tools > Log Manager
As mentioned earlier, PTF allows you to make minor modifications to existing test cases in case of PeopleTools upgrade. The PTF client stores the version of the PeopleTools which is used to record the test scripts. In case, you have opened the existing test cases on new tools version it prompts you to migrate this to a newer tools version by performing automated upgrade to the test cases.
In order, to perform actions like add, update or delete, PeopleSoft Test Framework (PTF) users’ needs to have either of the following permission list assigned by the security specialist:
Permission | List | Role
PTPT3400 | PTF | Administrator
PTPT3700 | PTF |Editor
PTPT3600 | PTF | User
Above specified roles can be granted Read/Execute, Modify and Full Control on the different folders and specified actions can be performed by responsible individuals.
From the above discussion, it is evident that all the test scripts created using PTF are Application designer managed object. Hence, this can undergo Object development lifecycle and can be easily migrated from one database to another using Application designer of any other supported migration tools like Phire, STAT etc.
Alternatively, the PTF test cases are stored in a repository database and executed against a target environment using the repository database. Only limitation with this approach is that
PSQUERY will not run if those are part of your test cases. It means that
PSQUERY needs to be migrated to all the environments wherever test cases making use of
PSQUERY needs to be executed.
As you can see PTF offers lot of options to carry out functional tests and tests once created in DEV can be used for unit testing, integration testing, SIT/UAT. Moreover, test cases once developed can be used in the future versions and application enhancements as well with minor modifications making the overall efforts for testing the application functionality as minimal.
Use the Feedback tab to make any comments or ask questions. You can also start a conversation with us.