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.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- 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
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- 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
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes