7 Min Read

How PeopleSoft Test Framework 2.0 enhanced system confidence and Lower cost

By Biv
July 1, 2019

The main advantage of PeopleSoft test framework (PFT) is consistency. It is one way to enhance your organization’s confidence in the PeopleSoft Test Framework. It is a critical factor in presenting PTF as an affirmative value proposition.

Once the test runs without any trouble, it always runs well until there is a configuration change. It is simple to change the data value to build different test cases for the same basic test, and this produces excellent adaptability with less cost.

As PTF output reports can identify update issues, the pre-update tests will not have to be rerun after all PeopleSoft update manager (PUM) problems are addressed. PTF reports recognize PUM that changes test objects. Also, PTF reports know PUM changes not covered by PeopleSoft test objects. PeopleSoft Test framework 2.0 gives businesses the confidence that regression tests identify anomalies at more inexpensive than traditional testing.

When you develop PTF tests, you assume that every time you run the same test, it will run successfully. If you think deploying PTF, your company will need you to confirm that PTF is reliable and cost-effective before committing resources to develop PTF scripts fully.

PTF in the “Debug” Mode

Move to Execution Options -> Debugging -> Skip PageSave or Skip RunRequest equal to Yes to turn off either or both, then click Accept in the upper right to save your selections.

After that, you can run the same process repeatedly without initiating a different constraint error. Quite a timesaver when you understand this small trick.

Then set Skip PageSave to Yes when you run the test. The save will not take place at the end of the test script, which allows the script to be debugged without having to change the data for each test potentially.

End-to-End Processing

If you want to test a “downstream” process, for example, posting an AP Voucher, you must understand what voucherID to post. When you build an end-to-end process, you will always know the voucherID because you will use a determined variable to see the voucherID in the script.

Using Formulas

Now takes a glance at the above voucher example. “Voucher save” will fail if it does not pass duplicate checking—usually a mixture of the same vendor, date, amount, and invoiceID. If a formula is employed for invoiceID that generates a unique invoice number, then the method would save the voucher every time it’s run.

The issue: a unique invoice number must be utilized for every test.

The solution: Invoice ID = the 12 right characters of the following PTF formula

right(concat(year(date())|month(date())|day(date()|hour(time())|minute(time())|second(time()))|12)

The issue: a US federal ID requires a unique SSN/FEIN. A similar formula provides a solution.

The solution: FEIN = the 9 right characters of the following PTF formula.

right(concat(year(date())|month(date())|day(date()|hour(time())|minute(time())|second(time()))|9)

Create a New Test Case with New Values

There are various methods to make a new test case. It can be built manually by doing a “Save As” on an existing test case or by exporting the current test case to Excel where you can make the changes, and then import a new test case from Excel.

At Sentinel Software, we provide constant support to hundreds of companies to enhanced system confidence and Lower cost with the help of PeopleSoft Test Framework 2.0. For more details, feel free to contact us.