Provar test results package
Provar has a managed package on the Salesforce AppExchange that is for storing and displaying Provar test results in a dashboard view inside of your Salesforce org. For information on how to install and setup this package, please refer to the Salesforce Test Integration Package.
This 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 you have this project 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 Test Case.testcase: This is a callable test case that must be run inside of a Finally block at the end of each test case you want to track results for. Examples can be seen inside of 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 tracked properly in your Salesforce org. A good way to do this is by using the TestCaseName() function built-in to Provar and pass 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 begin to see your test results inside of your Salesforce org, along with your linked Copado deployment.
Linking your Copado deployment to test suites
Finally, if you want to link our test results to the Copado deployment log record id, then you need to create a new Lookup relationship from test execution suite object to the Copado deployment object. When this is populated in the Provar test case the test results will automatically become visible from Copado.
Once this is added, you can begin testing your deployments with the added test cases to see if they are updating the records properly.
If so, you should see some test suite executions being created, and the Copado deployment record link:
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- 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
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar 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
- Circle CI
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server (Beta)
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Service Cloud console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes