Metadata Coverage with Manager
Tracking metadata coverage can give you valuable insight into how you are managing the quality of your applications. With Provar Manager, you can load metadata components, relate Automation test cases to metadata, and generate reports showing your metadata component coverage.
Load Metadata Components into Manager
There are two ways you can load metadata components into Manager. You can do it manually via Manager or you can do it automatically through the Provar Automation integration with Manager.
Via Manager
Salesforce system records let you browse the connected orgs to retrieve their Apex Classes, Apex Triggers, or Flows as Metadata Components (to be used for metadata coverage reporting and smart testing) or import the Apex Unit Tests as Test Cases (for test execution and metadata coverage reporting).
To browse the Salesforce org and import its information, follow these steps:
- Click the Browse Org button on a connected Salesforce system record page.
- Click the corresponding button (e.g., Browse Apex Classes) to load the list of metadata items in the org.
- Select the metadata items you want to import. You can see if they have been imported in the Imported column.
- Click Import as Metadata Components or Import as Test Cases to import the metadata items.
Via Automation
You can also enable Metadata reporting on the connection to Manager by checking the Report Metadata Coverage checkbox. After enabling this feature, Automation will start collecting what Salesforce metadata test cases interact with.
When uploading test cases to Manager, the metadata coverage present locally is also uploaded, allowing you to start running test cases from Manager based on metadata changes tracked in your DevOps pipeline.
Relate Test Cases to Metadata Components
There are two ways you can relate Test Cases to metadata components. You can do it manually via Manager or you can do it automatically through the Provar Automation integration with Manager.
Via Manager
You can link Test Cases to Metadata Components by clicking on the Link to Metadata Components option in the menu.
Via Automation
When setting up your Provar Manager connection, checking the Report Metadata Coverage checkbox will automatically relate your test cases to metadata components.
Report on Metadata Coverage
Code Coverage
Code coverage can be used to understand how much of the code is being tested, but it doesn’t measure how thorough or adequate those tests are.
Still, it can help your team progress toward a more thorough test suite, and highlight trouble spots requiring more attention (e.g. new code introduced but not covered, or coverage % dropping after a deployment).
Provar Manager can be used to monitor Salesforce Apex code coverage across multiple orgs. Follow the below instructions to set it up.
- Go to a System record of type “Salesforce”, or create a new one.
- Make sure Provar Manager is connected to the Salesforce org.
- Click on the “Coverage” tab.
Scheduling Coverage Reports
To schedule coverage reports to run regularly, create a Coverage Report Schedule record from the System record page (see above instructions).
Once the Coverage Report Schedule Status is set to “Active”, Provar Manager will regularly create a Coverage Report record under the selected System as per the schedule settings.
Analysing Coverage Reports
Above: Snapshot of a Coverage Report record.
Each Coverage Report record shows the number of components reported, and the individual coverage of each component.
By clicking on an individual component, you can see its coverage evolution over time and the test cases related to that component.
Teams can easily see if there were drops in coverage at a particular point in time, or if the coverage % is lower than the permitted threshold.
Above: Snapshot of a Metadata Component Coverage chart.
For more information, check out this course on University of Provar.
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Automation
- Provar Test Builder
- ProvarDX
- 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
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar 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
- 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
- Version Control
- Masking Provar Credentials on CI
- Salesforce Testing
- Best Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes