ServiceMax Field Service App Mobile Testing on iOS
ServiceMax Mobile Testing on iOS is a mobile application for engineers in the field. It allows them to access ServiceMax while on the go, comprising a full work order process, calendar and directions, as well as allowing engineers to account accurately for their work, follow the right steps for consistent service and confidently answer customer enquiries.
ServiceMax FSA can be accessed from laptops, smartphones and iPads. Provar currently supports ServiceMax mobile testing on iOS devices (from Provar version 1.9).
Some initial configuration needs to be completed to enable ServiceMax Mobile Testing on iOS. Before you follow the steps below, make sure you have read and completed the steps on the Mobile Testing with Appium page. Once you have completed the steps on that page, return here and continue to iOS Device Setup below.
iOS Device Setup
We’ll start by configuring the device you will be testing on.
Navigate to the Test Settings view and click the Browser Providers tab:
The Browser Provider represents the platform which hosts the FSA. Once you have configured the Browser Provider it will appear in the Web Browser dropdown in the top-right of Provar Desktop:
To begin adding a new Browser Provider, click the Add New button on the Browser Providers tab in Test Settings:
On the Add new Browser Provider screen, specify the following:
- Enter the Provider Name (this should be the machine that is hosting the Appium server)
- Select the Appium Server radio button
- Enter the Appium Server Address (the IP address where Appium is configured, i.e. your machine’s IP), followed by the port number (default port for Appium is 4723)
- Set a timeout duration in New Command Timeout (the Appium server will be disconnected after the number of seconds specified here)
Then add an iOS device by clicking the Add New button in the Devices section:
On the Add new Device screen, enter the device Name and set the Platform (iOS):
Next we’ll add some Appium Desired Capabilities. These are keys and values encoded in a JSON object, sent by Appium clients to the server when a new automation session is requested. They give the Appium drivers some key information about how you want your test to work, helping to set properties for the WebDriver.
We will add the following four properties:
- deviceName = iPad
- platformName = iOS
- platformVersion = 11.4 (or iOS version installed on iPad)
- Udid = [your device udid]
Follow the steps below to add these properties.
Start by clicking the Add New button in the Properties section:
On the Add new Desired Capability screen, set the Name to deviceName and the Value to iPad:
Then click the OK button.
Add the second property by clicking the Add New button in the Properties section.
On the Add new Desired Capability screen, set the Name to platformName and the Value to iOS:
Then click the OK button.
Add the third property by clicking the Add New button in the Properties section.
On the Add new Desired Capability screen, set the Name to platformVersion and the Value to 11.4 (or the iOS version installed on your iPad):
Then click the OK button.
Add the fourth and final property by clicking the Add New button in the Properties section.
On the Add new Desired Capability screen, set the Name to udid and the Value to the udid of your device (the udid for your device is shown inside iTunes).
Then click the OK button.
Launching Appium Server
Now you are ready to launch Appium Server.
Use the terminal to launch Appium Server. Launch Terminal and navigate to appium directory:
Enter the command:
node . -a [Appium server ip address] -p [port number]
Then press the Return key.
You should see the following message confirming that Appium Server is now running on your machine:
You should always launch the Appium Server before beginning mobile testing in Provar.
You can also re-launch the server to reconnect after a timeout (based on the time you have specified in the Browser Provider’s New Command Timeout).
Creating SFA Mobile Test Cases
Now that you have completed setup you can begin building FSA Mobile test cases.
First select the new Web Browser from the dropdown list in the top-right of Provar Desktop:
Then check you have added the Connection(s) you require for your FSA Mobile testing. If you have already been testing ServiceMax desktop, you can reuse these existing Connections. If not, you can create a ServiceMax FSA testing Connection in the standard way. Refer to Adding a Connection for more information.
Once you have your Web Browser selected and your Connection is set up, you can start creating Test Cases in the standard way.
On the New Provar Test Case screen, make sure the correct Connection is selected for ServiceMax Mobile Testing on iOS and select ServiceMax SFA in Salesforce Application:
Make sure that you leave Launch Test Builder Session ticked, then click the Finish button:
This will launch the Test Builder and open an iPad screen for you to begin mapping test steps.
ServiceMax Field Service App Mobile Support
Once logged into the app, Provar will automatically recognize elements such as the Calendar, Explore options, Create New options and Tasks:
Note that these navigational elements such as Calendar and Explore do not need to be mapped separately. Much like tabs in standard Salesforce, Provar will perform the navigation automatically once the inside screen element is mapped.
All Actions are also supported, as in this example for Action items under Work Orders in Explore:
Example 1: Default Search
Once logged into SFA, you can add test steps in the standard way: select the element to be mapped by right-clicking and selecting Add to Test Case:
Note that the page and fields have been recognized.
Then click Add & Do to execute the step. Once executed it should show as follows:
Below is an example FSA Mobile test case seen from Provar Desktop. The Default Search test step is highlighted:
And in Test Runner:
Example 2: Creating an Event
Launch the Test Builder into the ServiceMax SFA application and navigate to the Calendar view:
As mentioned above, note that a navigational element such as Calendar does not need to be mapped separately. Much like tabs in standard Salesforce, Provar will perform the navigation automatically once the inside screen element is mapped.
Add test steps in the standard way: select the element to be mapped by right-clicking and selecting Add to Test Case for example on the New button below:
Provar automatically recognises the fields on the New Event screen and you can map them in the normal way:
Once the relevant fields are mapped, the Save button is also mapped:
The draft test step above shows the page and elements being recognized automatically.
After clicking Add & Do, the test appears as below:
Here is the same test case seen from Provar Desktop:
And in Test Runner:
Example 3: Attach and Email Documents
This example demonstrates attaching an image file to a Work Order and then sending it by email.
Note that this example will involve emailing the file using Gmail, and currently Provar only supports the use of Gmail on iPad, not other iOS devices. We recommend making sure that Gmail is configured to work on your device prior to completing this email.
Before starting, prepare your image file and place the file to be uploaded under the templates folder inside your Provar project.
On the Edit WO screen, start by mapping the Add link under the Attached Documents header.
Make sure the Interaction Type is set to Attach File and then enter the filepath for the image in the templates folder, e.g. templates/download.jpg:
Then click the Add & Do button.
Once the image file has been uploaded, map the Select hyperlink on the Attached Images/Videos header and execute the step:
Then map a step to check the radio button next to your target image.
You can locate the target row based on image size, name or both, as shown:
Then click Add & Do to execute the step.
To email the file, first make sure that Gmail has been configured on your device. Note that Provar only supports the use of Gmail on iPad, not other iOS devices.
Next, map the envelope icon on the Attached Images/Videos to send an email:
Enter To, CC and BCC details and then click the Add & Do button.
Finally, verify in Gmail that the email has been sent and received successfully with the image file attached.
- 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