Oracle Cloud Quarterly Patch Testing


Client Overview

An American biotechnology company with offices in the United States, South America, Asia and, Europe. They were the first company to provide therapeutics for mucopolysaccharidosis type I. The organization was founded in 1997 with an investment of a $1. 5 million from Glyko Biomedical. Its headquarters are located in San Rafael, California. The products they manufacture are PALYNZIQ® (pegvaliase-pqpz) an injection self-administered enzyme substitution therapy for PKU, Brineura® (cerliponase alfa) for CLN2 Disease, Vimizim® (elosulfase alfa) for MPS IVA, Kuvan® (sapropterin dihydrochloride) tablets and powder for oral use for PKU, Naglazyme® (galsulfase) for MPS VI and, Aldurazyme® (laronidase) for MPS I.

Project Scope

Oracle Cloud Quarterly Patch Testing required the business to test the bug-fixes in new releases and enhancements. Patching is the process of applying modifications to the Oracle Cloud Applications environment. Modifications may be in user interface or in any logic level. Regression testing is required to find bugs in the new releases. In such a scenario,  manual testing is unfeasible. Manual testing can also impact business continuity due to limited testing coverage and human errors. Automating process should be encouraged to effectively patch test.

Business Situation

Oracle releases quarterly Cloud updates composed of new functionality,  customer enhancement requests and previous release bug-fixes.  These updates are mandatory and are applied on a scheduled date that is unchangeable. Clients will update to new releases immediately once the Oracle Cloud launches the upgrade patch. Testing needs to be done to compare the new release with a current patch for any modifications or upgrades. Whether you are in the middle of your implementation or already using Cloud,  understanding the impacts of the latest release on internal business processes is essential to ensuring a seamless update.

Technical Situation

Time for quarterly patch applications in development and production instances is less. Within these short time,  customers need to complete testing,  analyze the results,  and raise issues with Oracle,  if any. Manual testing is not possible at all and it gives some human errors as well. It needs some improved technique to compete the patch testing in a given period of time.


ChainSys deployed Smart Bots in the client environment to achieve the cloud quarterly patch testing. It compared the current patch with the new release too find the difference. Smart Bots fixed this issue by standardizing the template with new release. It reduced the time taken to complete each transaction and provided comparison with historical information.



It reduces the regression testing to merely hours,  enabling faster validation of Oracle Cloud quarterly patch upgrades. Initiating an automation process for patch testing reduces manpower. The consolidated log shows clear details about testing.

Products and Services Used

Smart Bots is deployed for Oracle Cloud Quarterly Patch Testing.


No items found.