Rolling out a new business-critical application requires careful testing to ensure it supports real-life business processes correctly. But when it comes to implementing Oracle Cloud ERP and its upgrades there may be an inclination to depend a bit too blindly on test automation, without considering the possible risks and challenges.
Part of the reason for this tendency is the continuous innovation model of the Oracle Cloud ERP. Updates of the solution’s functionality and features, as well as bug fixes, are provided monthly as consolidated suite-wide patches for implementation even while the system is running. And every single line of custom code that interacts with the database is bound to be affected in some way.
The most intense testing action, therefore, is covering the regular releases mandated by Oracle. And for that, we need speed and scalability. Test automation, launched on day one, sounds like a great solution.
That’s why we are hearing about many teams jumping right into testing Oracle Cloud ERP deployments using automation suites. After all, many people reason, Oracle already tested this SaaS application very carefully, so we can safely assume there will be no big failures or unpleasant surprises.
The problem with that kind of assumption is that test automation is designed to validate regression against a stable baseline. Test automation suites are not actually designed to evaluate new deployments and new processes. That means a failure registered when testing a new deployment may not be as clear an indication of a problem with the application or upgrade as it may seem. It could simply be an error in the automation asset itself, such as a faulty navigation sequence, inadequate test data, incorrect interpretation of pass/fail results, and the like.
These types of problems can be detected by applying the automation suite in a pre-tested stable environment. In that case, any failures are clear indicators of a weakness in the automation tool, rather than an application failure or even a false alarm.
So, for your next greenfield cloud SaaS deployment, plan on using a platform that provides cross-functional manual testing that mirrors your real-world end-to-end business processes. Then, given the increasing complexity of technological innovations, you will need a comprehensive testing workflow including people who are likely to actually use the solution. Their practical understanding of real-world scenarios can reveal hidden vulnerabilities and ensure the final product meets your organization’s business requirements. And for that, you’ll need effective and accelerated collaboration between IT and business users, in order to avoid overburdening your resources and wasting time.
When your manual test acceleration solution helps your teams quickly and efficiently evaluate your migration to a new Oracle Cloud ERP system, you are actually ensuring the ongoing success of your business.