--- schema_version: "1" id: c3952a77c6495f66b95b77981d7e213a0a0d1cee64fdf581b4d6590f8ca9a8a4 title: Resources for Testing Beta Versions of the Field Service Mobile App collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/mfs_testing_beta_resources.md canonical_url: https://help.salesforce.com/s/articleView?id=service.mfs_testing_beta_resources.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 55059b760ec7e4dac25995d7ecfa9e5d1879674cd88196de91a34466eec87a2e description: Salesforce provides resources to help you use the beta program to test the latest Field Service mobile app major releases and patch releases. products: - Field Service release: "264" --- # Resources for Testing Beta Versions of the Field Service Mobile App Salesforce provides resources to help you use the beta program to test the latest Field Service mobile app major releases and patch releases. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.
To access the Field Service mobile app, users need the Field Service Mobile user license.
## Sandboxes When you have the mobile application beta version installed, you’re ready to start testing. The most effective way to test beta versions of the mobile app is via the latest Salesforce sandbox test environment. We suggest that you keep an existing sandbox instance up to date, so that you can perform testing using data specific to your unique configurations and needs. Sandbox test environments are also an excellent resource when interacting with our support teams for any issues you encounter while consuming our beta versions. For instructions on how to obtain and use sandboxes for testing, see [Sandboxes: Staging Environments for Customizing and Testing](https://help.salesforce.com/s/articleView?id=platform.deploy_sandboxes_parent.htm&type=5&language=en_US). If you’re a first-time user or have to start a Sandbox from scratch, check out [Where Do I Start with Field Service](https://help.salesforce.com/s/articleView?id=service.fs_landing.htm&type=5&language=en_US) to set up for testing. ## Testing Major Releases Major releases introduce new features, performance improvements, UI or UX updates, and API changes. We hope these features improve your work and business, but the changes can sometimes also create configuration conflicts. Although we strive to maintain backward compatibility, new releases can unexpectedly affect customizations that are specific to your implementation. The best way to protect your implementation is through beta testing. To benefit most from the beta, create a test plan based on the most recent changes to the Field Service mobile app. Consider which features or Salesforce Field Service products you use most or that are most important to your business. To identify changes that impact your most crucial processes, focus your testing by reviewing Salesforce release notes each release. Here’s where you can find release notes pertaining to Field Service: - [Salesforce Release Notes](https://help.salesforce.com/s/articleView?id=release-notes.salesforce_release_notes.htm&language=en_US) alert you to the features being released for all Salesforce products. - Within the Salesforce Release Notes, the [Salesforce Field Service Release Notes](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice.htm&language=en_US) cover the Field Service features specifically, and includes a special section for the latest features released for the [Salesforce Field Service Mobile Release Notes](https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_mobile.htm&language=en_US). These notes alert you to what’s changed in the mobile application. ## Testing Patch Releases Patch releases are deployed only to resolve specific issues discovered on an existing production release. Beta versions for patch releases are made available at least one week before changes to the app are deployed. When consuming a patch release, you can isolate your testing to the specific purpose of the patch release. ## Recommended Test Areas In addition to reviewing the Salesforce Release Notes and testing potentially affected areas, it’s important to review parts of the application that you’ve customized or extended for your specific needs. We suggest starting your testing with Lightning Web Components and flows, because they’re the most commonly customized features. - [Lightning Web Components](https://help.salesforce.com/s/articleView?id=service.mfs_overview_lwc.htm&type=5&language=en_US) - [flows](https://help.salesforce.com/s/articleView?id=service.mfs_flow_considerations.htm&type=5&language=en_US) Also consider these frequently customized items when you plan for testing. - [Mobile Settings](https://help.salesforce.com/s/articleView?id=service.mfs_settings_details.htm&type=5&language=en_US) - [Custom Actions](https://help.salesforce.com/s/articleView?id=service.mfs_actions.htm&type=5&language=en_US) - [Customized Push Notifications](https://help.salesforce.com/s/articleView?id=service.mfs_push_notifications.htm&type=5&language=en_US) - [Deep Linking](https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_dev_mobile_deep_linking.htm) - [Custom Triggers](https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_dev_custom_triggers.htm) ## Lightning Web Components (LWC) Test Harness If you use Lightning Web Components (LWC), the [LWC Offline Test Harness](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/dx_harness_app.htm) (Test Harness, for short) is a lightweight testing and debugging app. Test Harness lets you iteratively develop, test, and debug Lightning web components for use in LWC Offline-based mobile apps. The streamlined app experience accelerates the interactive development lifecycle, making it easy to quickly test incremental improvements and fixes to your mobile LWCs. ## More Tools for Debugging Lightning Web Components We suggest using your web browser to debug Lightning Web Components. You can find resources and a tutorial in the [Mobile and Offline Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/quickstart_lwc_debugging.htm). To test your sandbox environments, you can also use the [emulator](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/quickstart_lwc_action_android_setup.htm#quickstart_lwc_action_android_setup_install_app) for Android and the [simulator](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/quickstart_lwc_action_ios_setup.htm#quickstart_lwc_action_ios_setup_install_app) for iOS. If the simulator and emulator are installed, you can directly access debug builds for [iOS](https://sfdc.co/fieldservice-mobile-app-ios-simulator) and for [Android](https://sfdc.co/fieldservice-mobile-app-android-simulator). ## Trailblazer Communities and Customer Support If you require further support, don’t worry, we’ve got your back! [Salesforce Trailblazer Communities](https://trailhead.salesforce.com/en/trailblazercommunity) can also help you prepare for and implement testing. These communities include everything from training material to ways to connect with other users. And, if you encounter an issue or require additional support, contact [Salesforce Customer Support](https://help.salesforce.com/s/articleView?id=000384365&type=1&language=en_US). If you find an issue only happens on the beta version, share about it in your case details.