- 1 Known Problems, Limitations and Workarounds
- 1.1 Oracle Open Script Load Testing
- 126.96.36.199.1 When using the SNMP data source, new SNMP MIBs that users specify are uploaded to the Oracle Load Testing Server by default and can be accessed only through the Local Oracle Load Testing Data Collector running on that Server. Remote Oracle Load Testing Data Collectors cannot access these MIBs and users need to copy those over manually.
- 188.8.131.52.2 The ServerStats JMX discovery caches counter information. The side effect is that it also caches error messages. For example, failure to copy the correct jar files to data collector’s classes directory prior to attempting the discovery would result in an error. When the discovery is attempted after copying the jar files, the discovery still may not work because of the cache. The recommended workaround is to re-start the Oracle Load Testing Server and retry the discovery.
- 1.2 Oracle Open Script Test Manager
- 1.3 Oracle Open Script Database 10g Express Edition
- 1.4 Oracle Open Script Functional Testing – OpenScript
- 1.5 Oracle Open Script Functional Testing
- 1.6 Share and Enjoy !
- 1.1 Oracle Open Script Load Testing
Known Problems, Limitations and Workarounds
This (Oracle Open Script) section lists known issues and workaround solutions for the components in the Oracle Application Testing Suite.
Oracle Open Script Load Testing
The following are know issues and workaround solutions for Oracle Load Testing.
- If your script fails to playback successfully in Oracle Load Testing due to Windows authentication or other user permissions related issues with your application, this may be due to the login authentication of the Oracle Load Testing Agent Service. The Oracle Load Testing Agent Service which runs all the Virtual Users on a given Agent system will by default be installed to run under the Local System account. This may cause issues for certain applications if they block access to this account. To address this, open the Oracle Load Testing Agent Service in the Services panel and change the login to run under a specific user with appropriate application permissions.
- In order to use the Oracle Load Testing Java Client “User Mode” option, users must first save a Java version of their test script saved in Oracle Functional Testing. There is an option available in Oracle Functional Testing that enables it to compile and save the test script in Java for use by the Java Agent. In the Oracle Functional Testing Advanced Options dialog under JavaAgent, check Create a Java Agent script after saving a script. The next time you save your script, Oracle Functional Testing will save the standard script files plus the Java Agent files. This script can then be run in Oracle Load Testing using the Java Client option.
When using the SNMP data source, new SNMP MIBs that users specify are uploaded to the Oracle Load Testing Server by default and can be accessed only through the Local Oracle Load Testing Data Collector running on that Server. Remote Oracle Load Testing Data Collectors cannot access these MIBs and users need to copy those over manually.
- To use the JMX Data Source, you may need to manually copy the server-specific class files to the <installdir>DataCollectorclasses directory on the Data Collector machine. These class files are required for each J2EE Application supported server. The jar files should be same version as the J2EE Application Server. You should get the class files from your Application Server installation. The list of required jar files is contained in the Oracle Load Testing “agents.properties” file located in <installdir>DataCollectorproperties.
To do JMX Discovery on WebLogic 10.3.1, doing the following:
- Copy <installdir>libwlfullclient.jar to <installdir>DataCollectorclassesweblogic9.1
- Open <installdir>DataCollectorpropertiesagents.properties and modify it so Agents.JMX.Server.weblogic91.ClassPath = classes/weblogic9.1/wlfullclient.jar and save the file.
- Log in to Oracle Load Testing.
- Select Metrics from the ServerStats menu then select New.
- Also select the JMX Data Source then click Discover Counters.
- Select the local system and click Edit.
- Select Oracle WebLogic 9.1 as the server (port 8088), username
oatsand the password (the password specified when installing the Oracle Application Testing Suite product).
- Click OK.
- Click OK and the discovery process begins. After a few moments, you will see a full list of the MBeans on the server.
The ServerStats JMX discovery caches counter information. The side effect is that it also caches error messages. For example, failure to copy the correct jar files to data collector’s classes directory prior to attempting the discovery would result in an error. When the discovery is attempted after copying the jar files, the discovery still may not work because of the cache. The recommended workaround is to re-start the Oracle Load Testing Server and retry the discovery.
Oracle Open Script Test Manager
The following are known issues and workaround solutions for Oracle Test Manager.
- When creating an Oracle Functional Testing type Test Case, the script file must be saved as a package file (.otmpkg) in Oracle Functional Testing in order to attach it to the Oracle Functional Testing Test Case in Oracle Test Manager.
- The icons in the Tree View for Requirements, Tests and Issues are automatically assigned and cannot currently be configured by the Administrator.
- After configuring a new database in the Oracle Test Manager Database Configuration dialog, users must restart the Oracle Application Testing Suite Application Service in order for that database to appear in the Database dropdown list on the Oracle Test Manager login page.
- Troubleshooting 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 Application Testing Suite Agent 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 the following all as one command. The .conf file is an argument for the .exe.
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.
Oracle Open Script Database 10g Express Edition
The following are known issues and workaround solutions for Oracle Database 10g Express Edition.
- In some cases, the Oracle Database 10g Express Edition service does not start completely. If you receive a 404 Not Found error when starting Oracle Load Testing or Oracle Test Manager, restart the Oracle database service and the Oracle Application testing service, as follows:
- Open the Control panel and the Administrative Tools.
- Open Services.
- Select the Oracle Application Testing Suite Application Service and click Stop the service.
- Select the OracleServiceXE service and click Restart the service.
- Wait for the OracleServiceXE service Status to indicate “Started”.
- Select the Oracle Application Testing Suite Application Service and click Start the service.
- Wait for the Oracle Application Testing Suite Application Service Status to indicate “Started”.
- Restart Oracle Load Testing or Oracle Test Manager.
Oracle Open Script Functional Testing – OpenScript
The following are known issues and workaround solutions for Oracle OpenScript.
- The Java editor does not pause at breakpoints outside of the current script. Playback will only pause at any breakpoints added to the current script. To pause at a breakpoint in a child script, it is necessary to add a breakpoint before the child script function. Then, use the “Step Into” feature to step into the child script function. Only after stepping into the child script, playback will pause at the child script’s breakpoint.
- Automatic proxy configuration (Preferences – OpenScript – Record – HTTP Module) for Firefox may not correctly configure the browser proxy. To record through Firefox, you should configure the browser proxy settings manually (Default: host=localhost, port=7777)
- Certain systems may have trouble launching the OpenScript Help (Help – Help Contents). This can be resolved by configuring the help to open in an external browser window:
- From the Tester Perspective, select View – OpenScript Preferences.
- Click the “Clear” icon next to the filter text field in the upper left. And click the Help tree node and check the “Use external browser” box in the Help preferences.
- Click OK and relaunch OpenScript Help.
Scripts created in OpenScript will not work in user defined profiles in Oracle Load Testing. Instead, users can build jobs using the Initialize, Run, and Finish sections of a script created in OpenScript.
Web Functional Test Recording with Firefox Troubleshooting
The following section describes Web Functional Test Recording with Firefox Troubleshooting techniques.
- When using the Firefox browser, you should disable or not install any add-ons into the OpenScript-created Firefox profiles.
- The first time recording it is possible that Firefox has not completely initialized the OpenScript plug-ins. Try stopping recording and trying again. If Firefox still fails to record:
- Run <install dir>/OpenScript/UninstallBrowserHelpers.bat
- Run <install dir>/OpenScript/InstallBrowserHelpers.bat
Oracle Open Script Functional Testing
The following are known issues and workaround solutions for Oracle Functional Testing.
- Scripts that playback successfully in Oracle Functional Testing may still fail when run in Oracle Load Testing Thin Client or Java Client modes. This is because Oracle Functional Testing is playing back scripts at the GUI level by automating browser DOM events and Thin/Java Client are playing back at the HTTP protocol level which may have different playback issues. Use the Oracle Functional Testing Navigation Editor to verify and troubleshoot script playback in Oracle Load Testing Thin and Java Agents.
- When adding a Text Matching Test to your script it is possible that it may be added to the wrong page or frame depending on what you have selected in your tree, resulting in a failure. Be sure to verify that your Text Matching Test was added to the correct page and frame if you are seeing unexpected failures.
- Double clicking on the HTML node of a frame with sub-frames will not display the HTML of the recorded page. Only pages with no sub-frames can be displayed in this manner.
- The Navigation Editor does not allow you to iterate over multiple records using databanks when playing back a script. Select the “Playback with Databank” option and specify which record to use to playback with that record.
Some proxy servers will always return a HTTP return code 200 (‘OK’) whether or not the requested item is available. In these cases Resource Validation will incorrectly report that a missing resource is available.
- In Options (Current Script or New Script) – Advanced – Siebel Support: The Reset Siebel State button is used in conjunction with the Regenerate Thin Client Script button. The Reset Siebel State button removes all of the previously found sources in the Thin Client script so that the Regenerate will operate on a script free of the previously found sources. The only effect of the Reset Siebel State button is to change the Thin Client script generated by the Regenerate Thin Client Script button.
- On systems without Microsoft Office installed, the Navigation Editor in Oracle Functional Testing may not function correctly. To remedy, install the Microsoft ActiveX Control Pad from
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaxctrl/html/cpad.aspwhich will install a needed .dll file.
For Windows Vista systems, complete these steps before running the ActiveX Control Pad setup procedure:
- Right click on setuppad.exe and select Properties.
- Click the Compatibility tab.
- Select Run this program in compatibility mode for: option and then select Windows XP (Service Pack 2).
- Click Apply and then OK.
- Run the setuppad.exe program to install the ActiveX Control Pad.