Customers often ask, “What should I test after I upgrade my EBS database?” Your environment is, by definition, unique to you, with your own architectural configurations, setup data, and customizations. You should always concentrate your testing efforts on the areas that may differ from our generic EBS tests. Until now, our generic common-sense answer has always been, “Test what is important to your business.”
Our Quality Assurance group in EBS Development has just published some guidance on the things that you might consider adding to your post-upgrade test plans:
They discuss things such as memory-intensive concurrent requests, compliance with new standards for initialization parameters, custom workflows, and more.
Your feedback is welcome. I’ll make sure that the Note’s authors are notified if you drop me an email or post a comment here.
Related Articles
- Creating a Maintenance Strategy for Oracle E-Business Suite
- Identifying Recommended Patches for E-Business Suite Environments
- What’s the Best Way to Patch an E-Business Suite Environment?
- Top 5 Myths About Patching Apps Environments
- Top Five Errors Customers Make When Maintaining E-Business Suite 12 (Part 6)