BEST PRACTICES IN OATS

EBS Issues:

1.       Not able to launch forms –

Check java path set In environment variables. Make sure it points to latest java update path. The latest java path can also be found under Control Panel -> Java -> Java tab -> Click on view button

Settings:

1.       Openscript recording issues –

By default “Direct connection to the internet” would have been selected in Open script. Enter HTTP Proxy details in “Network Connections” by selecting “Manual Proxy Configurations” option which might help with Open script connecting to portals and recording.

Note: Select the checkbox “Use this proxy server for SSL” if the proxy details is applied for SSL config as well

Navigation: Window -> Preferences ->General -> Click on ‘Network Connections’

2.       Browser startup timeout  –

By default it is set as 60 s. Openscript would fail to record if the browser fails to launch in 60 s due to slowness of the environment. It is better to increase the timeout.

Navigation: Window -> Preferences ->Openscript -> General -> Click on ‘Browsers’

3.       Record and playback browser option –

Some apps have browser limitation. Select the record or playback browser instance as per your specifications.

Navigation: Window -> Preferences -> Openscript -> General -> Click on ‘Browsers’

4.       Encrypt data –

It is a best practice to encrypt data’s like passwords. Select the option “Obfuscate script data” in the below navigation. In this way , Openscript will record the data in encrypted form which will be stored in script.

Navigation: Window -> Preferences -> Openscript -> General -> Click on ‘Encryption’

5.       Add repository –

Repository points the Openscript to a location where the scripts created will be saved.

Navigation: Window -> Preferences -> Openscript -> General -> Click on ‘Repository’.

6.       Forms Timeout issue –

This is a predominant issue which users have when recording EBS forms. Timeout issue occurs gets logged in console while launching forms. This issue occurs if the forms are not launched within the stipulated time set in below navigation (which is usually set as 60s or 30s by default) . It is a best practice to increase the timeout for “Forms Startup Timeout”, “Forms Action Timeout”, “Forms Response Timeout”.

Navigation: Window -> Preferences ->Openscript -> Playback -> Click on ‘Oracle EBS/Forms functional’.

7.       Objects Timeout issue –

This is a predominant issue which users have when recording EBS forms. Timeout issue occurs when a form takes a longer time to launch due to issues like environment slowness and hence Openscript fails to identify objects or fields. This issue occurs if the forms are not launched within the stipulated time set in below navigation (which is usually set as 60s by default) . It is a best practice to increase the Object Timeout.

Navigation: Window -> Preferences ->Openscript -> Playback -> Click on ‘Web functional’-> Expand ‘Object Timeout’ )

8.       Step groups –

This will basically group steps while recording. This setting can be used to control the step group creation at various intervals. Step groups helps with debugging since it captures window name where the actions are  performed. Step group can be given meaningful names based on the actions done or captured in the step.

By default “Forms Functional Test” option would have been selected. Select the option “Based on time threshold” and set “Threshold” value for 1 or more sec (This will create step group accordingly).

Navigation: Window -> Preferences -> OpenScript -> Step Groups -> <Select the desired module>

9.       Playback issue: Script is not pausing as per think time added to script –

This is due to the think time settings that is set as 0 to 10 second by default and hence the script will pause for a maximum of 10 sec only irrespective of the think time added to script.

By default “VU Pacing (Think Time)” field will have the value selected as “Recorded” from the dropdown. The “Minimum” value set is “0” sec and “Maximum” value set is “10” sec. Update the “Maximum” value to 60 seconds or more.

Navigation: View -> Openscript Preferences -> Select “Playback”

1.   Adding Assets –

Make sure to select relative path as “Relative to current script” (Under ‘Save path’ section) while adding assets to scripts as this will avoid the prompt of “not finding the databank file”.

1.   Enable line number in Text Editor –

Line number is helpful for debugging as script failure log points to line number where the script fails.

Navigation: Window -> Preferences -> Expand General -> Click on “Text Editors” -> Select “Show line numbers” checkbox. Click on “Apply” button to save changes.

Helpful Tips:

1.       Installing OATS and QTP in same machine –

It’s better to install the applications in different machines since it will throw java conflict issues while recording

2.       How to playback with no delay (disabling recorded think time) –

By default “VU Pacing (Think Time)” field will have the value selected as “Recorded” from the dropdown. Flip the value to “No Delay” from the dropdown and playback script. The script will not consider any think times and it will execute without any delay.

Navigation: View -> Openscript Preferences -> Select “Playback”

  

 . No matter if it is a web application or forms application, normal exit operation should be recorded in the script. If web actions and forms actions coexist in the transactions being recorded, we should exit the web application after exiting the forms application. It is not correct that we directly stop the recording after we finish doing the forms business, which will cause a large amount of invalid sessions, which will affect the performance of the server and the accuracy of test result.

5.       Make sure to delete the cookies that sometimes gets recorded while navigating through steps before play backing the script.

6.       Debugging script code –

Use ‘Edit -> Find/Replace’ to substitute values or variables in a script as there could be more than one variable for substitution. This ensures that nothing is missed.