Skip to main content

Testing and deploying application changes

Suggest edit Updated on September 12, 2020

Test a new application in the Build environment before migrating the application to a test or production environment. Testing in the Build environment enables you to verify that basic functionality and interfaces work correctly, and that performance is acceptable.

  1. Run functional tests, to test specific features from the end-user perspective.
  2. Test features used by all service intents, such as security, eligibility, search, and loading of data. Automated scripts are recommended for this unit testing, but are not required.
  3. 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.
  4. Test all integrations, both independently and with associated integrations. 

    Test integrations for any optional Pega Retail Advisor 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).

  5. Test security. Test the most common roles to ensure that the required access groups are configured and point to the correct software version.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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