Skip to main content

Testing in the test or production environments

Suggest edit
Updated on May 12, 2021

After you import your application to a test or production environment, test the application in the new environment to verify that it works correctly in that environment.

  1. Verify that the source and destination files are the same.
  2. Run functional tests to test specific features from the user perspective.
  3. Test features used by all service requests, such as security, eligibility, search, and loading of data. Automated scripts are recommended for this unit testing, but are not required.
  4. Run automated unit tests to test features such as security, eligibility, search, and loading of data.
  5. In the test or production environment, run the Application Guardrails Compliance Score to ensure that the application meets guardrails.
  6. Verify that there is an open production ruleset so that managers will be able to edit dialogs, coaching tips, and knowledge content in the test and production environments, and so that they can share those changes. Rulesets are typically locked during migration and must be unlocked after migration.
  7. Verify that the out-of-the-box reports and your custom reports run successfully, and that they show your implementation layer data, rather than the default demonstration data. This can be an automated test.
  8. Test all integrations, both independently and with associated integrations.

    Test integrations for any optional Pega Care Management components and other applications that you plan to use. See the product documentation for the component or application to determine which product components to test.

    For Pega Call, check the following pieces of moving infrastructure.

    • Switch
    • Provider software
    • Connectivity (network)
    • CTI engine
    • Integration with the CTI engine

    In addition, check all delegated rules (for example, coaching tips).

  9. Verify that the integrations point to the correct system of record, and not to the system of record for the Build environment.
  10. Test security. Test the most common roles to ensure that the required access groups are configured and point to the correct software version. Use these common roles in your smoke tests. See step 11.
  11. Run a smoke test to compare the source and destination environments. Verify that all tests that pass in the build environment also pass in the test or production environment. If anything fails, compare the environments to determine whether it is a difference in environment that causes the test to fail. If the environment causes a failure, either fix the issue that causes the failure or adjust the test as appropriate for the new environment.
  12. Run performance tests to verify that performance meets expectations. Pega recommends automated performance testing. Save the results so that you can compare them to future performance test results to determine whether an application update has a performance impact.
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