PTF: How to create and manage Test Cycles

As we have seen in the previous blogs, PeopleSoft Test Framework (PTF) automates business process testing within PeopleSoft through its Record and Playback capability and it helps in different types of testing in PeopleSoft applications.

Creating and managing a test cycle plays an important role in any type of PeopleSoft application testing.

Create and manage test cycles

A test cycle comprises of many aspects like:

• Test Strategy in PTF - Define your overall testing strategy, including the objectives, scope, and timelines of the testing effort. Identify the modules or areas of the PeopleSoft application that need to be tested.
• Test Plan - A test plan in PTF consists of the scope of testing - test scripts to be executed, test data to be used, different business scenarios to be tested, different environments where test scripts to be executed, timelines, test results as a deliverable.
  The test plan should outline the specific test cycles you plan to conduct, test objectives, test scenarios, and test cases for each cycle.
• Test Cycle Setup - Set up the necessary test environment for the test cycle, for each PeopleSoft application pillar. This includes configuring the PeopleSoft application, creating test data, and ensuring that the required test resources, such as test scripts, data, execution options with user ids and accesses are available.
• Test Script Execution - Execute the test script as defined for the test cycle. Document the test results, including any defects or issues encountered during testing. If needed, re-run the test script with modified test cases i.e., test data
• Defect Management - Track and manage defects discovered during the test cycle. Refer to the test script execution log to check the Test Results. Use a defect tracking tool or system to log defects, assign them to the appropriate team members, and track their resolution status. Prioritize and schedule defect fixes based on their severity and impact.
• Test Cycle Review - Conduct a review of the test cycle once all the test scripts have been executed for each of the PeopleSoft application pillars. Evaluate the test results and identify any gaps or areas for improvement. Document lessons learned and make necessary adjustments for future test cycles.
• Repeat the Cycle - Repeat the above steps for each test cycle required for your PeopleSoft application testing. Each test cycle can focus on different modules or functionalities, different environments and test data based on your testing goals.

Tips on executing and managing Test Cycles

Test plans/cycles need to be executed based on the priority (business critical test scripts followed by medium and low priority scripts) and the test cycle path (DEV > TEST > SIT > UAT).

Many times, the sequence of execution of test scripts is important when scripts are dependent on a certain test result/values fetch.

It is very important to monitor Test plan execution in order to be in line with the test phase, timelines, and deliverable.

Conclusion

We have seen the various aspect of having creating and managing test cycles in PTF, how to set them up and execute successfully.

If you are using PTF scripts in your organization for your testing, I would encourage you to use the pointers from this blog for your test cycles.

Also, please share your experiences with testing using PTF and any insights you may have in the comments section.