C Troubleshooting

This chapter provides information and possible solutions to known issues in OpenScript.

C.1 Installation

In some instances, the OpenScript Internet Explorer and/or Firefox browser plug-ins fail to install properly. You can manually install and uninstall Internet Explorer and/or Firefox browser plug-ins using batch files provided with OpenScript to resolve the issue.

The following batch files are located in <installdir>\OpenScript

InstallBrowserHelpers.bat
UninstallBrowserHelpers.bat

Usage: file.bat installation path [install|uninstall] [IE|FF|both]

The following example shows the usage and default values:

InstallBrowserHelpers.bat C:\OracleATS\OpenScript\ install both

Note:

On Windows 2000 systems, the InstallBrowserHelpers.bat installation does not detect that the .NET Framework 2.0 is installed and will attempt to reinstall it, which may cause an installation failure for the .NET Framework 2.0. However, the .NET Framework 2.0 is installed during the initial OpenScript installation and should be present on the system. Check Add/Remove Programs in the Control Panel to verify the .NET Framework 2.0 installation.

See the remarks in the batch files for additional information.

C.2 OpenScript Script Execution in Oracle Test Manager

The following additional steps are required in order to run the following types of OpenScript scripts from Oracle Test Manager:

Siebel Functional
Oracle Forms Functional
Web Functional scripts that rely on system input events, such as key press or mouse click

It is necessary to run these scripts using an interactive desktop of a named Windows user account that is always logged in.

For Siebel and Oracle Forms, the named user's account must have visited the Siebel or Oracle Forms site at least once to ensure that all necessary ActiveX controls and plug-ins are installed in the named user's browser.
On the Oracle Test Manager agent machine that will run the scripts, stop the "Oracle Agent Starter Service" and configure it to start manually.
On the Oracle Test Manager agent machine, login as the named Windows user account that will run the scripts. From a command prompt, run:
```
C:\OracleATS\agentmanager\bin\AgentManagerService.exe -c 

  C:\OracleATS\agentmanager\bin\AgentManagerService.conf
```
where C:\OracleATS is the OATS installed folder.
The named user account must remain logged into the system at all times that scripts will be run.

C.3 Manual Installation of Firefox Extension

In some cases, if Firefox was installed by upgrading from previous version, when recording scripts of Web Functional Test with Firefox, Firefox is launched but Firefox does not have the Web DOM extension and Web navigation actions are not recorded. In this case, you may have to install the extension manually/separately.

The Firefox extension is located in "<installdir>\OpenScript\plugins\oracle.oats.scripting.modules.webdom.firefoxExtension_2.3.0.0400\xpi"

To install the FF extension by manually:

Go to the extension directory of the Firefox profile "default". (Usually C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Profiles\9iusc98z.default\extensions
Create a file named "webdom@openscript" in the extension directory.
Copy the path of the Firefox extension ("<installdir>\OpenScript\plugins\oracle.oats.scripting.modules.webdom.firefoxExtension_2.3.0.0400\xpi") as the content of file "webdom@openscript".