Internationalization support
Automation supports internationalization testing of Salesforce, i.e., the end-user testing of Salesforce in languages other than English.
If your company operates across the globe and your teams take advantage of Salesforce’s native ability to switch the UI to their preferred language of choice, you must be able to test your business-critical processes for every language.
Simplify multi-language testing with reusable, compatible tests
With Provar internationalization testing, you can avoid the complexities of building and maintaining separate regression tests in different languages. With Automation, your QA teams can create a single, reusable test in Salesforce in their native language and automate that same test across other languages, too.
Instead of pushing out a new release and waiting for a call to learn about inadvertent impacts, you can create a library of tests that work for Automation and Salesforce-supported languages, including English, Danish, Dutch, German, Italian, Portuguese, Spanish, French, Swedish and Japanese (Beta).
To test Salesforce in a different language, simply follow the normal process of mapping test steps in the Test Builder. Automation will detect the language automatically and map test steps as usual.
In the example below, Automation is testing Salesforce in French.
The following test step illustrates mapping a new Opportunity.
You can see that the page and fields have been recognized automatically with both their French labels and their English translations.
In Automation, the above test steps appear as follows:
Note: Automation’s syntax is in English as usual, but some elements retain the language they were displayed in in the UI.
The test above displays as follows when run in the Test Runner:
- 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