In our previous post, we demystified the Oracle Cloud Apps quarterly patching process.
Testing the quarterly patch is a joint effort by both IT and business users. The fundamental requirements for the Quarterly patching process are :
-
Patch Release Schedule: knowing patch release date to plan for the quarterly
patch testing -
What's New: information on new features and capabilities in the quarterly patch. The
details of the latest patch are available on the Oracle Cloud Readiness website well in
advance. So, one should timely check on the features to identify the upcoming updates,
which also helps create the test cases -
Opt-In Expiration: One should be aware of the features falling under the
"Opt-In Expiration" category in the upcoming quarterly patching process to plan for testing - Test Case Category:
- Regression: Common test cases with every quarterly patch
- Upgrade Specific: New Test cases specific to the quarterly patch, upcoming features, and capabilities in the quarterly patch
- Opt-In Expiration: Test cases for features automatically migrated to production from the previous release
-
Quarterly Patch Application: Quarterly patch gets implemented in the Non-Production instance first and then in the Production instance. You have a two-week window to execute all the test cases before the patch gets applied to the PROD instance. All the executed test cases must PASS before the patch gets applied to PROD. In case of any failure, you should raise an Oracle SR and put the PROD patch application on hold
Triniti outlines some of the best practices for creating the test cases and testing schedule for the Oracle Cloud Quarterly Patching process:
-
Use Triniti's Template to create a quarterly patching schedule
-
Prepare the test cases well in advance, based on the quarterly patching schedule. Use Triniti's Template to create test cases