Vlocity API Testing
Vlocity UI Testing (*Vlocity is now “Salesforce Industries“) comprises JSON components. Thus, when Salesforce parses and displays these Vlocity UI fields, it creates dynamic ‘ng’ locators in the DOM, making it difficult for other automation tools to identify them with the traditional locators. Provar has implemented a unique solution that readily identifies and maps Vlocity UI elements on the page using a custom locator. This makes Vlocity API testing automation simple, maintainable, and more reliable.
Vlocity API Automation Testing
Vlocity objects are downloaded and available in the Provar Org Browser. This provides data visibility and allows the tester to create/modify data. This approach can create test data quickly and is ideal for creating seed data for a deterministic test case.
Vlocity UI Testing
Provar Test Builder maps the various Vlocity UI fields by using the By Vlocity Label locator, as shown below:
Vlocity Text Field
Vlocity text fields are recognized using By Vlocity Label locator and the Visual force page configured on it.
Vlocity Picklist
Vlocity picklists are similarly mapped, and all the options in that picklist are shown. The user can then choose to either set or assert a picklist value from the available options.
Vlocity Lookup
Vlocity lookups are different than what we have in Salesforce. It is mostly confused with an SF dropdown menu, but the options shown depend on the value we provide in the filter text box. Provar offers a simple implementation to map Vlocity lookups in which you can specify a filter and select the value in a single step.
Vlocity Checkbox
Vlocity checkboxes are mapped using the By Vlocity Label and show interaction types as Check, Uncheck, and Toggle.
Interested to know more about Vlocity testing with Provar? Get in touch today for a full demo.
- 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