What Should I Test After a Quarterly Update?

Oracle has thoroughly tested the product for the enhancements and corrections included in the update. Oracle has also run a wide range of regression tests against the product.

Your Oracle Cloud Application has been configured for your unique business requirements, so your test plan will be unique to your business. You should focus on validating your current configuration before you try out any of the new features available in an update. The point of this testing is to validate your CURRENT configuration to make sure that the update didn’t cause some unexpected behavior to your unique configuration. This IS NOT the time to start enabling the new features available in the update.

We recommend that you test your key business processes on the new update. These processes should include all steps and navigation and might include various functions and user roles. You should include a test of the "Features Delivered Enabled" in the Feature Summary table of the What’s New guide, if they apply to you. Also, you should also include a test of "Expired Opt In Features" in the What's New Features with Opt In Expiration.

Areas to Include in Your Test Plan

• Integration tests confirming APIs (such as XML, REST) still work and exercise your agents and back end processes
• Third party external systems (such as rating, distance and service time engines)
• Key business process flows for various roles in your organization
• Critical custom reports
• UI tests that cover users’ day-to-day activity and address screens that trigger agent actions
• Custom workflows including saved queries and direct SQL updates
• Automatically available UI
• Performance – test your key flows using production volume
• New enhancements that will apply to you (only after testing of your current configuration)

We strongly encourage clients to create automated tests to maximize coverage and streamline the test process.