How do I test the upgrade site during user acceptance testing (UAT)?
Oracle B2C Service
This answer summarizes the best practices recommended by Oracle for user acceptance testing (UAT) during an update.
Getting ready to test
1) In the time leading up to the start of the user acceptance testing (UAT) phase of your update project, work with your internal IT department to setup any needed test servers or test harnesses to facilitate thorough end-to-end testing of all your customizations and workflow using the upgrade site. (Remember: The URL will be different for the upgrade site than for your Production site.) Also, be sure the proper safelistings are in-place in your firewalls, to allow these connections to open without issues. (Review the Oracle B2C Service Infrastructure Requirements documents and reference the Network Requirements section for guidance.)
2) Ensure that your user's workstations are prepared for the update by reviewing the Workstation Requirements section of the Oracle B2C Service Infrastructure Requirements document.
3) Review the Product Documentation and Release Notes for your targeted Oracle B2C Service release, so you are aware of any product changes that may impact how you use the product.
4) If you are using the Pass-Through Authentication (PTA) feature or the Single Sign-On (SSO) feature, you may want or need to work around this security to test the Upgrade site. Please review Testing Single Sign-On (SSO) with Upgrade, Clone or Test site and Testing customer portal end-user PTA with Upgrade, Clone or Test site.
5) Your team should carefully review the Update Guide for your targeted Service Cloud release, to become familiar with how to prepare/perform testing in the Upgrade site (ex. activating mailboxes, enabling CRONs, etc.).
6) Before UAT begins, carefully document the steps for each business critical workflow. This will make verification easier during UAT and, can be used for your next update as well, if the workflow hasn't changed.
Best practices for testing:
1) Test the upgrade site as if it were your production site. Verify any business critical workflows to include e-mail, custom processes and CRON jobs, to ensure these perform as expected.
2) For e-mail testing, set up mailboxes on the upgrade site for incoming and outgoing e-mail (i.e. if part of your business process flow). Refer to Answer ID 2145: Testing email responses from the upgrade site for steps to do this.
3) Be sure to test your external integrations and desktop deployments. In particular, test any Add-In functionality thoroughly to make sure add-ins operate the same way they do on the production site. These areas are extremely important to test since they usually involve systems outside the Oracle B2C Service product. Additionally, verify all integrations using the Connect Common Object Model (CCOM). Verify that the coding within the integration specifies the version of CCOM being used in the call. If the version is not declared in the code, newer product releases will default to the latest version of CCOM available in the product.
4) Verify any end-user pages displayed through an iFrame will still display properly from the upgrade site. This will require some manipulation on your part to pull the page from the upgrade site rather than from your production site.
5) Report any problems or questions to Oracle through our Pregunta al Soporte Técnico link on our support pages. By being in the Auto Update Program, all customizations are built using our managed frameworks. Therefore, Technical Support will address any questions that might arise during your testing. (If there is a technical issue that will impact the update cutover of your site, you can Reschedule the Cutover Date to allow time to resolve the issue.)
6) When submitting new service requests to Oracle B2C Service Technical Support during your (UAT) testing, be sure to provide very detailed replication steps, including screen shots, to enable speedier resolution to your issues.
7) Depending on the level of customization to your site, you may want to review, the changes related to the new release of our product that may impact your site's functionality. The Service Update Notifications report (SUN) available once the Upgrade site is ready for you, describes changes to the product that may result in different behavior with the new release and includes any items that may have been deprecated from the product.
8) File Sync was enabled for all sites participating in the Auto Update Program (AUP) and updating to version 17D (November 2017) or newer, to reduce the change freeze duration for Customer Portal and custom PHP. File Sync allows PHP changes to be made on the production site until 8 hours before cutover. At the 8-hour period leading up to the cutover, files are synced from the production site to the Upgrade site so the PHP changes are not lost when cutover takes place. See Answer ID 9638: File Sync for Oracle B2C Service Update for more information.