Explore topic-wise InterviewSolutions in .

This could be tested through the AUTOMATED TEST TOOLS like RATIONAL robot and winrunner.

This could be tested through the automated test tools like rational robot and winrunner.

System testing is a TYPE of Black box testing. System testing MEANS testing the APPLICATION. After the integration testing, usually will do system testing. FUNCTIONALITY, Regression, and performance testing’s comes under system testing.

System testing is a type of Black box testing. System testing means testing the application. After the integration testing, usually will do system testing. Functionality, Regression, and performance testing’s comes under system testing.

RETESTING is the REPEATED execution of the test case which results in a fault,with the AIM that fault has been cured,Regression testing is the RENEWED testing of already tested program or PART after modification with the aim that the modification had.

Retesting is the repeated execution of the test case which results in a fault,with the aim that fault has been cured,Regression testing is the renewed testing of already tested program or part after modification with the aim that the modification had.

In both of the TEST we are performing Load and Performance TESTING. Testing the application in intranet (WITHOUT browser) is an example for client -server. Testing an application in INTERNET (using browser) is CALLED web testing.

In both of the Test we are performing Load and Performance Testing. Testing the application in intranet (without browser) is an example for client -server. Testing an application in internet (using browser) is called web testing.

WITHOUT USING GUI map Editor, We can recognize the Application in WinRunner by using RAPID Test SCRIPT Wizard, but it is also recognize only Client server application, not Web based application.

Without Using GUI map Editor, We can recognize the Application in WinRunner by using Rapid Test Script Wizard, but it is also recognize only Client server application, not Web based application.

There is one FORMULA to KNOW the NUMBER of test cases is Minimum Number of test cases=No. Of INPUTS *1.6

There is one formula to know the number of test cases is Minimum Number of test cases=No. Of inputs *1.6

Effective TEST CASE CONTAIN Test case description, test i/p DATA,exp o/p and actual o/p.

Effective test case contain Test case description, test i/p data,exp o/p and actual o/p.

A hot key is a key or a combination of keys on a computer keyboard when pressed performs a task. The specific task performed by a particular hot key varies by OPERATING SYSTEM or application. However, there are commonly-used hot keys. For EXAMPLE, pressing

A hot key is a key or a combination of keys on a computer keyboard when pressed performs a task. The specific task performed by a particular hot key varies by operating system or application. However, there are commonly-used hot keys. For example, pressing

.mtb

.mtb

Test Result FILE bar, MENU bar, Test RESULTS TOOL bar, Test result tree, Test result details, Status bar.

Test Result File bar, Menu bar, Test results tool bar, Test result tree, Test result details, Status bar.

TREE & EXPERT

Tree & Expert

• CREATING TESTS
• RUNNING Tests
• ANALYZING Tests.

4 TYPES of EXCEPTIONS are there:
1)Pop-Up exceptions
2)Object State exceptions
3)Test RUN error exceptions
4)Application Crash exceptions

4 Types of Exceptions are there:
1)Pop-Up exceptions
2)Object State exceptions
3)Test Run error exceptions
4)Application Crash exceptions

Output values are values we can get those values from our application. We can put those values in DATA table and wherever we WANT we can use those values. In Parameterizing Tests, you CREATED parameters that INSERTED different data into each iteration of a TEST run. You can also retrieve data from your application and output it to the Data Table, using output values. This data can then be used at a later stage in the test. QuickTest displays the retrieved data, following the test run, in the Runtime Data Table.

Output values are values we can get those values from our application. We can put those values in data table and wherever we want we can use those values. In Parameterizing Tests, you created parameters that inserted different data into each iteration of a test run. You can also retrieve data from your application and output it to the Data Table, using output values. This data can then be used at a later stage in the test. QuickTest displays the retrieved data, following the test run, in the Runtime Data Table.

FUNCTIONS are 2 types: 
1)VB Script Functions-abs,now….etc
2) USER defind Functions

Functions are 2 types: 
1)VB Script Functions-abs,now….etc
2) User defind Functions

•  QTP is icon based testing tool.
•  QTP uses VB script while winRunner uses TSL which is C language based.
•  QTP has Recovery Manager .Win Runner 7.5 ALSO having Recovery Manager.
•  QTP generates output values and these can be used as input values to other Objects.
• QTP has USERFRIENDLY Browser, At a glance we can have a look of scripts ,Active Screen and Data XL sheet.
•  In QTP we can’t put Runtime DATABASE check Point. In win runner we can.

Text Checkpoint—Enables you to check that the text is displayed in a SCREEN, window, or Web page, according to SPECIFIED CRITERIA. It is supported for all environments
Text AREA Checkpoint—Enables you to check that a text string appears within a defined area in a WINDOWS application, according to specified criteria. It is supported for Standard Windows, Visual Basic, and ActiveX environments.

Text Checkpoint—Enables you to check that the text is displayed in a screen, window, or Web page, according to specified criteria. It is supported for all environments
Text Area Checkpoint—Enables you to check that a text string appears within a defined area in a Windows application, according to specified criteria. It is supported for Standard Windows, Visual Basic, and ActiveX environments.

We STORE data in the Global tab when we want it to be available to all actions in our TEST, for EXAMPLE, to PASS parameters from one action to another.
We store data in the action’s tab when we want it to be available to only one action in our test.

We store data in the Global tab when we want it to be available to all actions in our test, for example, to pass parameters from one action to another.
We store data in the action’s tab when we want it to be available to only one action in our test.

TEST pane—Contains the TREE View and Expert View tabs
Test Details pane—Contains the Active Screen
Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, VARIABLES, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug TOOLBAR by choosing View > Debug Viewer.)

Test pane—Contains the Tree View and Expert View tabs
Test Details pane—Contains the Active Screen
Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug toolbar by choosing View > Debug Viewer.)

we can import DATA from a database by SELECTING a QUERY from Microsoft Query or by manually specifying an SQL statement
Right-click on the Data Table SHEET to which you want to import the data and select Sheet > Import > from Database. The Database Query Wizard opens. Select your database selection preferences like create query using Microsoft query or specify SQL statement manually and click next. After words by specifying connecting STRING and SQL statements. We can get data from database to data table.

we can import data from a database by selecting a query from Microsoft Query or by manually specifying an SQL statement
Right-click on the Data Table sheet to which you want to import the data and select Sheet > Import > from Database. The Database Query Wizard opens. Select your database selection preferences like create query using Microsoft query or specify SQL statement manually and click next. After words by specifying connecting string and SQL statements. We can get data from database to data table.

Virtual objects enable you to record and run tests on objects that are not normally RECOGNIZED by QuickTest. We can teach QuickTest to recognize any area of your APPLICATION as an object by defining it as a virtual object.Some TIMES QTP may not recognize some objects. In this kind of situations Using New Virtual Object we can CONVERT Custom Objects into standard Objects.

Virtual objects enable you to record and run tests on objects that are not normally recognized by QuickTest. We can teach QuickTest to recognize any area of your application as an object by defining it as a virtual object.Some times QTP may not recognize some objects. In this kind of situations Using New Virtual Object we can convert Custom Objects into standard Objects.

com interface appears in the scenario of front end and BACK end. for eg:if you are using oracle as back end and front end as VB or any LANGUAGE then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that program can use the methods on the specified object. It is used for IMPLEMENTING Automation (as defined by Microsoft).

com interface appears in the scenario of front end and back end. for eg:if you are using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that program can use the methods on the specified object. It is used for implementing Automation (as defined by Microsoft).

Name WOULD be ANOTHER property apart from title that we can USE.

Name would be another property apart from title that we can use.

Object Repository: displays a tree of all objects in the current component or in the current ACTION or entire test (depending on the object repository mode you SELECTED). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and DETERMINES in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a SPECIAL Ordinal identifier such as objects location on the page or in the SOURCE code.

Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.

A RED color indicates failure. Here we ANALYZE the cause for failure whether it is a Script Issue or Environment Issue or a APPLICATION issue.

A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

ADHOC TESTING is DONE. It Covers the LEAST basic FUNCTIONALITIES to verify that the system is working fine.

Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.

Batch Testing in WR is nothing but RUNNING the whole test set by selecting RUN Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set all the test SCRIPTS can be executed. In this process the Scripts get executed one by one by KEEPING all the remaining scripts in Waiting mode.

Batch Testing in WR is nothing but running the whole test set by selecting Run Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in Waiting mode.

There are four types of parameters: Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test. Data Table parameters enable you to create a data-driven test (or action) that RUNS several times using the data you supply. In each repetition, or iteration, Quick Test USES a different value from the Data Table. Environment variable parameters enable you to use variable values from other sources during the run session. These MAY be values you supply, or values that Quick Test GENERATES for you based on conditions and options you CHOOSE. Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have Quick Test generate a random number and insert it in a number of tickets edit field.

There are four types of parameters: Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test. Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, Quick Test uses a different value from the Data Table. Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that Quick Test generates for you based on conditions and options you choose. Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have Quick Test generate a random number and insert it in a number of tickets edit field.

Image CHECKPOINTS enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area WITHIN an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after ONE click on the control key that zooms in the map. USING the bitmap checkpoint, you can check that the map zooms in CORRECTLY. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). 

Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). 

When you test your application, you may want to check how it PERFORMS the same operations with multiple SETS of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate TESTS, each with its own set of data. ALTERNATIVELY, you can CREATE a parameterized test that runs ten times: each time the test runs, it uses a different set of data.

When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.

We can add CHECKPOINTS while recording the APPLICATION or we can add after recording is completed USING Active screen.

We can add checkpoints while recording the application or we can add after recording is completed using Active screen.

It contains the FOLLOWING key elements: Title bar, displaying the name of the currently OPEN test, Menu bar, displaying menus of Quick Test commands, File TOOLBAR, containing buttons to ASSIST you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first TIME. You can display the Debug toolbar by choosing View — Toolbars — Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View — Toolbars — Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View ,Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test. Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.) Status bar, displaying the status of the test

It contains the following key elements: Title bar, displaying the name of the currently open test, Menu bar, displaying menus of Quick Test commands, File toolbar, containing buttons to assist you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first time. You can display the Debug toolbar by choosing View — Toolbars — Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View — Toolbars — Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View ,Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test. Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.) Status bar, displaying the status of the test

Quick Test testing process consists of 6 main phases:

Create your test plan –
Prior to AUTOMATING there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data VALIDATIONS and existence or STATE verifications of objects in the application.

Recording a session on your application –
As you NAVIGATE through your application, Quick Test graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user ACTION that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.

Enhancing your test –
Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly. NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process. Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

Debugging your test –
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
Running your test on a new version of your application You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.

Analyzing the test results –
You examine the test results to pinpoint defects in your application.

Reporting defects –
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

Quick Test testing process consists of 6 main phases:

Create your test plan –
Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.

Recording a session on your application –
As you navigate through your application, Quick Test graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.

Enhancing your test –
Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly. NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process. Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

Debugging your test –
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
Running your test on a new version of your application You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.

Analyzing the test results –
You examine the test results to pinpoint defects in your application.

Reporting defects –
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

Quick Test Professional supports FUNCTIONAL testing of all ENTERPRISE environments, including Windows, Web,..NET, Java/J2EE, SAP, Siebel, ORACLE, PEOPLESOFT, Visual Basic, ActiveX, MAINFRAME terminal emulators, and Web services.

Quick Test Professional supports functional testing of all enterprise environments, including Windows, Web,..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.

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 Test Fusion reports with Quick Test 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 Test Fusion reports with Quick Test Professional, you can share reports across an entire QA and development team.

You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without PROGRAMMING, to EXPAND test case COVERAGE. Data can be TYPED in or imported from databases, spreadsheets, or text files.

You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.

There are two WAYS to Spy the objects in QTP:
1) through file toolbar, In the File Toolbar click on the last toolbar BUTTON (an icon SHOWING a person with hat).
2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and RELEASE the Ctrl button.

There are two ways to Spy the objects in QTP:
1) through file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat).
2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.

OUTPUT values ENABLE to view the values that the application TALKS 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.

Output values enable to view the values that the application talks 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.

There are 4 trigger events during which a recovery scenario should be activated. A pop up WINDOW appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions. You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager PROVIDES a WIZARD that guides you through the DEFINING recovery scenario.
Recovery scenario has three steps:
1. Triggered Events
2. Recovery steps
3. POST Recovery Test-Run

There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions. You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario.
Recovery scenario has three steps:
1. Triggered Events
2. Recovery steps
3. Post Recovery Test-Run

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.

DATA DRIVER is ONE WAY of parameterizing the SCRIPT.

Data Driver is one way of parameterizing the script.

Open Object REPOSITORY-> Add/Remove Object
Or
Record it USING Low LEVEL RECORDING.

Open Object Repository-> Add/Remove Object
Or
Record it using Low level Recording.

Debugging is used to view, set, or modify the current VALUE of objects or variables. It can be done by clicking on debug viewer pane, when TEST stop at any BREAKPOINT or the test PAUSES at any STEP due to error.

Debugging is used to view, set, or modify the current value of objects or variables. It can be done by clicking on debug viewer pane, when test stop at any breakpoint or the test pauses at any step due to error.

Go to keyword VIEW->Right click on ACTION->Action PROPERTIES
CHECK the Re-usable Action Checkbox.

Go to keyword view->Right click on Action->Action Properties
Check the Re-usable Action Checkbox.

To VIEW the PROPERTIES and METHODS of Test objects and RUN time objects.

To view the Properties and Methods of Test objects and Run time objects.

C:\ Program FILES\ Mercury INTERACTIVE\ QUICK TEST Professional\ Tests

C:\ Program Files\ Mercury Interactive\ Quick Test Professional\ Tests

YES and the NAVIGATION are:
Insert-> CALL to WIN RUNNER

Yes and the navigation are:
Insert-> call to win Runner

If we WANT to run an action for a particular NUMBER of TIMES then we GO for LOOPS.

If we want to run an action for a particular number of times then we go for Loops.

The PROGRAMMATIC DESCRIPTION will IDENTIFY the object from the application WITHOUT the help of Object repository.

The programmatic description will identify the object from the application without the help of Object repository.

YES, we can run tests without adding objects in your REPOSITORY USING Descriptive PROGRAMMING.

Yes, we can run tests without adding objects in your repository using Descriptive programming.