Governor Limits

Overview 

The main purpose of governor limits is to guard against software and system failures. By enforcing governor limits, Prodly ensures that both the Prodly AppOps Salesforce app and the Prodly AppOps 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 AppOps Test enforces, along with whether enforcement takes place in the Prodly AppOps Salesforce app and/or in the Prodly AppOps backend service. Whenever possible, enforcement takes place in the application UI. To avoid having to redo your work, pay special attention to not exceed the limits that Prodly can only enforce in the backend service.

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

Additional Tips 

Delete Unneeded Historical Test Runs 

Keep an eye on how much storage your test runs are using and delete unneeded test runs. The estimated size of 4000 test run result records is about 7MB.

Test Run API 

The test run execution API uses batch (not bulk API) requests.