Best Practices for Oracle EBS Test Automation

Case I- Record/Playback of Test Scripts  

1.1 Setting up Global timeout: 

The global timeout for EBS scripts should be 90 or more than 90 sec.


  • This recommendation suggests optimizing Oracle EBS application performance by setting the timeout to approximately 90 seconds. However, in scenarios with continuous test process executions and bandwidth consumption, it's advisable to configure the timeout as <=90 seconds. 

1.2 Keyboard and Mouse actions cannot be recorded:  

Opkey recorder does not capture keyboard actions such as Enter, Tab, Up, Down, Right, Left, delete, F1 – F12, Ctrl, shift, alt, Esc, and Right-click. 

1.3 Oracle EBS Submit Process output files cannot be recorded: 

While submitting any process, the state of the process is changed to complete then an output file will be generated in .pdf, .txt, or the Excel files. The generated files can be read by Opkey keywords but can't be recorded.

*Other than above, no specific pre-requisite is required to be followed to perform Record/Playback on Oracle EBS applications  


Case II- Test Creation using keyword-based scripting approach  


Recommended Keywords Libraries/best practices around Oracle EBS test script development 

2.1 SyncForm and SelectWindow keyword: 

Include the SyncForm keyword when transitioning from the web to Oracle Forms and add the SelectWindow keyword when transitioning from Oracle Forms to the web. 


2.2 List of Table keywords implemented for Oracle EBS: 

Below is the keyword list that we can use for Oracle Forms table scenarios.




2.3 Table cell actions by keyword using row no and the column name: 


Record any cell in an Oracle Forms with the recorder, then use the table keyword and the recorded cell object to perform actions on the entire table by specifying the row number and column name. 


2.4 Table Architecture:  

The table keywords operate on visible rows, not the total rows. For instance, if a table has 10 visible rows and you want to add data in the 11th row, provide the row number as 10 since only the visible rows are considered. 

2.5 Dtree object: 

To retrieve the selected value for the Dtree data object, employ the Oracle_GetProperty keyword. Pass only the first recorded step for all items in the dtree; this object will obtain the value from the selected item. For expansion, utilize keyboard actions such as ENTER or the RIGHT arrow key. 


2.6 Oracle_GetProperty keyword: 

Use the Oracle_GetProperty keyword to obtain the runtime properties of any object. Here is the list of implemented properties: 




2.7 To read the text file output of any process:  

If the output of a process is a text file and the Oracle page opens it in the web browser, use SelectWindow to navigate back to the home page first, then use SelectWindow to switch to the text file tab to retrieve the text. 


2.8 For Configurator Test Scripts: 

Transitioning from Oracle EBS Java form to web form, Opkey automatically adds a 'click button' when submitting a process. It's recommended to replace it with 'click button and wait' for proper handling when closing the existing window. 




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article