Skip to main content

Oracle ERP Cloud is a True cloud SaaS and modularized ERP (Enterprise Resource Planning) application that enables continuous digital innovation without end-of-life and implementation disruption required for today’s business. Compared to other ERPs, Oracle emphasizes continuous innovation across all applications through Quarterly updates that allow continuous innovation based on the latest technologies and market dynamics. Oracle ERP Cloud is a single solution means no need to migrate if the company grows or requirements evolve. Enterprises can deploy the same applications across HQ, subsidiaries, and business units regardless of size.

In this article let us walk through:

What is Oracle ERP Cloud?

Oracle ERP Cloud is a suite of flexible modular SaaS applications and a unique approach compared to other leading cloud ERPs. All modules are built on unified data; enterprises can optimize processes and analyze data across departments. Modularity allows for diverse business models and priority-focused implementation. Like other Cloud ERP providers, Oracle ERP cloud is not just ERP-centric but a comprehensive set of flexible modular SaaS applications.

Compared to leading cloud ERPs, Oracle ERP is designed to provide the best user experience and seamlessly fit the digital era. However, Oracle ERP Cloud’s complex upgrades/patches process in the form of monthly maintenance packs, quarterly upgrades, and patches throws many challenges for organizations and resources.

Project Teams Organization
Business Process Owners (BPOs) and SMEs Time to market
Oracle ERP Cloud Functional Consultants (FC) Risk management
Oracle ERP Cloud Technical Consultants(TC) Total cost of quality
Quality analysts / Testing Consultants Business Assurance
Release Managers and the whole crew Continuous improvement

What matters to a tester in testing Oracle EPR Cloud?

Continuous Learning and Zero-knowledge gaps:

Oracle ERP Cloud follows a quarterly publication cycle each year that significantly impacts an instance with over 600 new functionalities per year, code optimization, business process optimization, and feature updates/ enhancements. With four feature updates each calendar year, this frequency compares to the typical 12 to 18 months cycle for other on-premises deployments.

Is it redundant Knowledge Transfer (KT) activity from BPO/SME/FC/TC to the tester? What if BPO/SME / FC/Manual Tester can build a test process using some simple English?

Impact analysis (Functional & Technical impact)

Oracle ERP Cloud’s complex upgrades/patches in the form of monthly maintenance packs, quarterly upgrades, and patches creates a huge functional and technical impact on both Oracle cloud instance and test suites. In addition, The tester will observe script failure during test execution because of dynamic elements and Rule-driven configurations. The tester must perform a thorough impact analysis on both

  • Functional (Features and Business Process) Level: Primary and branch paths, including the decision logic validation of each workflow
  • Technical level: APIs and CIDER (Configurations, Integrations, Data, Extensions, and Reports)
Impact analysis-ACCELQ

OPT-IN Expiration:

Along with FC/SMEs, the tester must keep an eye on the continuous monitoring mechanism on OPT-IN features with future expiration to keep the test suite ready for further benefits. In addition, the tester has to keep the test suite ready based on features initially enabled via the opt-in user interface for both SMALL Scale UI or Process-Based Feature and LARGER Scale UI or Process-Based Feature.

OPT IN Expiration- ACCELQ Oracle

Security Assurance

As features are continuously added to the instance, it is essential constantly update Security Scenarios to assure security at a different level.

  • Security: The tester should focus on security assurance, User Confidence, and business integrity through a focused security regression run during patches/upgrades/ releases. The test has to update the test cases/data to test CRUD (Copy/download, read/view, update/alter/change and delete/erase) operations. The security test suites should be designed to ensure authenticated access, sensitive data protection, user configuration validation, verify account management and verify report modification
  • Role validation: The tester should ensure all applicable job roles, positions and titles are appropriately identified and implemented
  • Responsibilities verification: The test should thoroughly validate the correct mapping of responsibilities to roles which is critical for security and workflows  
Security Assurance-ACCELQ Oracle

Test operations and management:

Today, all leading test automation tools have integrations with various test management through a plug-in, but it’s a cakewalk for a tester through a unified solution by bringing test management and testing into one platform. Few of the hectic moments for a tester during a release are

  • Test suite impacts analysis against technical and functional changes Test suite management for different testing needs, including risk-based, business process-driven, rollout testing focused on I18N and I11N (Localization vs. Internationalization testing), Smoke suite.
  • Test suite orchestration based on Scenario Planning and Scenario modeling, Business requirement, Regression type, in-sprint test suites,
  • Test enablement coordination with ops team for test environment provisioning and test data refresh for every test run
  • Traceability and change management between the business requirement to test scenarios
  • Custom reporting-based roles and test types

Initially, the Failure rate will be higher in initial runs/regression cycles during upgrades/ patches because of instance issues and configuration changes. Therefore, the tester should adopt a robust defect management practice and a proper differentiation process for bugs, defects, issues, and errors. Tester is also responsible for defect closure.

Proactive preparedness:

By default, non-production Oracle Cloud environments (e.g., training, quality, etc.) are updated on the first Friday of the quarterly update month, and Production environments are updated on the third Friday of the quarterly update month. However, Proactive preparedness is much needed for both tester and automation solution providers as Oracle’s users/customer has the flexibility to choose quarterly update in 3 cycles:

  • January/April/July/October
  • February/May/August/November
  • or March/June/September/December

A must have capabilities in an Automation Solution:

  1. Truly no-code low code to enable BPOs, SME, and FC to build automation scenarios
  2.  AI at core for self-healing, intelligent test suite orchestration, and visual validation
  3.  One solution for end-to-end automation Oracle Alta UI, REST APIs, File-Based Data Import (FBDI), desktop-based scenarios, and data validation
  4.  Unified platform both test management, test automation, and defect management
  5. Oracle ERP Cloud Native capabilities to ensure cost and effort reduction
  6. Release alignment with monthly maintenance packs, patches, and quarterly upgrade
  7. Business assurance through a comprehensive view of Oracle ERP Cloud along with its downstream and upstream applications
Mani kumar Image

Manikumar Sarma Peri | Director- SaaS Solutions at ACCELQ

Manikumar specializes as seasoned presales professional with deep capabilities in solution architecting and design for large-scale ERP implementations and Quality engineering. He drives pursuits with philosophy: “Thank Business – Configure Technology – Deploy Solution.”

   

This Might Also Interests You...

Get started on your Codeless Test Automation journey

Talk to ACCELQ Team and see how you can get started.

Close Menu