Oracle Cloud Quarterly Patch Testing


Client Overview

An American biotechnology company that has offices in the United States, South America, Asia,  Europe. They were the first company to provide therapeutics for mucopolysaccharidosis type I. It was founded in 1997 with an investment of a $1. 5 million from Glyko Biomedical. It has headquarters at San Rafael, California. Products manufactured are PALYNZIQ® (pegvaliase-pqpz) Injection self-administered enzyme substitution therapy for PKU, Brineura® (cerliponase alfa) for CLN2 Disease, Vimizim® (elosulfase alfa) for MPS IVA, Kuvan® (sapropterin dihydrochloride) Tablets for Oral Use and Powder for Oral Solution for PKU, Naglazyme® (galsulfase) for MPS VI, Aldurazyme® (laronidase) for MPS I.

Project Scope

Oracle Cloud Quarterly Patch Testing required for the business to test the bug-fixes in new releases and enhancements. The releases follow a quarterly schedule. 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 the updations 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. Automation process should be encouraged to achieve the patch testing effectively.

Business Situation

Oracle releases quarterly Cloud updates composed of new functionality,  customer enhancement requests and previous release bug-fixes.  These updates are mandatory and applied on a scheduled date that is unchangeable once it’s been established. Clients will go for 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 compares the current patch with the new release and find the difference. Smart Bots fixed this issue by standardize the template with new release. It reduces the time taken to complete each transaction and provides comparison with historical information.



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

Products and Services Used

Smart Bots is deployed for Oracle Cloud Quarterly Patch Testing.


No items found.