Functional testing and release of Customer Engagement configuration
Key Takeaway
To show updated page layouts and Lightning record pages in the Life Sciences Cloud mobile app, generate a new metadata cache for the affected users' profiles. Test early on consistent devices, and release Customer Engagement features in phases.
Functional testing and release of Customer Engagement configuration means proving that what you built works for field users before it goes live. Field users work in both the Life Sciences Cloud org on the web and the Life Sciences Cloud mobile app, so testing covers both. Salesforce's project best practices stress testing early and continuously, keeping test conditions realistic and consistent, and releasing features in phases so each layer rests on a stable foundation. Configuration changes reach the mobile app through a metadata cache that you generate.
Test early and continuously
Salesforce recommends validating all tests on every push of code to a dev branch, so problems surface continuously instead of as surprises at go-live.
Integration testing covers both the Life Sciences Cloud mobile app and the Life Sciences Cloud org on the web. Run it well before client user acceptance testing (UAT), because integration testing too close to UAT leaves too little time to resolve the problems it finds.