Monday, January 27, 2014

UFT/QTP - Patches and toolkit

UFT/QTP - Patches
1. Patches For Fire-fox Support with QTP-11
- QTPWEB_00090
- QTPWEB_00092
- QTPWEB_00100
- QTPWEB_00105

2. Patche(s) For Chrome Support with QTP-11
- QTPWEB_00088

3. I.E 9 Support
- QTPWEB_00078

4. UFT Service Pack 11.53
- UFT_00044

5. Install Web 2.0 Toolkit
- Run setup.exe, and click the “Add-in Extensibility and Web 2.0 Toolkits.  This will open a page in IE.
- Click the Web 2.0 Toolkit Support Link --> Download and unzip the Web2AddinSetip.zip file
- Run WebToolkitsInstaller.exe.
- Install any or all add-ins (ASP Ajax, Dojo, GWT, JQueryUI, YahooUI)

Thursday, January 23, 2014

Installation required to integrate UFT with QC

Installation required to integrate UFT with QC.

Download below mentioned files from HP site:
- HP_Unified_Functional_Add-in_for_ALM
- TDConnect
- SysAgent
- UFTALM_00038

http://<QCServer>/qcbin



Reference:
http://update.external.hp.com/qualitycenter/qc90/mictools/qtp/index.html


Friday, January 17, 2014

UFT/QTP - Test Batch Runner Tool

How to Create and Run a Test Batch


Relevant for: GUI tests and components and API testing
- "Open Test Batch Runner" below
- "Access the test batch file" on next page
- "Add batches or tests" on next page
- "Select the tests to be part of the test batch run" on next page
- "Run the test batch"
- "View the test batch run results"

1. Open Test Batch Runner
Select Start > All Programs > HP Software > HP Unified Functional Testing > Tools > Test Batch Runner. This opens a separate window for the Test Batch Runner program. You do not need to have UFT open to use Test Batch Runner.

2. Access the test batch file
To create a new test batch file, select File > New or click the New batch file button .
Give your batch file a meaningful name and assign it to a place in your directory.
To open an existing batch file, select File > Open or click the Open batch file button .
In the Open dialog box, navigate to the folder in which the batch file is found and click Open.
The tests from the opened batch file are added to the Test Batch Runner main window.

3. Add batches or tests
To add a test batch file (.mtb), select File > Add or click the Add button . Navigate to the folder in which the batch file is saved.
To add individual tests, select Tests > Add or click the Add button . In the Browse For Folder dialog box, select the folder in which your tests are located. All the tests from the selected folder are added to the Tests pane in the main Test Batch Runner window.
Note: When adding tests through the Tests > Add menu command, you must select
all the tests from the target folder. If you do not want to run all the tests in the target
folder, select the check boxes next to the tests you want to run before you run the test
batch.

4. Select the tests to be part of the test batch run
Select the checkboxes for the tests that you want to include in the test batch run.

5. Run the test batch
Click the Run button to run the test batch. The Output pane provides run log details of the
batch run while the batch is running.

6. View the test batch run results
In the Tests pane, click the results link for a specific test in the Run Results column. This
opens the results for that test in the Run Results Viewer. For details on the Run Results
Viewer, click F1 within the viewer window.


How to Run a Test Batch Using the Windows Command Line
Relevant for: GUI tests and components and API testing
- "Open the Windows Command Line window" below
- "Provide the source folder for the batch file or tests" below
- "Run the test batch" below
- "View the test batch run results (API testing only)" below

1. Open the Windows Command Line window
Run cmd.exe to open the Command Line window. (For example, from the Windows Run
dialog box.)

2. Provide the source folder for the batch file or tests
In the Command Line window, enter UFTBatchRunnerCMD.exe and the source switch
followed by the test batch file (.mtb) or folder containing the test.
For example, your command line might contain text like this:
UFTBatchRunnerCMD.exe -source "C:\users\MySample.mtb"
UFTBatchRunnerCMD.exe -source "C:\users\APITest1"

3. Run the test batch
After entering the Test Batch Runner command and the location of the folder containing your
tests, press ENTER. Test Batch Runner runs the test batch. For API tests, the test log is
displayed in the command window.

4. View the test batch run results (API testing only)
When the test batch run is complete:
a. Open the Run Results Viewer from the Start menu. The Open Run Results dialog box 
b. In the Open Run Results dialog box, select the Results XML file option.
c. Navigate to the Results.xml file under the test's Report folder and click Open. 
Each test has its own results. 

Friday, December 27, 2013

Configure Terminal Emulator in UFT / QTP [with(out) HLLAPI]

Configure Terminal Emulator in UFT / QTP

Configure the Terminal Emulator add-in for the correct emulator application being used, To configure the Terminal Emulator add-in:
1. Go to Tools -> Options -> Terminal Emulator tab.
2. Select the correct emulator application that you are using. If your emulator is not listed, select the New/Modify button and follow the steps in the Terminal Emulator Configuration Wizard.

Emulator NOT supports HLLAPI
From QTP's Options, create a new setting for the terminal emulator being used, Follow the instructions below if your terminal emulator NOT uses HLLAPI.
1. Start the emulator and connect to the server.
2. Go to Tools -> Options.
3. Select the Terminal Emulator tab.
4. Click <New/Modify> (<Open Wizard> for QTP 9.5 / UFT). The Terminal Emulator Configuration Wizard will appear.
5. Click <Next>.
6. Select the "Configure a new user-defined setting" radio button.
7. Enter in the name of your emulator.
8. Click <Next>.
9. Click <Next>.
10. Select the "Emulator does not support HLLAPI" radio button.
11. Click <Next>.
12. Now we need to point out the different screen components of the emulator window to QTP. Click the “hand” button for each one and then click the area of the window that you want to register. You should enabled the checkbox configure the emulator screen Click Next.
13. Mark Text Area – Terminal Emulator
14. Save the terminal emulator settings into file for use by other computers.
15. Finish button


Emulator supports HLLAPI

From QTP's Options, create a new setting for the terminal emulator being used, Follow the instructions below if your terminal emulator uses HLLAPI.
1. Start the emulator and connect to the server. Verify that you have set a short name for the emulator session that you have open. Please refer to your terminal emulator's documentation for instructions on how to do this.
2. Go to Tools -> Options.
3. Select the Terminal Emulator tab.
4. Click <New/Modify> (<Open Wizard> for QTP 9.5 and later). The Terminal Emulator Configuration Wizard will appear.
5. Click <Next>.
6. Select the "Configure a new user-defined setting" radio button.
7. Enter in the name of your emulator.
8. Click <Next>.
9. Click <Next>.
10. Select the "Emulator supports HLLAPI" radio button.
a. Either enter in the path or browse to the HLLAPI DLL. The DLL normally resides in the terminal emulator installation folder and is generally named ehllapi32.dll, whllapi32.dll, or ehllapi.dll.
b. Enter the HLLAPI procedure name.
c. Select the HLLAPI format. It is recommended you select "Auto-detect." If, in the next screen, QuickTest Professional is unable to capture the text in your emulator, click <Back> and change your selection to either "Classic" or "Extended.
Note:
Use "Text-only" if QuickTest Professional encounters recording and replay problems.
11. Click <Next>.
12. If QuickTest Professional is able to successfully identify the terminal emulator screen, you will see a screen capture in the HLLAPI Configuration Test Screen.
If you do not, try these trouble-shooting steps:
a. Verify your emulator is connected to the host and the short name is set.
b. Check that your HLLAPI property settings are correct (dll path, procedure, format).
c. Change the HLLAPI format to "Text-only".
d. Select "Emulator does not support HLLAPI" if all the above tips have failed.
13. Click <Next>.
14. You can save the settings that you have configured to a separate file so that other users can copy the terminal emulator configuration settings.
15. Click <Finish>.




Thursday, December 26, 2013

UFT/QTP - Terminal Emulator Add-in

UFT/QTP - Terminal Emulator Add-in

Use UFT with the Terminal Emulator Add-in to test terminal emulator applications that support HLL API (High Level Language Application Programming Interface) and those that do not, for example, emulator sessions configured to work with the VT100 protocol (using the Text-only option). HLLAPI allows an application to communicate with a mainframe application with extended capabilities.

The terminal emulator window consists of the frame, menus, toolbar, and status bar of the terminal emulator itself. This window remains constant throughout each terminal emulator session.


If your emulator supports HLLAPI, UFT recognizes the screen and field objects in your emulator screen. If 
your emulator does not support HLLAPI, or you have configured UFT in Text-only mode, UFT records operations in terms of the text as it appears in the rows and columns of your emulator screen.

Emulator -> IBM Personal Communications (PCOM)
The preconfigured settings enable UFT to work with IBM PCOM terminal emulators

Wednesday, December 18, 2013

What is Dojo Add-in UFT/QTP

Dojo Toolkit Environment

ProjectName: DojoToolkitLib
ProjectTitle: Dojo Toolkit Environment

Dojo objects.
Test Object Description
DojoAccordion A Dojo control that contains expandable panels, of which only one panel can be expanded at a time.
DojoCalendar A Dojo calendar control.
DojoCollapsiblePanel A Dojo panel that can be expanded or collapsed to show or hide its content by clicking its title.
DojoComboButton A Dojo control that has a regular button on the left, and on the right has a down arrow that opens a drop-down control (often a menu).
DojoDropDownButton A Dojo button that opens a drop-down control (often a menu).
DojoDropDownMenu A Dojo menu control that opens when you click another control.
DojoFilterComboBox A Dojo combo box that filters the values in its drop down list according to the text entered in its edit box.
DojoProgressBar A Dojo progress bar control.
DojoRichTextArea A Dojo text area that allows complex editing, styling, and formatting.
DojoSlider A Dojo slider control.
DojoTabStrip A Dojo tabstrip control.
DojoToggleButton A Dojo toggle button control, which can be pressed to toggle between On (pressed) and Off (released) states.
DojoToolbar A Dojo toolbar control.
DojoTree A Dojo tree control.

Notes:
Dojo objects are supported in UFT only when the UFT Web Add-in and Dojo sub-add-in are installed and loaded.
Dojo test objects extend test objects from the UFT Web Add-in and inherit many of their methods and properties from those objects.