Skip to main content

Validating the completion of update testing

Suggest edit
Updated on April 29, 2021

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

Types of update validation

You can use two types of update 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-update 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. Note: 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-update issues.

Update 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, updated staging environment is provisioned until now
  • The last 60 days
Note: 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.

Understanding the update validation workflow

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

The update validation workflow consists of the following steps:
  1. During stage 3: Basic update validation using application testing, test all your applications on the cloned, updated staging environment for functional correctness within either 10 days (for an update from Pega Infinity release 8.4.2 or later) or 30 days (for an update from Pega Infinity release 8.4.1 or earlier).
  2. Notify Pega that you are ready to update to production:
    • If you update from Pega Infinity release 8.4.2 or later on Pega Cloud services, go to My Pega Cloud, and, in the My Pega Cloud tab, indicate your approval for the update on your production environment by using the Go-NoGo banner. You can skip this step if you update from an earlier version or for on-premises systems.
    • If you update from Pega Infinity release 8.4.1 or earlier, notify Pega that you are ready to proceed with your software update by updating the existing update request.
    Result: The Application Testing Tracker fetches the latest validation reports to verify that you have completed testing.
    • If you completed testing, the update to production resumes.
    • If you did not complete testing, the tracker pauses so that you can finish testing before resuming the update to production.

Client responsibilities

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

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

Configuring your environment to use the Application Testing Tracker

Before you can use the Application Testing Tracker, configure the cloned, updated 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 ruleset link.
  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 updating 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 ConfigureSystemSettingsApplication Testing Tracker.Result: 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.Result: Results for untested validations are displayed in a new tab.

    If case type validations failed, the service engineer who is responsible for updating 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 Resolving validation failures

Resolving validation failures

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

When case type validation fails, the service engineer who is responsible for updating 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 ConfigureSystemSettingsApplication 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.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us