Oracle EBS, short for Oracle E Business Suite, is a set of business applications used by thousands of companies to run finance, purchasing, inventory, manufacturing, order management and human resources. Because so much daily work depends on it, every change to the system needs testing. Doing those tests by hand is slow and easy to get wrong. This guide explains, in plain language, how to plan and automate Oracle EBS testing so that updates and patches go in with less risk.
We have also updated the facts. The old version of this post said Oracle pushes weekly upgrades with more than a thousand changes. That is not how Oracle EBS updates work, and we explain the real cycle below.
Table of Contents
Why Oracle EBS Needs Regular Testing
Oracle EBS 12.2 is the current release. Since 2018 Oracle has followed what it calls a Continuous Innovation model. Instead of a big new version every few years, it adds features through updates to 12.2. The latest of these, 12.2.15, arrived in 2025. In March 2026 Oracle said it will keep Premier Support for 12.2 running through at least December 2037, so many companies will keep using the suite for years.
On top of feature updates, Oracle releases security fixes called Critical Patch Updates four times a year, in January, April, July and October. Companies also make their own changes: new reports, custom forms, workflow rules, integrations with banks or tax systems, and new users and roles.
Each of these changes can break something that worked yesterday. A tax rule may stop applying, an invoice approval may get stuck, or a report may show the wrong totals. Testing catches these problems before they reach the business.
Manual Testing vs Automated Testing
In manual testing, people follow written steps, click through screens and check the results. It works for small changes but has clear limits:
- It takes a lot of time from finance, supply chain and HR staff who have their own jobs to do.
- People skip steps when they are rushed, especially near the end of a patch window.
- Coverage is usually thin, so rare but important cases go untested.
- Results are hard to repeat and compare from one cycle to the next.
Automated testing uses software to run the same steps and check the results. Once a test is built, it can run again and again at little extra cost. That makes it ideal for regression testing, which means checking that existing functions still work after a change.
What to Automate First
You do not need to automate everything at once. Start with the processes that would hurt most if they failed and that are run most often.
Core business flows
Good first candidates include procure to pay, order to cash, record to report and hire to retire. These flows touch many modules, so they catch a wide range of problems. For example, a procure to pay test might create a requisition, approve it, raise a purchase order, receive goods, match an invoice and make a payment.
Security and roles
Patches and setup changes can alter what users are allowed to see or do. Automated checks that log in as different roles and confirm their access help prevent both blocked users and unwanted access.
Integrations and reports
Interfaces with banks, tax engines, e commerce stores and data warehouses often fail silently. Tests that send sample data through these links and compare the output can save days of clean up later. Key reports, such as trial balances or ageing reports, can be compared against expected figures.
Steps to Build an Automation Plan
- List your processes. Write down the main business flows, who owns them and how often they run.
- Rank by risk. Score each flow by business impact and by how often changes touch it.
- Prepare test data. Use a copy of production with sensitive data masked, or a stable set of test records that can be reset.
- Choose a tool. Match the tool to your screens, skills and budget (see below).
- Build a small pilot. Automate five to ten flows, run them on a real patch cycle and measure the time saved.
- Grow in stages. Add more flows each quarter, guided by where defects were found.
- Maintain the tests. Review failed tests quickly and update them when processes change, so the suite stays trusted.
Choosing a Testing Tool
Oracle EBS mixes two kinds of screens. Newer pages run in the browser as HTML, while many older forms are built with Oracle Forms and run through Java. Some general web testing tools work well on the HTML pages but cannot read the Java forms. When you compare tools, check these points:
- Support for both HTML pages and Oracle Forms.
- Whether business users can build tests without much coding.
- Ready made test steps for common EBS flows.
- How easily tests can be updated after an Oracle update changes a screen.
- Reporting that shows clear pass and fail results with screenshots.
- Total cost, including licences, training and upkeep.
Options range from open source frameworks, which are free but need skilled engineers, to commercial platforms built for packaged business software. Ask vendors for a trial on your own system rather than relying on demos. Automation in other parts of a business follows similar rules, as our posts on marketing automation software and automating RFP management show.
Testing Around Patches and Updates
Oracle EBS 12.2 uses online patching, which applies most changes while users keep working and then switches over in a short cutover. This reduces downtime but does not remove the need to test. A practical cycle looks like this:
- Apply the patch or update to a test copy first.
- Run the full automated regression suite overnight.
- Ask business owners to check only the failures and any new features.
- Fix, retest and then schedule the production cutover.
- Run a short set of smoke tests in production straight after cutover.
Lining this up with Oracle’s quarterly security patches gives a steady rhythm that teams can plan around.
Common Mistakes to Avoid
- Automating unstable processes that are still being redesigned.
- Writing very long tests that are hard to fix when one step changes.
- Ignoring test data, which leads to tests that fail for the wrong reasons.
- Leaving tests unowned, so failures pile up and people stop trusting them.
- Expecting automation to replace all manual checks. People are still needed for new features and judgement calls.
Who Should Own Oracle EBS Testing?
Testing works best as a shared job. Business process owners know what the right result looks like, so they should define what each test checks. A small central team, often called a testing centre of excellence, can build and maintain the automated tests, choose standards and run the suite on each cycle. IT and the database team look after test environments, data refreshes and patch schedules. When one group tries to do all of this alone, tests tend to drift away from how the business really works.
Measuring the Benefits
Before you start, record how long a full manual regression cycle takes today, how many people it needs and how many defects slip into production. After automation, track the same numbers. Useful measures include hours saved per patch cycle, the share of key flows covered by tests, the number of defects found before go live and the time from patch release to production. These figures help decide where to invest next and show whether the effort is paying off.
The Role of AI in EBS Testing
Newer tools use artificial intelligence to suggest tests from process logs, repair tests when a screen changes and spot unusual results. These features can cut upkeep, but they still need human review. India’s large IT services sector is a major provider of this kind of work; read more in our post on how India is becoming a global AI superpower.
Write each test so it can run on its own, with its own data, rather than depending on the result of another test.
Keep a simple dashboard of test runs, pass rates and defects found. It helps show the value of automation to managers and auditors.
Store test scripts in version control, just like code, so changes are tracked and can be reviewed.
What We Changed From the Old Post
The old post was a sponsored piece that promoted one testing vendor, repeated its marketing claims and linked to its website several times. It also wrongly said Oracle releases weekly upgrades. We removed the vendor links and claims, corrected the update cycle, added Oracle’s support timeline to 2037, and rewrote the post as a neutral, step by step guide.
Frequently Asked Questions
How often does Oracle EBS change?
Oracle issues security patches every quarter and adds features through 12.2 updates. Your own custom changes add more.
How long will Oracle support EBS 12.2?
Oracle has committed to Premier Support through at least December 2037.
Can all Oracle EBS tests be automated?
Most repeatable regression tests can. New features and judgement based checks still need people.
Where should a company start?
Start with high risk, frequently used flows such as procure to pay and order to cash.