This shows you the differences between two versions of the page.
en:uft_integration [2019/05/03 11:47] tast [UFT Integration] |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== UFT Integration ====== | ||
- | |||
- | |||
- | TAST allows UFT tests execution in order to integrate both tools. | ||
- | |||
- | ===== Prerequisites ===== | ||
- | |||
- | * TAST must be installed and accessible. | ||
- | * UFT must be installed and accessible. | ||
- | * An ALM user with enough rights to run the script must be available. | ||
- | |||
- | ===== TAST ===== | ||
- | |||
- | The execution is made from a TAST diagram, the following elements are required: | ||
- | |||
- | * “User” object. | ||
- | * Message to execute the command. | ||
- | |||
- | The configuration of these objects are as follows: | ||
- | * User: | ||
- | * Mapping as “Adaptor user Object”. | ||
- | |||
- | * Message: | ||
- | * Properties: Predefined Function: //executeCommand//. | ||
- | * Mapping: String Value: //cscript.exe//. | ||
- | * // "C:\TAST\PayIntlSepa\Payments_RunUft.vbs"\\. | ||
- | * //The vbs file into quotes is the one containing the execution of the script, as explained later on. | ||
- | |||
- | {{:UFT_eng_1.png?nolink&350|}} | ||
- | |||
- | ===== UFT ===== | ||
- | |||
- | Steps to follow: | ||
- | |||
- | * Launch the UFT. | ||
- | * Register in ALM with a user with enough permissions to run the script. | ||
- | * Leave marked the tickbox for connecting to ALM with each new start. | ||
- | * Export the script to an available folder (several folders and files will be created inside this path). | ||
- | * The UFT can be closed or left open. | ||
- | |||
- | {{:UFT_eng_2.png?nolink&300|}} | ||
- | |||
- | ===== UFT Execution from TAST ===== | ||
- | |||
- | |||
- | |||
- | {{:UFT_eng_3.png?nolink&450|}} | ||
- | |||