Provar Test Results Package
Important Note! The Test Results application is no longer supported, and we encourage you to upgrade to Provar Manager. For ease of integration, please refer to our guide Integration with Provar Manager without changing your test cases.
Provar has a managed package on the Salesforce AppExchange that stores and displays Provar test results in a dashboard view inside your Salesforce org. For information on installing and setting up this package, please refer to the Salesforce Test Integration Package.
Provar Test Results package can be used to write your test results back into your Salesforce org, which can then be linked to your Copado Deployment jobs.
The following is a zipped project which contains the necessary test cases to get started with your Provar test results implementation: Provar Copado Integration Tests. Once this project is downloaded to your machine locally, you can extract this folder anywhere.
You can copy the test case files directly to your project. Included are also some sample build files and a test spreadsheet for the sample test.
Note: tests/Copado contains all test cases.
Relevant Test Cases for Writing your Test Results Back to Salesforce
Create Test Suite. setup: This test case is a setup test case that runs at the start to create the Provar test suite execution object. The two customizable fields being used here are:
The provarti__Name__c field is the name of your test suite execution.
The Deployment__c is a reference field to the Copado deployment. We will be pulling this Id from the environment variables. Since all build parameters passed to Jenkins are saved as environment variables, this is the DEPLOYMENT_ID environment variable. This may also be the EXTERNAL_ID environment variable if you have set the build parameter as such.
Create a Test Case. testcase: This is a callable test case that must be run inside a Finally block at the end of each test case you want to track results for. Examples are inside the CreateAndConverLead.testcase and CreateAccountsFromExcel.testcase tests.
You will need to pass the name of the test case being executed to this test case so it can be appropriately tracked in your Salesforce org. An excellent way to do this is by using the TestCaseName() function built-in to Provar and passing that as a test case parameter.
Update Test Suite.teardown: This test case is a teardown test case that will always run at the end of the test run to update the Provar test case execution object with the total test run duration.
Once you have checked in your Provar project with these changes implemented, you can see your test results inside your Salesforce org, along with your linked Copado deployment.
Linking your Copado Deployment to Test Suites
Finally, suppose you want to link our test results to the Copado deployment log record id. In that case, you must create a new Lookup relationship from the test execution suite object to the Copado deployment object. When populated in the Provar test case, the test results will automatically become visible from Copado.
Once added, you can test your deployments with the added test cases to see if they update the records correctly.
If so, you should see some test suite executions being created and the Copado deployment record link:
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Creating and Importing Projects
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- Running Tests
- Searching Provar with Find Usages
- Secrets Management and Encryption
- Setup and Teardown Test Cases
- Tags and Service Level Agreements (SLAs)
- Test Cycles
- Test Plans
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Provar Manager
- DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version Control
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes