Troubleshooting

This topic provides troubleshooting for known issues when working with LeanFT.

Java applications do not run when I launch LeanFT

Problem: After I launch the LeanFT runtime engine, Java applications that usually run on my computer without any problem do not run.

Solution: Manually make the following change in the c:\Windows\mercury.ini file:

  1. Add the process name of your Java application to the end of the file using the following format: <processName>.exe=0
  2. Restart the LeanFT runtime engine.

Back to top

Runtime: Test gets stuck after browser opens

Problem: When running a test, the test gets stuck after the browser opens, before navigation.

Solution: If you have a proxy set up, make sure it is not localhost or 127.0.0.1.

Back to top

Eclipse: LeanFT plugin not working in Eclipse

Back to top

Eclipse: "View Last Run Results" is disabled in the LeanFT menu after running a test

Problem: I get the following error in my Eclipse console output:

java.io.IOException: Cannot run program "wmic": CreateProcess error=2, The system cannot find the file specified

Solution: Make sure that you have the Java JRE/JDK path configured in your PATH environment variable. The path should point to the location of java.exe.

Example: C:\Program Files (x86)\Java\jre1.8.0_91\bin

Back to top

Web is not recognized on Google Chrome

Possible cause: For LeanFT to work in Google Chrome, the Google Chrome extension needs to be installed. If LeanFT was installed before Google Chrome was installed, then the Google Chrome extension is missing in the LeanFT resources.

Solution:

  1. Open Google Chrome Extensions (chrome://extensions)

  2. Drag and drop the following file onto the Extensions page:

    • Chrome v. 30 and earlier: <LeanFT installation folder>\Installations\Chrome\AgentLegacy.crx
    • Chrome v. 31 and later: <LeanFT installation folder>\Installations\Chrome\Agent.crx

    After the Functional Testing Agent extension is installed, it is displayed in the Chrome Extensions list.

  3. Restart the computer.

  4. Restart the LeanFT runtime engine.

Back to top

LeanFT is not recognizing the objects in my application

Problem: LeanFT is not recognizing the objects in my application. What should I do?

Solutions:

  • If you are testing Web objects, make sure you have followed the instructions for setting up your Web browsers to work with LeanFT and that you open the Web browser after the LeanFT runtime engine is active. For details, see Set up web browsers and controls.
  • Make sure your application was developed with a supported technology and version. For details, view the LeanFT Product Availability Matrix from the HP Software Support site. (Requires an HP Passport and a support contract.)
  • If you need to test specific objects that are not supported out of the box, create Insight test objects to enable LeanFT to access your objects via image-based recognition. For details, see Insight image-based identification (Windows only).

Back to top

Object Identification Center (OIC) not identifying browser (design)

Problem: During design time, the OIC is not able to identify my browser.

Solution: If you have a proxy set up, make sure it is not localhost or 127.0.0.1.

Back to top

Object Identification Center (OIC) not recognizing objects

Back to top

Object Identification Center (OIC) in Eclipse not working after LeanFT upgrade

Problem: I just upgraded LeanFT. Now when I open the OIC in Eclipse, it flashes open but then disappears. I tried to invoke the OIC from command line, but the same thing happens. The log tells me that "C:\Program" failed to run.

Back to top

Cannot open the Object Identification Center (OIC) on Linux

Problem: The OIC is not opening (on Linux).

Possible cause: To work with the OIC on Linux, the libXss library must be installed on your machine.

Solution: Install the libXss library by running the following command: # yum install libXScrnSaver

Back to top

Application model in Visual Studio is showing a blank screen

In Visual Studio, the Application model window suddenly goes blank.

Solution:

  1. Open PackagePreferences.json, located in %appdata%\Hewlett-Packard\LeanFT\Preferences.
  2. Locate the EnableAppModelLargeAddressSpace parameter, and change the value from false to true.

    It should look as follows:

    "EnableAppModelLargeAddressSpace": true

Back to top

Report not building after running test

Problem: The report is not being generated after the test runs

Solution: Make sure you have write permissions to the report output folder. The location may be specified in a LEANFT_REPORTS_TARGETDIR environment variable, in the test's App.config or leanft.project file, or inside your test using the ReportConfiguration methods.

Back to top

Mobile: Device logs not showing up in run results report

Problem: I ran a test on a mobile device, but I don't see the device log in the HTML report.

Solution: To see device logs in the HTML report, you must include a Launch or Restart method to ensure that app opens on the device. For more information, see Create mobile steps in your test in the Mobile Center Help.

Back to top

ALM: "LEANFT-TEST" missing in test types

Problem: When I create a new test in my ALM test plan, I don't see LEANFT-TEST in the Type list.

Possible causes:

  • The ALM patch (12.53) that supports the LeanFT test type must be installed and configured.

  • After installing the 12.53, the test types may not have been manually updated. This is necessary for the new test types to appear in the Type list of existing projects.

Solution: 

  1. Close ALM.

  2. Install and configure the ALM 12.53 patch.

  3. Log into ALM >  Site Administration and update the test types (Tools> Update Test Types). All existing active ALM projects will be updated with the test type definition files that were added in the new ALM version, which include the LeanFT test type.

    For more details, see the ALM Help Center.

Back to top

ALM: Cannot run test. I get a message about Remote Agent configuration

Back to top

ALM: Cannot run a NUnit 3 test with parameters from ALM

Possible cause: You may be using the ALM data source that is meant for NUnit 2.6 tests. Instead, for NUnit 3 tests, you should be using the ALMStatic data source.

Solution: For NUnit 3 tests, use the ALMStatic data source.

For example:

[TestCaseSource("ALMStatic")]

public void Test(string param)

{

...

}

Back to top

LeanFT-BPT entities are corrupted after upgrade

Possible cause: LeanFT-BPT entities created in a previous version of ALM can become corrupted after upgrading to a version of ALM that does not support LeanFT, and then upgrading again to another version of ALM that does support LeanFT.

For example, if your upgrade path was: ALM 12.01 Patch 3 > ALM 12.50 > ALM 12.53, then your entities may become corrupted.

LeanFT-BPT entities include LeanFT components and BPT flows or tests with LeanFT components.

Solution: Perform a repair of the ALM project with corrupted entities, as described in the ALM Administrator Help.

Back to top

See also: