Tags and Service Level Agreements (SLAs)
Tags and Service Level Agreements (SLAs) are very powerful features in Provar that can help you apply labels and descriptions to test cases and individual test steps. These are designed to help you identify important information such as the business owner, the functional area of the test case and the name of the person who is responsible for maintaining the case.
These can help you overcome the challenges associated with managing and organizing a large volume of test cases.
In general, you will need to first create and define your tags and SLAs and then apply them to your test cases where applicable.
The following includes instructions for defining test cases using the Tags and SLA feature.
Business Owner tag
The Business Owner tag is used to define the business owner of test cases.
Step 1: To create a business owner tag, click Test Settings and then the Tags and SLA tab.
Above: View of the Tags and SLAs tab.
Step 2: Click this icon
Step 3: Click the Tag Type drop-down menu and select Business Owner.
Above: View of a Business Owner tag.
Step 4: Enter the Tag Name and Description.
Step 5: Click the OK button.
Above: View of a Business Owner tag.
Functional Area Tag
The Functional Area tag is used to define the functional area of what you are testing. For example, you might want to create a Functional Area tag to describe the individual processes or systems that you are testing.
Step 1: To create a business owner tag, click Test Settings and then the Tags & SLA tab.
Step 2: Click this icon
Step 3: Click the Tag Type drop-down menu and select Functional Area.
Step 4: Enter the Tag Name and Description.
Step 5: Click the OK button.
Above: View of a Functional Area tag.
Test Case Maintainer tag
You can use this to define the name of the person who will be maintaining the test case.
Step 1: To create a Test Case Maintainer tag, click Test Settings and then the Tags & SLA tab.
Step 2: Click this icon
Step 3: Click the Tag Type drop-down menu and select Test Case Maintainer.
Step 4: Enter the Tag Name and Description.
Step 5: Click the OK button.
Above: View of a Test Case Maintainer tag.
Creating SLAs
You can use SLAs to define service level agreement parameters for test cases.
Step 1: To create the SLA, click on Test Settings and then the Tags and SLA tab.
Step 2: Click this icon
Step 3: Select SLA Requirement.
Step 4: Enter the Tag Name and Description.
Step 5: Enter the Expected Duration in (seconds) which will be used to measure test case execution and test step execution.
Step 6: Enter the Maximum Duration in (seconds) which will be used to measure test case execution and test step execution
Step 7: Click the OK button.
Above: View of the Add a new Tag screen.
Above: View of Tags and SLAs screen.
Using tags and SLAs in test cases
You can use tags and SLAs at both the test case level and test step level.
Step 1: Open test case.
Step 2: Click the Tag icon in the test case and select the tag type that you want to add such as SLA Requirement, Business Owner, Functional Area or Test Case Maintainer.
Above: View of Tags icon within a test case.
Step 3: Within the Tags and SLA screen, select the tag(s) or SLA(s) that you want to add from the relevant drop-down menus.
Above: View of the Tags and SLAs window.
Step 4: You can reorder the selected tag(s) and/or SLA(s) using the yellow up and down arrows. This will determine the order in which these sections appear in your exported report.
Step 5: Run your test case.
Step 6: When exporting your test case execution report, you have the option to select Summarize by Functional Area, Summarize by SLA Requirement, Summarize by Test Case Maintainer and/or Summarize by Business Owner.
You will see your test cases grouped by your tags and SLAs.
Above: View of the Export Test Run window.
Above: View of test case report results grouped by tags.
- 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
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- 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 Data Generation
- Test Plans
- Testing Browser – Chrome Headless
- 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
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices 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
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- 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
- Installing Provar After Upgrading to macOS Catalina
- 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