Skuid Testing
Provar now supports Skuid testing. Skuid is an AppExchange solution that provides tools to quickly create Salesforce pages with a custom user interface and greater functionality. Learn more at Skuid.com.
Skuid testing is an interesting case because whenever changes are made to a Skuid page, this changes the XPaths, so automation test cases that use XPaths will need to be updated. This occurs with even minor page changes. For example, if we locate two fields on a page using XPaths, and, later, another field is added at the start of the page, the existing XPaths will no longer be accurate.
Another unique feature of Skuid testing is that Skuid has Tab Sets, which contain various tabs. To properly test all these tabs, we must manually switch between tabs and write additional steps to manage this.
Finally, Skuid also has master pages used to create child pages. These child pages have entire master pages with some additional content. XPaths must be rewritten for each page to test all these child pages.
Skuid Testing with Provar
Provar’s solution is to integrate with metadata so that any changes in the page can be detected and handled to ensure that existing test cases don’t break. Adding more fields or sections to a Skuid page does not break existing test steps.
In addition, users can author new test steps or test cases after the changes, and Provar will recognize the new changes automatically.
Provar automatically switches between tabs on a Skuid page without adding extra steps, making test cases shorter and easier to understand.
Finally, when testing child pages created from master pages, Provar automatically recognizes the child page through metadata and uses the information from its master page to test the child page.
As usual, metadata reload is needed after changes are made to the Org.
Skuid Testing Setup
To start testing a Skuid application, first Add your Salesforce Connection details in the usual way:
Skuid Test Case
You can create test cases and add test steps via the Test Builder.
Map Skuid pages as you would any average page:
Note that the page and fields have been recognized automatically as normal:
From Provar Desktop, the test case shows that it has recognized the Skuid page automatically:
Provar also supports the mapping of master and child pages.
An example master page:
In Provar Desktop:
Example child page:
In Provar Desktop:
Provar also supports the mapping of Skuid tables:
And in Provar Desktop:
Provar also supports the mapping of lookup fields on Skuid pages. Note that the lookup is recognized automatically in the test step below:
And in Provar Desktop:
Finally, Provar also automatically recognizes and maps summary fields:
In Provar Desktop:
- 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
- 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
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes