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.
ServiceMax also has a mobile application, the Field Service App (FSA), which Provar also 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 application and the ServiceMax mobile application. pre-1.9 versions support desktop ServiceMax only.
ServiceMax Desktop setup
Begin your ServiceMax testing by creating a Salesforce Connection in the standard way.
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 that 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 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 of all Service Flow Wizards, including Field Service actions 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 has been recognised automatically, as well as an embedded page representing the Service Flow Wizards. The Close Work Order option has also been recognised automatically.
Clicking Add & Do on the draft test step navigates the user automatically 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 has been recognised automatically, as well as an embedded page representing the Service Flow Wizards. The Edit Work Order Lines – Usage option has also been recognised 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:
Note that once again the page and the target field is 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 the testing of ServiceMax’s Field Service Application for iOS. Refer to ServiceMax FSA Mobile Testing for more information.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- 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
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- 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
- Circle CI
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server (Beta)
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Service Cloud console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes