UFT Runtime Engine
Relevant for: GUI tests and components, API testing, and business process tests and flows
UFT One Runtime Engine enables you to run UFT One tests (both GUI and API) and business process tests on your computer without installing the entire UFT One IDE. In addition, you can install the Runtime Engine without the Run Results Viewer, UFT One Add-in for ALM, sample applications, or Help documentation. This can potentially save you valuable disk space on your computer.
When you run the test with the Runtime Engine, you can access and run the test from a number of different places without the need to open the UFT One interface and configure UFT One options. When the test runs it runs in the background. At the end of the test run, you can view the test results.
Using the Runtime Engine requires very little experience in using UFT One. You do not need to edit tests, change settings, or understand how to make UFT One work with your application. You simply select the test, run the test, and view the run results.
Runtime Engine can be used in a number of different scenarios:
|Running tests and components from ALM||You can set up test runs from the Test Lab module in ALM, and run these on a computer using the Runtime Engine. This enables you to run the test, without the need to interact with the UFT One interface (such as loading UFT One add-ins in the Add-in Manager dialog box).|
|Running tests from automation||You can run tests using automation using the Runtime Engine. The Runtime Engine installation enables you to save disk space on the computer running these tests, freeing up system resources on that computer for other tasks.|
|Running tests using the Jenkins plug-in||
Runtime Engine can be installed on a build server or computer running builds of your applications. Using the Jenkins plug-in, you run a UFT One test as a post-build action of your application's build process.
Having Runtime Engine installed on this computer to run UFT One tests enables you to free up system resources for the important application build tasks.
|Running tests using external UFT One tools||
When you install the Runtime Engine, you have external tools which enable you to run UFT One tests locally, including the Test Batch Runner and the Silent Test Runner. These tools enable you to run a test locally against your application as it is developed, and view the results instantly after the test run.
As Runtime Engine does not enable you to edit a test, this version of the UFT One installation can be used by your application's developers and QA on an ongoing basis to provide regular testing of the application throughout the development process.
Runtime Engine Settings options
Runtime Engine also supports all the UFT One Add-ins as the full UFT One IDE, so you can run tests using any supported technology using the Runtime Engine. All objects and methods for all UFT One Add-ins are supported for use with the Runtime Engine.
As part of running a test, you can set specific run-time options. These options are set in the Runtime Engine Settings dialog box, available from the Windows Start menu:
|Add-ins||You can specify add-ins to be loaded.|
|Run result export options||You can specify how and what the Runtime Engine should export from the run results after a run session.|
|Autosave options||You can specify whether to automatically save the copies of open GUI tests every a few minutes and the auto-save interval.|
|Remote connection options||
Note: To modify these options, you must have a UFT One license installed.
You can specify how the Runtime Engine runs tests, including the format of the run results, whether the run results are opened automatically after a test run, and if the Runtime Engine takes screen captures or movies of the run session.
|Text Recognition options||
You can specify how the Runtime Engine works with text in your application when running a GUI test.
When setting the Text Recognition > ABBYY OCR Language option, you must use values from the following list:
Abkhaz, Adyghe, Afrikaans, Agul, Albanian, Altaic, ArmenianEastern, ArmenianGrabar, ArmenianWestern, Awar, Aymara, AzeriCyrillic, AzeriLatin, Bashkir, Basque, Belarusian, Bemba, Blackfoot, Breton, Bugotu, Bulgarian, Buryat, Catalan, Chamorro, Chechen, ChinesePRC (for ChineseSimplified), ChineseTaiwan (for ChineseTraditional), Chukcha, Chuvash, Corsican, CrimeanTatar, Croatian, Crow, Czech, Danish, Dargwa, Digits, Dungan, Dutch, DutchBelgian, English, EskimoCyrillic, EskimoLatin, Esperanto, Estonian, Even, Evenki, Faeroese, Fijian, Finnish, French, Frisian, Friulian, GaelicScottish, Gagauz, Galician, Ganda, German, GermanLuxembourg, GermanNewSpelling, Greek, Guarani, Hani, Hausa, Hawaiian, Hebrew, Hungarian, Icelandic, Ido, Indonesian, Ingush, Interlingua, Irish, Italian, Japanese, Kabardian, Kalmyk, KarachayBalkar, Karakalpak, Kasub, Kawa, Kazakh, Khakas, Khanty, Kikuyu, Kirgiz, Kongo, Korean, Koryak, Kpelle, Kumyk, Kurdish, Lak, Lappish, Latin, Latvian, Lezgin, Lithuanian, Luba, Macedonian, Malagasy, Malay, Malinke, Maltese, Mansi, Maori, Mari, Maya, Miao, Minankabaw, Mohawk, Mongol, Mordvin, Nahuatl, Nenets, Nivkh, Nogay, Norwegian, NorwegianBokmal, NorwegianNynorsk, Nyanja, Occidental, Ojibway, OldEnglish, OldFrench, OldGerman, OldItalian, OldSpanish, Ossetic, Papiamento, PidginEnglish, Polish, PortugueseBrazilian, PortugueseStandard, Provencal, Quechua, RhaetoRomanic, Romanian, RomanianMoldavia, Romany, Ruanda, Rundi, Russian, RussianOldSpelling, Samoan, Selkup, SerbianCyrillic, SerbianLatin, Shona, Sioux, Slovak, Slovenian, Somali, Sorbian, Sotho, Spanish, Sunda, Swahili, Swazi, Swedish, Tabassaran, Tagalog, Tahitian, Tajik, Tatar, Tinpo, Tongan, Tswana, Tun, Turkish, Turkmen, Tuvin, Udmurt, UighurCyrillic, UighurLatin, Ukrainian, UzbekCyrillic, UzbekLatin, Visayan, Welsh, Wolof, Xhosa, Yakut, Zapotec, Zulu
The ABBYY OCR Language option is available only if you include the ABBYY OCR Engine feature in the UFT One installation.
|Web and Windows Application options||You can specify how the Runtime Engine runs tests for specific scenarios against a Web application or Windows application.|
For details on using the Runtime Engine, see the Runtime Engine Guide.