An Introduction to Callable Tests Case
It is possible to convert a test case into a Callable test case. This is recommended to encapsulate functionality and make it reusable across several test cases.
These tests also reduce test maintenance since they provide a centralized location for regularly used functionality.
Create a Callable Test Case
Define the main Parameters and Settings in the test case. Then, set Callable on the Callable dropdown:
This will add a small red image against the test case in the Navigator to indicate that the test case is Callable.
You can now pass parameters into the called test and return output parameters.
Then, save the test case.
Invoke a Callable Test Case
To invoke a Callable test case, first, open the test case that should be called. Then locate the test case in the Navigator and click and drag it into the Calling test:
You will note that the Call is created as a new test step containing Input and Output Parameters. These values can then be defined as required.
Callable Test Value Visibility
As your tests get more sophisticated, there is a danger that called test cases would start ‘stepping on each other’s toes,’ with called test cases overwriting values on which other test cases depend.
Provar observes the following rules to mitigate these issues:
- Called test cases cannot see their Caller’s values. These need to be passed as Input Parameters if required.
- The Calling test case cannot see the Called test case’s values. These need to be returned as Output Parameters if required.
- If a Called test case defines a value with the same name as the Calling test case, these values are kept separate, and one will not overwrite the other.
- Folder values and Global values are shared between test cases.
- 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