Troubleshooting Functional tests

On Linux, when you either run the recorded scripts or insert objects to the scripts for the Eclipse application in Rational® Functional Tester, the scripts fail and display the ObjectNotFound Exception error.

There is a mismatch in the GTK version between Rational® Functional Tester and the Eclipse application that is under test.

After you record Functional tests on a web application by using the Chrome browser, when you highlight the test objects, the objects are not highlighted in the application under test.

When you select any object from the Test Object Map window, the test object is not highlighted in the application under test. The following error message is displayed:

The <Object name> could not be highlighted.

You must place the Test Object Map window in front of the Chrome browser window. Because the application under test is in focus, the objects are highlighted correctly.

On Linux, when you play back the Compound test that contains Functional tests, the playback does not start.

Soon after you install Rational® Functional Tester on your computer, if you playback the Compound test that contains Functional tests, the playback does not start. The error log displays the code generation error because of the null pointer exception. This is because the environment variable did not take effect after the installation of Rational® Functional Tester.

When you play back Functional tests by using the Chrome or Edge browsers, the playback fails.

The Web UI method of playback requires the latest drivers for the Chrome or Edge browsers. If the latest drivers are not found, then the playback fails.

ObjectNotFoundException exceptions occur while inserting a verification point on ErrorProvider, HelpProvider and ToolTipText controls in .Net.

This occurs if you create a data verification point on ErrorProvider, HelpProvider and ToolTipText controls while recording in .Net.

In .NET, create properties verification points on these controls.

System.NullReferenceException occurs while playing back a data-driven script that contains calendar controls in SAP applications.

You might have closed the calendar control after recording a data-driven script, in which case a close() event is generated in the script. The script will look similar to the following example:

Because the setDate() method sets the focused date and also closes the calendar control, the script will fail during playback while trying to close the calendar control.

Playback fails while performing data verification on controls like text, ComboBox, or Tree in SAP applications.

This occurs if the verification point method is recorded before the methods like set for text/combo box or ExpandNode/doubleClickNode for a tree control.

The following error message is displayed while creating a functional test project in .Net:

"Failed to enable ClearCase® integration. Registry entries for installed source code control provider are missing. Please configure source control provider appropriately."

This message is displayed if the registry settings for ClearCase are corrupted.

You must fix the registry settings manually. For more information about changing the source control provider or editing the registry settings, refer to the MSDN Help.

Rational® Functional Tester does not recognize Siebel 7.7 controls after moving back to Siebel 7.7 from Siebel 7.8.

When you start Siebel 7.8, Internet Explorer installs the latest Siebel ActiveX objects. So, if you try to record using Rational® Functional Tester on Siebel 7.7 after this, Rational® Functional Tester is not able to recognize Siebel 7.7 controls.

Remove the Siebel ActiveX objects from the folder C:\WINDOWS\Downloaded Program Files and then try to work with the Siebel 7.7 application again.

A Java™ application-under-test (AUT) does not open while configuring the application for testing in Rational® Functional Tester.

The AUT does not open while configuring the application for testing if you specify a lower version of JRE than the JRE version that was used to compile the test application.

Playback fails while testing SAP applications that contains password fields.

Rational® Functional Tester records the entered password as it appears in the password field and is not able to read the encrypted value.

Before playing back the script, replace the recorded password with the actual password in the script.

Rational® Functional Tester context sensitive help does not work on VS .Net IDE.

Install the MSDN library. During installation, select options to integrate the MSDN library with the VS .Net IDE for the Rational® Functional Tester context sensitive help to work.

When you try to open a PDF file from the Tutorial Gallery, the computer hangs.

If you are using Adobe® Reader 6.0.0, opening a PDF file from the Tutorial Gallery might cause your computer to hang.

Other versions of Adobe Reader do not cause this problem. Free upgrades to the latest level of Adobe Reader are available from the Adobe web site.

Multimedia user assistance does not appear.

Multimedia user assistance, such as Tours, Tutorials, and Show me viewlets require the Flash player to be installed on your computer.

Install Flash Player version 6.0 or newer from the Adobe web site.

Disabling the support for playback on Eclipse when views and editors are dragged or undocked after recording.

Add the statementrational.test.ft.enable_eclipse_support=false in ivory.properties file.

Script that are recorded in one browser fail to play back in another browser.

A script recorded in Internet Explorer, for example sometimes fails to playback in Mozilla Firefox

Inspect the DOM structure of the objects in the browsers. For example, you can use the DomInspector for Mozilla Firefox. Similarly, DOM Structure can be interpreted for other Browsers as well. Then you can compare and check whether the object hierarchy is same.

• If the DOM hierarchy of the browsers is not same then the failure is not happening because of a Rational® Functional Tester problem. The browsers are creating different DOM hierarchy because of which the playback fails.

  Workaround: This can be fixed by introducing the missing hierarchy Rational® Functional Tester looks for while playing back the script

• If DOM hierarchy of browsers is same then there might be a problem with Rational® Functional Tester.

Record and playback does not work on browser menu options

Rational® Functional Tester supports testing the browser content but not interactions with the browser menu options or the browser itself. This is done mainly to provide cross-browser record and playback facility for testing HTML applications.

Capture the browser object and use the inputKeys method to interact with the menu options using the keyboard shortcuts for the specific menu options.

For example, the Close option in the File menu can be accessed using the shortcut key Alt+F+C. If you need to access this option, then you can use the inputKeys method on the browser object, providing the shortcut key ("%fc") as an input parameter as shown below:

Browser_HtmlBrowser(Document_HtmlDocument(),DEFAULT_FLAGS).InputKeys("%fc")

Internal SAP error (ABAP) during recording

While recording against SAP applications, sometimes SAP scripting framework internally throws some ABAP errors and recording stops. The problem will not get fixed unless SAP fixes it in their scripting framework.

Disable modal search help on the system for the user that runs the script. You can do this in the Preferences dialog in the SAP GUI, from the help menu. If this solution does not work, you may have to restart your SAP application

System.NullReferenceException occurs while playing back a data-driven script, which contains calendar controls in SAP applications.

You may have closed the calendar control after recording a data-driven script and hence a close() event is generated in the script.

The script will look like: dialog_calendar().close();

Since the setDate() method sets the focused date and also closes the calendar control the script will fail during playback while trying to close the calendar control.

Delete the calendar close method that was generated in the script.

In Linux®, calling the RationalTestScript API commands from multiple threads causes asynchronous errors.

When two threads in a process submit X requests simultaneously, the X libraries cannot handle the requests because they are not thread-safe. This causes asynchronous errors with messages like Unexpected asynchronous reply or Event lost to occur. This may also occur when multiple threads are used in functional test scripts.

In the ivory.properties file, set the option rational.test.ft.script.playback.mouse.allow_multiple_threads to "true."

Encoding problems while importing files on Linux.

On Linux, due to incompatible encoding formats, Rational® Functional Tester may not recognise or read the files that are being imported. In Rational® Functional Tester the default encoding format is set to UTF-8. But UTF-8 cannot handle a few encoding formats like Cp1252.

Unable to play back .Net scripts stored in the network.

The project in the network may not have Full Trust permission in the local computer due to its security policy. A RuntimeSecurityPolicyException message is displayed in the playback log or in the debug log.

Compilation error occurs while sharing a functional test project using ClearCase.

By default, ClearCase is configured to be case insensitive. If a file name contains upper case letters, ClearCase converts it into lower case. Similar problem occurs when you record a new script inside an existing project located in ClearCase.

ClearCase integration on Linux does not work if it is not installed in the /opt/rational directory.

To use ClearCase with Linux, you must install ClearCase in the /opt/rational or the /usr/atria directory, or set CLEARCASEHOME or ATRIAHOME to the ClearCase installation directory.

Unable to resolve resource bundle

If Flex Builder 2 is used to build a Flex application with the Rational® Functional Tester adapter, you might get an error on resource bundling.

Do not modify the functional test project assets hierarchy.

1. Click Configure > Enable Environments for Testing > Java environments tab.
2. Type -Dawt.toolkit=sun.awt.motif.MToolkit in the Run Options field and click Finish.

• The Internet Explorer setting Initialize and script ActiveX controls not marked as safe is enabled.
• The application is loaded through a HTML page, with an <object> tag that has an id attribute set, and the id attribute contains no periods or hyphens.
• The application is loaded either from a web server or locally from a trusted SWF file.

For example: Looking for [button] with state [ENABLED|VISIBLE|READY], possible failing candidate[{.mappableClassIndex=0, text=*!ENT!*, .classIndex=0}] with incorrect state [DISABLED]

• ENABLED
• VISIBLE
• READY (for browser)

For example: Replace button().click(); with button(null, DISABLED).click();

• Ensure that the GEF enabler plug-in com.rational.test.ft.gef_xx.jar exists in the plug-in directory of the AUT.
• If the GEF objects are not identified even after enabling, start the AUT with -clean option.
• For non-standard editors, add the method getAdapter in the non-standard GEF editor (AUT). This method is used by Rational® Functional Tester to get an instance of GraphicalViewer to recognize GEF objects in the editor.

  public Object getAdapter(Class type)
  {
  if (type = org.eclipse.gef.GraphicalViewer.class)
   {
  <<return the current instance of org.eclipse.gef.GraphicalViewer>>
   }
  }
  

1. Go to Tools > Internet Options > Security Wizard.
2. Clear the Protected mode check box.
3. Restart the browser.

1. Type about:config as the URL in the Firefox 3.0 browser.
2. Set the following security flags:
   • key: security.fileuri.origin_policy and value: 3
   • key: security.fileuri.strict_origin_policy and value: false

• Change <param name="movie" value="C:\FlexSample\Smoke.swf"> to <param name="movie" value="Smoke.swf"/>.
• Change <embed src="C:\FlexSample\Smoke.swf"> to <embed src="Smoke.swf">.

1. Open the terminal with root credentials
2. Browse to /usr/sbin and run the command run the command setenforce 0.

Add the statement rational.test.ft.enable_eclipse_support=false in ivory.properties file.

• Ensure that the version of the xulrunner is -1.9.2.
• Before launching Rational® Functional Tester, add the line: -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner to the eclipse.ini file available in the Rational® Functional Tester installation directory. For example: /opt/IBM/SDP/eclipse.ini

1. Verify that Rational® Functional Tester supports the SAP GUI version for testing.
2. Enable the SAP GUI client for testing.
3. Enable the SAP server for testing

1. Back up the registry by exporting the key     HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider.
2. Change the Windows Registry entry     HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider to     [HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider]     "ProviderRegKey"="Software\\Microsoft\\SourceSafe"     "PreviousProviderRegKey"="Software\\Atria\\ClearCase"     [HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders]     "Microsoft Visual SourceSafe"="Software\\Microsoft\\SourceSafe"
   Note: The double backslashes are present if you export the registry keys. You can use the export to import though a .reg file. To set the entries manually, use single backslashes. For example: Software\Microsoft\SourceSafe

1. Download and install the vcredist_x86.EXE file from the location http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26347. Complete the installation instructions mentioned in the page. You might be prompted to restart your computer.
2. Open the command prompt and navigate to C:\Program Files\IBM\FunctionalTester\vsnet\bin (on 64-bit computers, C:\Program Files (x86)\IBM\FunctionalTester\vsnet\bin)
3. Run the following command: regsvr32 RftVs10.dll. A dialog box is displayed, with a message indicating that the Rftvs10.dll file was successfully registered: DllRegisterServer in RftVs10.dll succeeded.

• For Internet Explorer browsers, update the policy file with the permissions in the security folder of the JRE that is associated with the browser.
• For Mozilla Firefox browsers, manually enable the browsers, and ensure that the Next-Gen plug-in is disabled.
• Use the Scripting option to access elements relative to the enabled domain toplevelwindow (either HTMLTopLevelWindow or JavaTopLevelWindow)