Guide in ServiceMax Testing
ServiceMax is a complete field service software solution built on the Force.com platform. It includes features such as Installed Base Management, Scheduling & Dispatch, Service Requests & Work Orders, and more. This documentation serves as a guide in ServiceMax testing.
ServiceMax also has a mobile application, the Field Service App (FSA), which Provar supports. For information on how to test the FSA mobile application, please refer to ServiceMax FSA Mobile Testing.
Note: As of version 1.9, Provar supports both the ServiceMax desktop and the ServiceMax mobile applications. pre-1.9 versions support desktop ServiceMax only.
ServiceMax Desktop Setup
To begin the guide in ServiceMax testing, create a Salesforce Connection in the standard way first.
Refer to Adding a Connection for more information.
Creating ServiceMax Test Cases
Once your Connection is added, you can start adding ServiceMax test cases in the standard way. Make sure you select your ServiceMax Connection and select the application as ServiceMax from the dropdown.
This will open the test case in the ServiceMax application.
Refer to Creating Test Cases for more information.
ServiceMax Work Orders
Provar automatically recognizes the Work Order object and its fields when mapping test steps.
Here is an example of test step mapping on the New Work Order page.
Here is an example test step mapping of a record in the Recent Work Orders table on the Work Order tab.
Here is an example ServiceMax test case including both of the above steps, as seen from Provar Desktop:
Service Flow Wizards
Provar supports mapping all Service Flow Wizards, including Field Service and WO Wizard actions.
Example 1: Close work order
Below is an example test mapping a Close Work Order flow.
After right-clicking on Close Work Order and selecting Add to Test Case, the following draft test step appears:
Note that the Work Order View screen and an embedded page representing the Service Flow Wizards have been recognized automatically. The Close Work Order option has also been recognized automatically.
Clicking Add & Do on the draft test step navigates the user to the Close Work Order page, where all fields are recognized automatically.
The below test step is an example step entering a value into the Work Performed field:
Once Add & Do is clicked on the above step, the step is executed as follows:
Here is the test as it appears in Provar Desktop:
Example 2: Edit Work Order Lines – Usage
Below is an example test mapping an Edit Work Order Lines – Usage flow.
After right-clicking on Edit Work Order Lines – Usage and selecting Add to Test Case, the following draft test step appears:
Note that the Work Order View screen and an embedded page representing the Service Flow Wizards have been recognized automatically. The Edit Work Order Lines – Usage option has also been recognized automatically.
Clicking Add & Do on the draft test step navigates the user automatically to the Manage Work Order Usage page:
The below test step is an example step entering a value into the Priority field:
Once again, the page and the target field are recognized automatically.
Once Add & Do is clicked on the above step, the test moves on to the Add Parts button in the Lines section of the page:
The correct part is then located via the ServiceMax Lookup:
Note that Provar recognizes the search results as a table with results located on a specific Product Name value:
Once the correct part is located and selected, the Save button is mapped:
Here is the completed test case as seen from Provar Desktop:
ServiceMax FSA Mobile Testing
As of Provar version 1.9, Provar also supports testing ServiceMax’s Field Service Application for iOS. Refer to ServiceMax FSA Mobile Testing for more information.
- 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
- 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
- Provar Desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- 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
- Generate Test Case
- List Compare
- Page Object Cleaner
- 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 Automation
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- Provar Manager
- 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
- 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- 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
- Internationalization Support
- List and Table Testing
- Salesforce Console Testing
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) Locator Support
- Salesforce Release Updates
- Visualforce Testing
- Best Practices
- Configurations and Permissions
- Error Messages
- Licensing, Installation and Firewalls
- Test Builder and Test Cases
- Release Notes