Skip to main content

Testing in the Build environment

Suggest edit Updated on September 18, 2020

Test a new application in the Build environment before migrating the new 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. Run automated unit tests to test features such as security, eligibility, search, and loading of data.
  3. Use the Performance tool (PAL) to measure the performance of the application. For information about the PAL tool, see Tracking system utilization for a requestor session with Performance Analyzer.

Prior to extending your site-specific Pega implementation, Pegasystems recommends that you establish a performance benchmark (baseline) using PAL. This allows subsequent, iterative performance tests against the established baseline to help identify any degradation in performance resulting from development efforts.

Use PAL to check the performance of the following:

  • Search
  • Loading of components

Save the PAL test results so that you can compare them to future PAL test results to determine whether an application update has a performance impact.

  1. Verify that the Pega-provided 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.
  2. Test all integrations, both independently and with associated integrations.
  3. 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