Sauce Labs desktop
Provar supports Sauce Labs desktop cloud testing. (And, oh hey, we do Sauce Labs mobile, too.)
Sauce Labs provides comprehensive desktop testing using real devices, emulators and simulators. With Sauce Labs you can run automated tests of your web apps on a variety of operating system/browser versions for desktop and mobile browsers.
Configuring Sauce Labs in Provar
Before configuring a Sauce Labs Desktop App in Provar, you should have already sorted your Sauce Labs setup and have your Sauce Labs username, access token and factory class (if applicable). Refer to Sauce Labs’ documentation for more information on completing this setup in Sauce Labs.
Adding a browser provider
To begin configuring the Sauce Labs Desktop App in Provar, start by adding a new Browser Provider.
Navigate to the Test Settings view and click the Browser Providers tab. Then, click the Add New (‘+’) button.
On the Add new Browser Provider screen:
- In the Name field, enter a browser provider name.
- In the Type field, select Sauce Labs Desktop from the drop-down.
Add your Sauce Labs details to connect to Sauce Labs, including Factory Class if applicable.
Within the Data Center drop-down menu, you can choose from globally accessible data centers while creating a Sauce Labs connection. In the Data Center field, select the specific Sauce Labs data center.
Use the Test Connection button to verify the server details.
Next, add the Browsers that will be used by clicking the Add New (‘+’) button on the Browsers section.
A new Add Sauce Labs Desktop Browsers screen is displayed, select the Platform where testing is going to be carried out. (You can ignore the Browser Name as this will be pre populated based on your other selections.) The Platform drop-down will show all the platforms assigned to the relevant Sauce Labs account.
Then, select a Web Browser and a Browser Version. For the Browser Version, you can select the latest instead of a specific version if you want to run on the latest version of your chosen browser.
Once you are happy with the device details provided, click OK. You can see the browser is added.
You can see that the added browser provider is displayed in the Browser Providers tab.
Running Tests on Sauce Labs for Desktop
Once set up has been completed, tests can be run in Run mode, Debug mode or Run under ANT.
Run and Debug Mode Execution
To start executing test cases, first select the new Web Browser which you created above:
This can also be set for a particular test case by using the ‘Web Browser Override’ on the test’s Connection step.
Then, click Run or Debug to run the test.
Progress can be monitored as usual in the Test Runner.
In the Sauce Labs Dashboard, under Automated Builds, you can monitor currently running and previously executed sessions.
Clicking on a session provides running details.
Run under ANT execution
Provar also provides Run under ANT execution for Sauce Labs for Desktop.
To select this, right-click on the test(s) or folder and select Run Under ANT.
In the ANT Dialog, select the new Web Browser you created above.
This will add the following parameters to the Build.xml file.
Running this file will initiate the session/run in a similar way to the Run and Debug mode sessions above.
Sauce Labs execution will work as normal when there are proxies defined under Provar Network Settings, or defined under the Desired Capability of the Browser Provider as a proxyURL (see below).
Note that, if proxy information is set up at both levels, Provar will give preference to the proxy information in the Desired Capability setting in the Browser Provider.
To add a proxy at the Browser Provider level, open the Browser Provider in edit and go to the Desired Capabilities section.
Click the Add New (‘+’) icon.
On Add new desired Capabilities screen, enter a Name of proxyURL and the value.
Then, click OK.
Once added, use the Test Connection button to make sure the connection is working as expected.
Modifying the Job Name
You can define a custom Job Name if you would like to present a specific name in Sauce Labs. This is helpful when you have multiple sets of test cases. If a custom Job Name is defined, a single entry will be created with a grouping of test cases inside.
You can define a custom Job Name by setting up a new system environment variable or in console where an ANT job is running. If the environment variable PROVAR_Sauce Labs_BUILDNAME is set, this name will be used as the build name.
This can be done by setting up a new system environment variable of PROVAR_SAUCELABS_BUILDNAME.
The system environment variable can also be set in the console.
The following limitations currently exist in Provar’s implementation of Sauce Labs.
Accessing Chrome profiles
Normally, when Provar’s test execution happens locally, Provar users can specify the Google Chrome profile that should be used in the execution. This is not supported when executing tests over Selenium Grid as the execution will be happening at the remote node. Due to this limitation, you’ll need to re-provide a password and verification token when executing over Selenium Grid, or your IP will need to be whitelisted. Salesforce should know from where the request is coming so it can provide login access to execute the tests.
Accessing locally stored files
Normally Provar allows you to download a file locally to perform actions such as assertions. This is not supported when executing tests on Selenium Grid because the remote node will not be able to access the locally downloaded file, so any tests which use locally downloaded files will not run successfully.
If you are affected by either of these limitations please contact Provar support directly for advice.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- 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
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar 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
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- 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 CI
- Travis CI
- Execution Environment Security Configuration
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Configurations and permissions
- Error messages
- Administrator has blocked access to client
- macOS Big Sur upgrade issue
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes
- Version 2.8.0 Winter ’23
- Version 2.7.2
- Version 2.7.0 Summer ’22
- Version 2.6.3
- Version 2.6.0 Spring ’22
- Version 2.5.0 Winter ’22
- Version 2.4.1
- Version 2.4.0 Summer ’21
- Version 2.3.1
- Version 2.3.0 Spring ’21
- Version 2.2.1
- Version 2.2.0 Winter ’21
- Version 2.1.1
- Version 2.1.0 Summer ’20
- Version 2.0.5
- Version 2.0.4
- Version 2.0.3 Spring ’20
- Version 1.9.12
- Version 1.9.11