Featured

0 IIS setting for 64 bit Win 7

 

Working with 64-bit Systems

Unfortunately there are no 64-bit ODBC drivers, so on 64-bit systems you will have to run your applications in 32-bit mode. To do so, use the following steps:
  1. On the taskbar, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the Connections pane, click Application Pools.
  3. Highlight the application pool for your application, then click Advanced Settings... in the Actions pane.
  4. In the Advanced Settings dialog, specify True for Enable 32-Bit Applications.
  5. Click OK to close the Advanced Settings dialog.
Read more

0 QC-Business Components fail to run

Failed :
Initialize_Script: You do not have permissions to run business components on this machine. You can change this option in your testing tool's Options dialog box.










Goto QTP Menu Tools>Options and do as below

Read more

0 Steps to call any QTP Action first

You can make QTP to call any Reusable Action to be called first when the Test starts..

Steps to call any QTP Action first.
1. Go to Keyword View
2. Select the Action that you want to call first in the test.
3. Drag it to the topmost position.
4. Save the test and Run.



Read more

0 Cannot launch scanner, verify your QTP installation - SAP TAO

Cannot launch scanner, verify your QTP installation - SAP TAO


Solution:
- Check the same with any other machine
- Run the Self-Check in SAP TAO
- Restart the server and try to work and see if it is getting solved
Read more

0 HLLAPI DLL was not found


  - If the QuickTest Professional Terminal Emulator Add-in is installed and loaded, but there is no terminal emulator installed on your computer, the following error message is displayed: QuickTest Terminal Emulator support is not configured correctly. Either the terminal emulator is not installed on your computer or the HLLAPI DLL was not found.

Workaround: When you open QuickTest, clear the Terminal Emulators check box in the Add-in Manager. 

You can prevent this message from appearing by adjusting your emulator's configuration settings.
When working with an emulator that does not support HLLAPI, or with an emulator that has been configured as supporting text-only HLLAPI operations, do not change the size of the terminal emulator window after configuring the emulator settings.

When installing a Hummingbird HostExplorer terminal emulator or patches, make sure that QuickTest Professional is closed.

To enable support for a NetManage Web-To-Host Java Client session that is configured to open in a separate window, specify the title of your session window using the Tools > Options > Terminal Emulator > Adjust Configuration > Object identification settings > Identify emulator window based on title bar prefix option.


  • The QuickTest Professional Terminal Emulator Add-in can identify emulator window objects only when the emulator is connected. For example, you cannot use the following statement to connect to an emulator session:

  • TeWindow("TeWindow").WinMenu("Menu").Select "Communication;Connect"
    Read more

    0 HLLAPI

    HLLAPI is an acronym for High Level Language Application Program Interface.
    HLLAPI was developed so that external programs can be written to interact with a host session.
    Read more

    1 QTP and Terminal Emulator tutorial

    1. Terminal Emulator is an Add-in used to recognize Mainframe Screens/Dos Prompts....what ever is command prompt to be generic...
    2. You need to get the add-in installed for your version of QTP, its available from HP,

    3. Screen & Field's are the two controls that are recognized by this Add-in

    4. Key Press events are functions that operates in case of navigation.

    5. Install it & enjoy.


    To ensure that QuickTest and your terminal emulator integrate successfully while recording a test or component, open and connect your terminal emulator session before recording begins. While running tests or components, you can add a SystemUtil.Run statement to the beginning of your test or component to automatically launch your emulator session from QuickTest. For more information, refer to the Utility section of the HP QuickTest Professional Object Model Reference.

    If your terminal emulator has an option to automatically resize the terminal emulator window according to the font size, then it should be enabled. For example, in the EXTRA! 6.7 emulator, choose Settings > Font > Autosize window to font size.

    You can run tests or components using the QuickTest Professional Terminal Emulator Add-in from other HP products, for example, Quality Center. Before you run these tests or components, make sure you select the required emulator on the computer on which the test or component is to run, using the QuickTest Tools > Options >Terminal Emulator tab.  
    Read more

    0 QTP Naming Conventions


    Checkbox = chk   
    Dialog Box = dbDisplay = displ                                                         
    Icon = icLabel = lbl
    Links = linkList Box = lb                                                            
    List View = lvLogo = logo     
    Menu = mMenu Item = mi                                                       
    Message Box = mbPopup List = poplst  
    Push Button = pbRadio Button = rb                                                   
    Scroll Bar = sbStatic Text = stxt                                                     
    Status Bar = stbrTab = tab                                                                
    Table = tblText Box = txt                                                        
    Tool Bar = tbTree View = tv                                                      
    Header = hdrPanel = pan                                                              
    Status Window = stwinSplitter = sp                                                            
    Container = ctnNavigation bar = nb                                                
    Grid = grdCombo box = cbx                                                    
    Window = win         

    Test Scripts

     The test scripts name
    • Must consist of alphabets, numbers and ‘_’.
    • Must start with an upper case letter.
    • If more than one word is used, the starting of every word must be in Upper case.      (Eg: Test_Script)
    • Name of the script must be in the format – Application/Test group, Feature/Action Number (XYZ_01).

    VBS Files

    • A  VBScript file name must consist of alphabets.
    • Name should preferably be in the format Project_Module_Function

    Functions

    • Must consist of alphabets.
    • Must start with ‘func’.
    • Name must stand for the functionality of the function.
    • If more than one word is used, the starting of every word should be in capitals.
    • Numerical are not allowed in the names
              Eg:  Public function funcOpenWindow (in window_name) 

     Constants and Variables

    • Name of a constant must be in upper case letters with underscores in it.  Eg: public const OR_PATH_DIR= c:\\mytests\\Action1; 
    • Name of a variable must be of lowercase letters and can contain underscores and digits. Eg: public my_variable_name=”This is my variable”;
    ·        Declare all the variables using DIM.

    Object Repository

    • Object repository file name must consist of alphabets and should be like project_Module_Function.tsr.
    • If the name of an object or window is ambiguous, then it must be renamed in the format ObjectType_Label. Eg: Button_Done, Window_EngagementSummry, Checkbox_Overage, Radio_Awarded etc.
    • If more than one word is used, the starting of every word should be in capitals.

    Recovery Manager

    • Name of a Recovery Manager file must be of alphabets and if necessary digits.
    • The files must be of the format Project_Module_Function_in.qrs.
    Read more
  • Recent Posts

     
    © QTPCode | Design by Blog template in collaboration with Concert Tickets, and Menopause symptoms
    Powered by Blogger