Explore topic-wise InterviewSolutions in .

Check point CAPTURE the VALUE but not STORE it. Output value CAPTURES the value and stores that value in data table.

Check point capture the value but not store it. Output value captures the value and stores that value in data table.

CURRENTLY QTP 9.2 BETA VERSION is in the MARKET.

Currently QTP 9.2 beta version is in the market.

VARIANT is the only ONE DATA type USED in qtp.

Variant is the only one data type used in qtp.

There are TWO types of OBJECT repository in QTP

1. LOCAL
2. SHARED

There are two types of object repository in qtp

DATABASE & XML

Database & XML

There are 3 TYPES of ACTIONS available in QTP

1. Reusable
2. non-reusable
3. extern Action

There are 3 types of actions available in QTP

FRAME Work:

1. SMOKE Testing - ENVIRONMENTAL checkup of the application.
2. Driver - Business functionality
3. Application Business Functionality Execution
4. VERIFICATION checker
5. Reporter generation
6. Terminator

Frame Work:

QTP INTEGRATED components LIKE DBConnection, DATATABLE and REPORTERS can be customized.

QTP Integrated components like DBConnection, Datatable and Reporters can be customized.

QTP is BASED on TWO concept:
► Recording
► PLAYBACK

QTP is based on two concept:
► Recording
► Playback

QTP provides three TYPES of recording METHODS:
► CONTEXT Recording (Normal)
► Analog Recording
► LOW Level Recording

QTP provides three types of recording methods:
► Context Recording (Normal)
► Analog Recording
► Low Level Recording

QTP USING VB SCRIPTING.

QTP using VB scripting.

QTP testing process CONSIST of SEVEN steps:
► Preparing to recoding
► Recoding
► Enhancing your SCRIPT
► Debugging
► Run
► ANALYZE
► Report Defects

QTP testing process consist of seven steps:
► Preparing to recoding
► Recoding
► Enhancing your script
► Debugging
► Run
► Analyze
► Report Defects

QTP provides THREE TYPES of PARAMETER:
► Method ARGUMENT
► Data Driven
► Dynamic

QTP provides three types of Parameter:
► Method Argument
► Data Driven
► Dynamic

QuickTest stores the definitions for application objects in a FILE called the Object Repository. As you record your test, QuickTest will add an entry for each item you INTERACT with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a SET of properties (type, name, ETC) that uniquely identify each object. Each line in the QuickTest script will contain a reference to the object that you interacted with, a CALL to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

Once a tester has run a test, a Test FUSION report displays all aspects of the test run: a high-level results overview, an expandable TREE View of the test specifying exactly where application FAILURES occurred, the test data USED, application screen shots for every step that highlight any DISCREPANCIES, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

Once a tester has run a test, a Test Fusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

The page checkpoint checks that the number of links and images in the page when you run your test is the same as when you recorded your test.
1 LOCATE the page where you want to ADD a page checkpoint.
2 Create a page checkpoint.
Right-click anywhere in the Active Screen, and CHOOSE Insert Standard Checkpoint. The Object Selection - Checkpoint Properties DIALOG BOX opens. 
3 Save the test.

The page checkpoint checks that the number of links and images in the page when you run your test is the same as when you recorded your test.
1 Locate the page where you want to add a page checkpoint.
2 Create a page checkpoint.
Right-click anywhere in the Active Screen, and choose Insert Standard Checkpoint. The Object Selection - Checkpoint Properties dialog box opens. 
3 Save the test.

Output values enable to view the values that the application TAKES during RUN time. When parameterized, the values change for each iteration.Thus by CREATING output values, we can capture the values that the application takes for each run and output them to the data table.

Text output value is future in QTP, this is used for capturing a text value from the application under test, during the run time. Captures the value from the OBJECT(object in the SENSE may from the edit box, combobox) and stores it under a specified column in the run time data table.

Output values enable to view the values that the application takes during run time. When parameterized, the values change for each iteration.Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.

Text output value is future in QTP, this is used for capturing a text value from the application under test, during the run time. Captures the value from the object(object in the sense may from the edit box, combobox) and stores it under a specified column in the run time data table.

By DEFAULT QTP runs first ACTION1, but it is possible to run with Action 2 or other by DRAG and DROP action 2 to action1 and then run the action 2.

By default QTP runs first action1, but it is possible to run with Action 2 or other by drag and drop action 2 to action1 and then run the action 2.

Choose TEST > RECORD or click the Record button.
When the Record and Run Settings dialog box opens to do this;
1. In the Web tab, SELECT Open the following browser when a record or run session begins.
2. In the Windows Applications tab, CONFIRM that Record and run on these applications (opened on session start) is selected, and that there are no applications listed.

Choose Test > Record or click the Record button.
When the Record and Run Settings dialog box opens to do this;
1. In the Web tab, select Open the following browser when a record or run session begins.
2. In the Windows Applications tab, confirm that Record and run on these applications (opened on session start) is selected, and that there are no applications listed.

1. Start QuickTest and open your test.
In the Open Test dialog box, locate and SELECT your test, then CLICK Open.

2. SAVE the test as Checkpoint.
Select File > Save As. Save the test as Checkpoint.

3. Confirm that the Active Screen option is enabled.
If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button, or choose View > Active Screen.

4. Locate the page where you want to add a standard checkpoint.

5 CREATE a standard checkpoint.
In the Active Screen, right-click element in your application and choose Insert Standard Checkpoint.

6 Save the test.

1. Start QuickTest and open your test.
In the Open Test dialog box, locate and select your test, then click Open.

2. Save the test as Checkpoint.
Select File > Save As. Save the test as Checkpoint.

3. Confirm that the Active Screen option is enabled.
If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button, or choose View > Active Screen.

4. Locate the page where you want to add a standard checkpoint.

5 Create a standard checkpoint.
In the Active Screen, right-click element in your application and choose Insert Standard Checkpoint.

6 Save the test.

A CHECKPOINT verifies that EXPECTED information is DISPLAYED in your APPLICATION while the test is RUNNING.

A checkpoint verifies that expected information is displayed in your application while the test is running.

From the Test results VIEWER "TOOLS > FILTERS > Warnings"...MUST be "Unchecked".

From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

Expert View: It represents the script in VB script FORMAT

Keyword View: It represents the script using graphical user interface, which is further divided into FOUR parts.

1. Item
2. Operation
3. VALUE
4. Documentation

Expert View: It represents the script in VB script format

Keyword View: It represents the script using graphical user interface, which is further divided into four parts.

Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving CAPABILITY. IDENTIFIES objects with Unique Smart OBJECT Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a SINGLE step with Auto-documentation technology. Enables through validation of applications through a full complement of checkpoints.

Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables through validation of applications through a full complement of checkpoints.

USING the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected objects hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

Object Spy is feature PROVIDED by QTP which shows the COMPLETE object information like list of properties, list of methods, syntax of methods, and DESCRIPTION of methods for both test objects as well as runtime and test objects by POINTING the object spy pointer on the object.

Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected objects hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

Object Spy is feature provided by QTP which shows the complete object information like list of properties, list of methods, syntax of methods, and description of methods for both test objects as well as runtime and test objects by pointing the object spy pointer on the object.

There are 3 types of recording modes in QTP, Context Sensitive (NORMAL), Analog Recording mode and Low Level Recording mode. Context Sensitive RECORDS the OBJECTS in the application and OPERATIONS performed on them. Analog records all MOUSE exact mouse and keyboard actions. Low level enables to record on any object.

There are 3 types of recording modes in QTP, Context Sensitive (normal), Analog Recording mode and Low Level Recording mode. Context Sensitive records the objects in the application and operations performed on them. Analog records all mouse exact mouse and keyboard actions. Low level enables to record on any object.

QTP STRUCTURED by actions. Actions are sub procedures which perform certain events on AUT. There are 2 types of actions. Regular actions (non reusable actions) and reusable actions. Regular actions are USED only in the script where the action exists.

QTP structured by actions. Actions are sub procedures which perform certain events on AUT. There are 2 types of actions. Regular actions (non reusable actions) and reusable actions. Regular actions are used only in the script where the action exists.

In SWE section we need to ADD AutomationEnable = TRUE and at the same TIME you need to USE SWECmd= AutoOn in the URL.

In SWE section we need to add AutomationEnable = TRUE and at the same time you need to use SWECmd= AutoOn in the URL.

RECOVERY SCENARIO manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has four steps
1. Triggered Events
2. Recovery steps
3. Post Recovery
4.Name and FINISH

Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has four steps
1. Triggered Events
2. Recovery steps
3. Post Recovery
4.Name and Finish

An OUTPUT value is a value retrieved during the run session and entered into runtime table or data table subsequently it can be used as INPUT value in your test. Checkpoint ENSURES the functionality of an OBJECT by verifying the STATE of an object during the runtime.

An output value is a value retrieved during the run session and entered into runtime table or data table subsequently it can be used as input value in your test. Checkpoint ensures the functionality of an object by verifying the state of an object during the runtime.

It cannot store OBJECTS when it REACHES MAXIMUM Size (2MB). We cannot do changes to an object by tester at the same TIME.

It cannot store objects when it reaches maximum Size (2MB). We cannot do changes to an object by tester at the same time.

Per ACTION: For Each Action, ONE Object Repository is created.
SHARED: Single Object Repository will be USED for all actions.

Per Action: For Each Action, one Object Repository is created.
Shared: Single Object Repository will be used for all actions.

In QTP there are 2 object repositories, SHARED Object Repository and PER Action Mode.
Default mode is Per-Action. In Shared, we use only one OR that is common to all actions and can SHARE by other testers. It's like calling external libraries. We will use per action OR for a each action EXCLUSIVELY.

In QTP there are 2 object repositories, Shared Object Repository and Per Action Mode.
Default mode is Per-Action. In Shared, we use only one OR that is common to all actions and can share by other testers. It's like calling external libraries. We will use per action OR for a each action exclusively.

During RECORDING QTP looks at the object and STORES it as test object. For each test object QTP learns a SET of default properties called mandatory properties and look at the rest of the objects to check whether this properties are enough to uniquely identify the same object during test run.

During recording QTP looks at the object and stores it as test object. For each test object QTP learns a set of default properties called mandatory properties and look at the rest of the objects to check whether this properties are enough to uniquely identify the same object during test run.

Quick Test Pro environment uses the graphical interface and ACTIVE Screen technologies. A testing process for creating test scripts, relating manual test requirements to automated VERIFICATION features - Data driving to USE several sets of data using parameters.

Quick Test Pro environment uses the graphical interface and Active Screen technologies. A testing process for creating test scripts, relating manual test requirements to automated verification features - Data driving to use several sets of data using parameters.

When we INSERT Call to Existing Action, they are read only in the calling test. It can only be modified in the ORIGINAL test. Where as come to Copy of Action, you can make changes to the copied action. Changes will not EFFECT the original action where it created.

When we insert Call to Existing Action, they are read only in the calling test. It can only be modified in the original test. Where as come to Copy of Action, you can make changes to the copied action. Changes will not effect the original action where it created.

Using PARAMETERIZATION feature we can enhance test or COMPONENT by parameterize the values that it uses. A Parameter is VARIABLE that is ASSIGNED a value from the external data source. There are 4 types of parameters like Test/Action or Component, Data Table parameter, Random Number and ENVIRONMENT Parameter. Data Driving enables to parameterize several property values for test objects, checkpoints.

Using parameterization feature we can enhance test or component by parameterize the values that it uses. A Parameter is variable that is assigned a value from the external data source. There are 4 types of parameters like Test/Action or Component, Data Table parameter, Random Number and Environment Parameter. Data Driving enables to parameterize several property values for test objects, checkpoints.

During the run SESSION, Quick Test creates a run-time Data Table—a LIVE version of the Data Table associated with your test or component. When the run session ends, the run-time Data Table closes, and the Data Table PANE again displays the stored design-time Data Table. Data ENTERED in the run-time Data Table during the run session is not SAVED with the test or component. The final data from the run-time Data Table is displayed in the Run-Time Data Table in the Test Results window

During the run session, Quick Test creates a run-time Data Table—a live version of the Data Table associated with your test or component. When the run session ends, the run-time Data Table closes, and the Data Table pane again displays the stored design-time Data Table. Data entered in the run-time Data Table during the run session is not saved with the test or component. The final data from the run-time Data Table is displayed in the Run-Time Data Table in the Test Results window

Quick TEST AUTOMATE the testing of your APPLICATIONS, we can use the QTP Automation Object Model to automate your Quick Test operations. Using the objects, methods, and properties exposed by QuickTest's AOM, we can WRITE programs that configure Quick Test options and run tests instead of performing these operations manually using the Quick Test interface.

Automation programs are especially useful for performing the same tasks multiple times or on multiple tests or components, or quickly configuring Quick Test according to your needs for a particular environment or application.

Quick Test automate the testing of your applications, we can use the QTP Automation Object Model to automate your Quick Test operations. Using the objects, methods, and properties exposed by QuickTest's AOM, we can write programs that configure Quick Test options and run tests instead of performing these operations manually using the Quick Test interface.

Automation programs are especially useful for performing the same tasks multiple times or on multiple tests or components, or quickly configuring Quick Test according to your needs for a particular environment or application.

We use “TITLE” PROPERTY to IDENTIFY browser and web PAGE.

We use “title” property to identify browser and web page.

CREATES and returns a reference to an AUTOMATION object.
Example: ES = CreateObject ("Excel.Sheet")

Creates and returns a reference to an Automation object.
Example: ES = CreateObject ("Excel.Sheet")

VBSCRIPT, JAVA Script and WINDOWS Script Host(WSH)

VBScript, Java Script and Windows Script Host(WSH)

USING GETRO PROPERTY we will HANDLE the RUNTIME OBJECTS.

Using GETRO Property we will handle the runtime objects.

IMPORT from External Spreadsheet File by selecting Import then From File . This imports a tabbed text file or a single SHEET from an existing MICROSOFT Excel file into the table. The sheet you import REPLACES all data in the currently selected.

Import from External Spreadsheet File by selecting Import then From File . This imports a tabbed text file or a single sheet from an existing Microsoft Excel file into the table. The sheet you import replaces all data in the currently selected.

3 TYPES of RECORDING modes in QTP.
1.normal 
2.analog mode
3.low LEVEL recording mode.

3 types of recording modes in QTP.
1.normal 
2.analog mode
3.low level recording mode.

FIRST of all we need to have a java add-in to handle a java tree. In tools option we have the "object identification" DROP down LIST. There we have the java option to recognize the objects there SELECT the tree option. Add the properties.

first of all we need to have a java add-in to handle a java tree. In tools option we have the "object identification" drop down list. There we have the java option to recognize the objects there select the tree option. Add the properties.

USING USER ACCEPTANCE TEST

Using user acceptance test

First check the requirements of the keyboard as we are FAMILIAR with keyboards, check the dimensions and DESIGN of the keyboard as requirements next checks the total no. of keys and check WHETHER all keys are present and present CORRECTLY in their specified.

First check the requirements of the keyboard as we are familiar with keyboards, check the dimensions and design of the keyboard as requirements next checks the total no. of keys and check whether all keys are present and present correctly in their specified.

Defect leakage defines the TIME GAP between DEFECTS FOUND to defect resolved.

Defect leakage defines the time gap between defects found to defect resolved.

Since testing comes at the last stage , there are huge chances of defect multiplication, defects will be migrated to EVERY stage wastage of HUMAN resources and time delays are ALSO introduced.

Since testing comes at the last stage , there are huge chances of defect multiplication, defects will be migrated to every stage wastage of human resources and time delays are also introduced.