2008-Dec-6 - QuickTest Professional Terminal Emulator Add-in

Welcome to the QuickTest Professional Terminal Emulator Add-in

You can use the QuickTest Professional Terminal Emulator Add-in to test applications running on most terminal emulators. The QuickTest Professional Terminal Emulator Add-in recognizes your terminal emulator and records and runs the operations you perform on the screens and fields of the running application.

You can use QuickTest Professional with the Terminal Emulator Add-in to test applications on terminal emulators that support HLLAPI (High Level Language Application Programming Interface) as well as those that do not, for example, emulator sessions configured to work with the VT100 protocol (using the Text-only option). HLLAPI allows a PC application to communicate with a mainframe application with extended capabilities.

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

The QuickTest Professional Terminal Emulator Add-in includes preconfigured settings for several terminal emulators. The Terminal Emulator Add-in also enables you to configure the settings for most other terminal emulators using the Terminal Emulator Configuration Wizard.

The Terminal Emulator Configuration Wizard guides you through the process of configuring the settings QuickTest needs to identify your terminal emulator. If your emulator is not in the list of preconfigured settings to select, you can define the way QuickTest identifies your emulator.  

2008-Dec-6 - Checking Java Environment Variables Settings

Checking Java Environment Variables Settings

This section describes the environment variables that need to be set when you load your Java application with QuickTest Java Add-in support. For all of the environments, you need to set one or more environment variables to the short path name of the Java Add-in support classes’ folder.

Sun Java 2 (Version 1.2 or Later) or IBM Java 2 (Version 1.2 or Later)

Set the _JAVA_OPTIONS environment variable (Sun) or the IBM_JAVA_OPTIONS environment variable (IBM) as follows:

-Xrunjvmhook -Xbootclasspath/a:\MERCUR~1\FUNCTI~1\Java\classes;\MERCUR~1\FUNCTI~1\Java\classes\jasmine.jar

The above settings should appear on one line (no newline separators).

Note: denotes the short path of the Common Files folder located under Program Files. For example, if the Common Files folder is located in C:\Program Files\Common Files, then the value for -Xbootclasspath is as follows:

-Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\jasmine.jar

Microsoft Java Virtual Machine (JVM) - Internet Explorer/JView

2008-Nov-14 - Features of QTP

Features of QTP

Ø    Scripting Language is VBScript which is easy to use, understand and program even complex functionalities with ease.

Ø    Uses “Active Screen” technology to record scripts which aids the tester in referring to the screens object properties.

Ø    Library files contain VBScript functions and subroutines that can be added to the test.

Ø    Support Modern Development Environment.

2008-Nov-13 - Which Test Cases to Automate?

Before start-off Automation, we need to do Feasibility Analysis. It is must.

Which Test Cases to automate?

Ø  Tests that need to be run for every build of the application

Ø  Tests that use multiple data values, (using Data Parametrization)

Ø  Stress testing

Ø  Load testing

Ø  Tests requiring a great deal of precision/accuracy

2008-Nov-11 - Learn Automation Quickly

2008-Nov-11 - Why Automation?

Why Test Automation?

The following points elucidate the reasons behind the need for automation (selective and not exhaustive):

·         Running the existing tests on a new version(s) of a program/application

·