Before you integrate test providers with DevOps Testing, review these limitations and behaviors.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Professional (API access required), Unlimited, and Developer Editions |
Code Analyzer
- Code Analyzer with
--workspace .in the YAML configuration always scans all files in the repository, including the files changed in the work item being promoted. Narrowing the rule selector, for example--rule-selector recommended, doesn't reduce the number of files scanned. - Code Analyzer runs fail with an Apex CPU time limit exceeded error when a repository has approximately 2,000 or more violations. To resolve this issue, reduce violations by reviewing your GitHub Actions workflow results, or unassign the Code Analyzer test suite from the affected pipeline stage.
Flow and Apex Unit Testing
- DevOps Testing syncs up to 10,000 Apex unit test records. It skips any additional records.
- Apex unit test and flow test executions with more than 5,000 test records may impact performance.
- Apex unit test or flow test executions fail if their runtime exceeds four hours.
- Flow class name (flowtesting.namespace.flowname) must not exceed 255 characters.
- Apex class name (namespacePrefix.apexClassName) must not exceed 255 characters.
- Flow method name, which is a combination of the test name and flow name, must not exceed 236 characters. If the combined length exceeds this value, DevOps Testing skips the record.
- Apex method name must not exceed 217 characters. If the method name exceeds this value, DevOps Testing skips the record.