Start/Stop the runtime engine

This topic includes information on how start and stop the OpenText Functional Testing for Developers runtime engine, as well as retrieve information on the runtime engine status.

While the engine is running, it always consumes at least one license. When the engine is idle for the amount of time configured in the runtime engine settings, the OpenText Functional Testing for Developers license is released and the runtime engine closes.

Start the runtime engine

You can run the runtime engine to use as a stand-alone OpenText Functional Testing for Developers machine, or as part of an OpenText Functional Testing for Developers grid configuration.

For a grid configuration, run the runtime engine as a grid on the grid machine, and run it as a node on the node machines. For more details on the OpenText Functional Testing for Developers grid configuration, see Use a grid configuration.

Start the runtime engine in one of the following ways:

Where Run as Stand-alone Run as Grid or Node

In the IDE

From the UFT Developer menu, select Start Runtime Engine.

If you select Enable UFT Developer when <IDE> opens, the engine is automatically activated the next times you open your IDE.

NA
Start menu (Windows only)

Select UFT Developer Runtime.

Select one of the following:

  • UFT Developer Runtime (Grid)
  • UFT Developer Runtime (Grid Node)
Command line

Windows:

Run leanft start (located in <Installdir>\bin).

Linux: Run ./leanft start (located in <Installdir>/bin).

Mac: Run ./leanft start (located in the installation directory).

Note: You cannot run OpenText Functional Testing for Developers in parallel to OpenText Functional Testing or Sprinter.

Windows:

Run leanft.bat start --role=grid

or leanft.bat start --role=node

(located in <Installdir>\bin).

Linux:

Run ./leanft start --role=grid

or ./leanft start --role=node

(located in <Installdir>/bin).

Mac:

Run ./leanft start --role=grid

or ./leanft start --role=node

(located in the installation directory).

Caution: Do not run the OpenText Functional Testing for Developers runtime engine as a grid and a node on the same machine.

Note: OpenText Functional Testing for Developers nodes connect to the grid configured in their settings, regardless of whether nodes are started before or after the grid.

Therefore, when you restart an OpenText Functional Testing for Developers grid machine, you don't need to restart the nodes that were connected to it.

Back to top

Stop the runtime engine

Stop the runtime engine in one of the following ways:

From where Deactivate the runtime engine

In the IDE

 From the UFT Developer menu, select Stop Runtime Engine.
Task Bar / Start menu (Windows only) Right-click the icon in the task bar and select Exit.
Command line

Windows: Run leanft stop (located in <Installdir>\bin).

Linux: Run ./leanft stop (located in <Installdir>/bin).

Mac: Run ./leanft stop (located in the <Installdir>).

Note: To stop the grid or node runtime engine, add --role=grid or --role=node to the stop command.

Back to top

Retrieve runtime engine status

You can retrieve the status of the runtime engine on by running leanft info.

For engine status information on a grid or node machine, run leanft info --role=grid or leanft info --role=node

This information includes the OpenText Functional Testing for Developers build number, the port in use, whether the engine is running, and whether there is a valid license.

Example: (Windows)

C:\My Programs\UFT Developer\bin> leanft.bat info
UFT Developer local module is currently running
License: Demo DEMO, License expires in 30 days
Role: local
Port: 5095
UsingSecuredConnection: false
Build: <Build number>, (c) Copyright <year and company name>
Installation Folder: C:\My Programs\UFT Developer

Back to top