Close popover

Table of Contents

Validating the completion of upgrade testing

For Pega Infinity upgrades on Pega Cloud Services, during the Basic upgrade phase, the Application Testing Tracker automatically verifies that you have completed upgrade testing on the cloned, upgraded staging environment before Pega upgrades your production environment. By using this service, you can monitor what you need to test so that the upgrade to production proceeds.

Types of upgrade validation
You can use two types of upgrade validation: case type and application login.
Case type validation
Verifies that at least one case instance of every case type exists across all your applications in the system. This validation ensures that you have tested all case types at least once. To prevent post-upgrade issues, test all the case types in your application.
Application login validation
Verifies that at least one user login exists for each of your applications. This validation is a minimal check to ensure that you have conducted user-level testing.
While the application login validation passes when you log in to one application with one user, log in to each of your applications with operators from all the applicable access groups to identify any post-upgrade issues.

Upgrade validation fails when either one or both of these validation checks fail.

The data for both checks is taken from one of the following periods of time, whichever is earliest:

  • From the time that the cloned, upgraded staging environment is provisioned until now
  • The last 60 days
The Application Testing Tracker does not check Pega Platform applications, industry applications, or the case types that belong to those applications. The Application Testing Tracker only checks the applications that you create.

Upgrade validation workflow
The Application Testing Tracker runs on your system every day and generates a report that displays the upgrade validation results up to the current day.

The upgrade validation workflow consists of the following steps:

  1. During stage 3: Basic upgrade validation using application testing, test all your applications on the cloned, upgraded staging environment for functional correctness within either 15 days (for a minor upgrade) or 30 days (for a major upgrade).

  2. Notify Pega that you are ready to upgrade to production:

    • If you upgrade from the 8.4.1 release of Pega Infinity or later on Pega Cloud Services, go to My Support Portal, and, in the My Pega Cloud tab, indicate your approval for the upgrade on your production environment by using the go/no-go banner. You can skip this step if you upgrade from an earlier version or for on-premises systems.
    • If you upgrade from earlier releases of Pega Infinity than 8.4.1, notify Pega that you are ready to proceed with your software upgrade by updating the existing upgrade request.
    The Application Testing Tracker fetches the latest validation reports to verify that you have completed testing.
    • If you completed testing, the upgrade to production resumes.
    • If you did not complete testing, the tracker pauses so that you can finish testing before resuming the upgrade to production.

Client responsibilities

During upgrade testing and validation, client responsibilities are as follows:

  • During the prescribed upgrade validation interval, perform application compatibility testing and validation on the upgraded, cloned staging environment.
  • Notify Pega that you are ready to upgrade to production.

Configuring your environment to use the Application Testing Tracker

Before you can use the Application Testing Tracker, configure the cloned, upgraded staging environment so that you can run the tracker and view results.

You configure your environment by adding the PegaPlatformValidator access group to the appropriate operator ID.
  1. In Dev Studio, in the lower-right corner, click your operator icon, and then click Operator.

  2. On the Edit Operator form, in the Application Access section, click the Add rulesetlink.

  3. In the Access Group field, press the Down arrow key, and then select PegaPlatformValidator.

  4. Click Save.

Viewing validation results

The application testing tracker runs daily, and you can view the results of each day's validation status. By regularly checking this page, you can monitor the case types and application logins that you need to test before upgrading to production.

  1. Select the PegaPlatformValidator access group as your default access group:

    1. In Dev Studio, in the lower-right corner, click your operator icon, and then click Operator.

    2. On the Edit Operator form, in the Application Access section, click the radio button for the PegaPlatformValidator access group.

    3. Click Save.

  2. In Dev Studio, click Configure System Settings Application Testing Tracker .

    The System: Application Testing Tracker page displays the overall validation status, the status of case type and application login validation, and validation reports.
  3. To view details of the validations that were not tested, on the System: Forensic Validation page, in the Validation history section, in the Validation column, click a report.

    Results for untested validations are displayed in a new tab.

    If case type validations failed, the service engineer who is responsible for upgrading your production environment provides you with the unique validation ID of the report that lists the case type validations that failed. You can then use the report to help you resolve those failures.

    For more information, see Validating the completion of upgrade testing

Resolving validation failures

Upgrade validation fails when either case type validation fails, application login fails, or both. When validation fails, the upgrade process stops. After you resolve upgrade failures, your upgrade to production resumes.

When case type validation fails, the service engineer who is responsible for upgrading your production environment checks the error message and the recommendation for resolving the error. The service engineer then provides you with the unique validation ID of the report that lists the case type validations that failed. You can then use the report to help you resolve any validation failures.

  1. Select the PegaPlatformValidator:Users access group as your default access group:

    1. In Dev Studio, in the lower-right corner, click your operator icon, and then click Operator.

    2. On the Edit Operator form, in the Application Access section, click the radio button for the PegaPlatformValidator:Users access group.

    3. Click Save.

  2. In Dev Studio, click Configure System Settings Application Testing Tracker .

  3. On the System: Application Testing Tracker page, in the Validation History section, in the Validation column, click the report whose name matches the validation ID.

  4. After you resolve errors, check whether your validation now passes, run the Application Testing Tracker again by clicking Re-Validate.

  • Validating the completion of upgrade testing

    For Pega Infinity upgrades on Pega Cloud Services, during the Basic upgrade phase, the Application Testing Tracker automatically verifies that you have completed upgrade testing on the cloned, upgraded staging environment before Pega upgrades your production environment. By using this service, you can monitor what you need to test so that the upgrade to production proceeds.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.