Provar now supports the use of Perfecto mobile cloud for cloud-based test execution.
The Perfecto Mobile cloud is a web-based Software as a Service (SaaS) platform that allows mobile application developers and QA Engineers to work with services such as advanced automation, monitoring and testing services. It enables mobile app testers to automate testing for mobile phone devices connected with diverse mobile networks spread across different geo-locations.
Configuring Perfecto in Provar
Before configuring a Perfecto Mobile App in Provar, you should have already sorted your Perfecto setup and have your Perfecto Mobile Server details (username and password or a security token). Refer to Perfecto’s documentation for more information on completing this setup in Perfecto.
Adding a browser provider
To begin configuring the Perfecto Mobile 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, add a Provider Name and then select the Perfecto Mobile radio button:
Note that there are two ways we can connect Perfecto application, logging in with user credentials or logging in with a security token.
To log in with user credentials, leave this radio button ticked and add Perfecto mobile server details:
Alternatively, to log in with a security token, tick this radio button and then pass your application security token value into the Security Token field:
Once your login details are added, click the Test Connection button to verify the details are correct:
Adding a device
Next, add the devices that will be used.
On the same screen as above, click the Add New (‘+’) button on the Devices section:
On the Add Perfecto Mobile Device page, you can select the Platform where testing is going to be carried out. Provar provides two-platform support for iOS and Android. Selecting the Platform will alter the options in the Make and Model dropdowns.
First your Platform and then the relevant Make and Model:
Before selecting the Device, note that there are three radio buttons below Device which offer different Device availability types: All, Available and Reserved By You. These define how Provar should pick the Device.
These availability types have the following options:
- If All is selected, the Device dropdown will default to ‘any’ but also offer specific devices for selection (regardless of whether they are currently available for testing)
- If Available is selected, the Device dropdown will offer ‘any’ as well as devices that are currently available for testing.
- If Reserved By You is selected, the Device dropdown will offer ‘any’ as well as any devices that you have reserved for testing on Perfecto.
If there are no available devices, we recommend selecting ‘any’ so that Provar will automatically pick the device which is available at that moment:
Once you are happy with the device details provided, click the OK button to complete adding the Perfecto Mobile Device.
Back on the Browser Provider details screen, you can now click the OK button to complete adding the new Browser Provider. The new Browser Provider will have been added to the list:
Adding a mobile app
We can now add a new Mobile App for Perfecto mobile.
Still on the Test Settings view, click the Mobile Apps tab. Then click the Add New (‘+’) button:
Provide an App Name, then in the Perfecto section select the Application Name from the dropdown.
In this dropdown you can see all the Application Capability Values which are hosted on the Perfecto account.
Note that these names represent the repository path in Perfecto where the mobile app is placed. It will be prefixed PRIVATE or PUBLIC depending on the location in Perfecto.
In Perfecto, this can be seen under the Repository tab where you can place mobile apps. There are two sections, one for Public (named ‘Public Media’) and one for Private (‘My Media’). These folder locations are reflected in Provar as above.
Back in Provar, once you are happy with your Mobile App details, click OK.
You will see this new Mobile App added on the Mobile Apps tab:
Running tests on perfecto
Now that setup is complete you are ready to start executing test cases. To start executing test cases, first select the new Web Browser which you created above.
To create a new Test Case using the setup above, create a new Test Case and select your Perfecto mobile application from the Salesforce Application dropdown. Click the ‘Finish’ button, then build your test case as usual.
Note that you can also run existing test cases by selecting the Web Browser as above and then amending the ‘Salesforce Application’ on the Connect step to reflect the mobile application where your Perfecto app settings are stored.
Once the test is ready to be run, use Run mode or Debug mode to execute it. (Currently Provar only supports these two modes for test execution on Perfecto.) Progress can be monitored as usual in the Test Runner. You can also review test execution on the Perfecto website by clicking More > Device Dashboard:
Click the Select Device option and the Select button to choose a device.
Below is an example of a ServiceMax FSA app test case running on Perfecto through Provar.
You can also access an execution report by clicking More > Execution Center.
To see more detail, click on any row.
- 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
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- 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