Vlocity UI is made up of JSON components. Thus when Salesforce parses and displays these Vlocity UI fields, it creates dynamic ‘ng’ locators in the ‘Dom’ that makes it difficult for other automation tools to identify these fields 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 automation simple, maintainable and more reliable.
Vlocity API Testing
Vlocity objects are downloaded and available in the Provar Org Browser. This provides visibility of the data and also 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 ‘By Vlocity Label’ locator as shown below:
Vlocity Text field
Vlocity text fields are recognized using ‘By Vlocity Label’ locator along with the Visual force page on which it has been configured.
Vlocity picklists are similarly mapped and all the available options in that picklist are shown. The user can then choose to either set or assert a picklist value from the available options.
Vlocity lookups are different than what we have in Salesforce. It is mostly confused with a SF dropdown menu, but actually the options that are 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 checkboxes are mapped using the ‘By Vlocity Label’ and show interaction types as Check, Uncheck and Toggle.