Learn the Fundamentals

Test has 4 main components to authorize, automate, and report on your Salesforce data:

Test Templates Simply a list of fields (from one or more objects) for future use by test cases.

Test Cases Tests specific functionality using the fields from the test template.

Test Suites A structured group of test cases that makes testing more efficient.

Test Runs A collection of test cases and the results of executing those test cases.

Workflow

For maximum flexibility and versatility, you build Test components in this order:

  1. Start by installing the Prodly managed package in the org where your Salesforce CPQ installation resides.
  2. Identify the object fields to test, storing the list of fields as a test template.
  3. Test templates are the building blocks for test cases. Create a test case by selecting a template and other parameters that define what to test. On save, the test case executes and captures the results in the test case to use later as a baseline.
  4. Test cases can be grouped into test suites. A test suite consists of one or more test cases, allowing you to group them logically (e.g., all tests for renewal scenarios) to make testing more efficient.
  5. Create a test run by selecting one or more test cases, or an entire test suite, to execute. This execution generates test run results, which are stored in the test run. Test runs can be executed immediately or scheduled for a later time.
  6. In the future, rerun the test run (which automatically clones and runs it) to generate a new set of test run results.

Limitations

The main purpose of governor limits is to guard against software and system failures. By enforcing governor limits, Prodly ensures that both the Prodly Salesforce app and the Prodly backend service retain reasonable performance and do not breach sizes and limits for memory, CPU, heap, threads, and time.

Governor Limits Table

This table lists the governor limits Test enforces, along with whether enforcement takes place in the Prodly Salesforce app and/or in the Prodly backend service. Whenever possible, enforcement takes place in the application UI.

Description Limit App Service
Maximum test fields per test template 50 Yes No
Maximum quote lines per test case 500 Yes No
Maximum baseline values per test case 25,000 Yes No
Maximum test cases per test run 1000 Yes No
Maximum records per test case. Test silently skips records above the limit 50,000 Yes No
Maximum concurrent test cases executions 1000 No Yes
Maximum number of test run result records per API batch request allowed by Salesforce 2000 No Yes
Maximum test case execution time in seconds 180 No Yes
Maximum scheduled test runs 10 Yes No

<aside> <img src="/icons/warning_red.svg" alt="/icons/warning_red.svg" width="40px" />

Test cases are limited to a maximum of 50,000 records. If a test case's query returns more than this limit, Test will silently ignore all records beyond the 50,000 maximum.

You will not receive an error or notification for these skipped records.

</aside>