QTP - Quick Test Professional Interview Questions And Answers

Explain the keyword createobject with an example.

2009-06-26T02:44:00.000-07:00

Ans) Creates and returns a reference to an Automation object . create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by microsoft).

Explain in brief about the QTP Automation Object Model.

2009-06-25T02:42:00.000-07:00

Ans) Essentially all configuration and run functionality provided via the QuickTest interface is in some way represented in the QuickTest automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in QuickTest have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods.
You can use the objects, methods, and properties exposed by the QuickTest automation object model, along with standard programming elements such as loops and conditional statements to design your program

What are the different scripting languages you could use when working with QTP?

2009-06-23T02:42:00.000-07:00

Ans) Visual Basic Script,XML,JavaScript,Java,HTML

Explain the keyword createobject with an example.

2009-06-22T02:42:00.000-07:00

What are the properties you would use for identifying a browser & page when using descriptive programming?

2009-06-21T02:41:00.000-07:00

Ans) Title is the property we use.ex: Browser("Title:="xxx").page("Title:="xxxx").....
"Name" would be another property apart from "title" that we can use.
Ex: Browser ("name:="xxx"").page("name:="xxxx"").....

Explain the concept of object repository & how QTP recognises objects?

2009-06-20T02:41:00.000-07:00

Ans) 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.

What is the file extension of the code file & object repository file in QTP?

2009-06-19T02:41:00.001-07:00

1.
Ans) for object repositories file the extension is .tsr
for code file the extension is .vbs

Qtp Pro Faq's II

2008-07-17T09:22:00.001-07:00

1. How Does Run time data (Parameterization) is handled in QTP?
A) 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.

2) What is keyword view and Expert view in QTP?
A) Quick Test’s Keyword Driven approach, test automation experts Have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.
Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard __VBScript that? Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

3) Explain about the Test Fusion Report of QTP?
A) Once a tester has run a test, a TestFusion 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.

4) To which environments does a QTP support?
A) QuickTest 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.

5) What is QTP?
A) QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications...

6) Explain QTP testing process?
A) The QuickTest testing process consists of 6 main phases:
1. 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.

2. Recording a session on your application
As you navigate through your application, QuickTest 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.
3. 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.
o 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.
o Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
4. Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
5. Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.
6. Analyzing the test results
You examine the test results to pinpoint defects in your application.
7. Reporting defects
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

7) Explain the QTP Tool interface.
A) It contains the following key elements:
Title bar, displaying the name of the currently open test
Menu bar, displaying menus of QuickTest 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 QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug. Note that this tutorial does not describe how to debug a test. For additional information, refer to the QuickTest Professional User's Guide.
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 QuickTest 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. For additional information, refer to the QuickTest Professional User's Guide . 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

8) How QTP recognizes Objects in AUT?
A) 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.

9) What are the types of Object Repository’s in QTP?
A) QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.
The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

10) Explain the check points in QTP?
A) . A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.
 A page checkpoint checks the characteristics of a Application
 A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
 An object checkpoint (Standard) checks the values of an object on a Application.
 An image checkpoint checks the values of an image on a Application.
 A table checkpoint checks information within a table on a Application
 An Accessibility checkpoint checks the web page for Section 508 compliance.
 An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
 A database checkpoint checks the contents of databases accessed by your web site
11) In how many ways we can add check points to an application using QTP.
A) We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).

12) How does QTP identifies the object in the application?
A) QTP identifies the object in the application by Logical Name and Class.
For example:
The Edit box is identified by
Logical Name: PSOPTIONS_BSE_TIME20
Class: WebEdit

13) If an application name is changes frequently i.e while recording it has name "Window1" and then while running its "Windows2" in this case how does QTP handles?
A) QTP handles those situations using "Regular Expressions".

14) What is Parameterizing Tests?
A) 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.

15) What is test object model in QTP?
A) The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.
A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.
A run-time object is the actual object in your Web site or application on which methods are performed during the run session.
When you perform an operation on your application while recording, QuickTest:
An identifies the QuickTest test object class that represents the object on which you performed the operation and creates the appropriate test object reads the current value of the object's properties in your application and stores the list of properties and values with the test object chooses a unique name for the object, generally using the value of one of its prominent properties records the operation that you performed on the object using the appropriate QuickTest test object method
For example, suppose you click on a Find button with the following HTML source code:

QuickTest identifies the object that you clicked as a WebButton test object.
It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton:
It also records that you performed a Click method on the WebButton.
QuickTest displays your step in the Keyword View like this:
QuickTest displays your step in the Expert View like this:
Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").Click

16) What is Object Spy in QTP?
A) 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 object's hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

Supported Check-Points in QTP?
17) What is the Diff between Image check-point and Bit map Check point?
A) 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. QuickTest 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 is loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

18) How many ways we can parameterize data in QTP?
A) 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, QuickTest 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 QuickTest 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 QuickTest generate a random number and insert it in a number of tickets edit field.

19. How do u do batch testing in WR & is it possible to do in QTP, if so explain?

Ans: Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid". The same is possible with QTP also. If our test cases are automated then by selecting "Run Testset" 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.

20. What does it mean when a check point is in red color? what do u do?

Ans : 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.

21. What do you call the window test director - testlab?

Ans : "Execution Grid". It is place from where we Run all Manual / Automated Scripts

22. How does u create new test sets in TD?

Ans : Login to TD.
Click on "Test Lab" tab.
Select the Desired folder under which we need to Create the Test Set. (Test Sets can be grouped as per module.)
Click on "New Test Set or Ctrl+N" Icon to create a Test Set.

23. How do u do batch testing in WR & is it possible to do in QTP, if so explain?

Ans : You can use Test Batch Runner to run several tests in succession. The results for each test are stored in their default location.

Using Test Batch Runner, you can set up a list of tests and save the list as an .mtb file, so that you can easily run the same batch of tests again, at another time. You can also choose to include or exclude a test in your batch list from running during a batch run.

24. If I give some thousand tests to execute in 2 days what do u do?

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

25. How to Import data from a ".xls" file to Data table during Runtime.

Ans : Datatable.Import "...XLS file name..."

DataTable.ImportSheet(FileName, SheetSource, SheetDest)
DataTable.ImportSheet "C:\name.xls" ,1 ,"name"

26. How to export data present in Datatable to an ".xls" file?

Ans : DataTable.Export "....xls file name..."

27. How to get Traceability matrix from TD?

28. How to import a test case present in ".xls" file to TD under a Test set?

29. How to attach a file to TD?

30. What do you to script when objects are removed from application?

31. Syntax for how to call one script from another and Syntax to call one "Action" in another?
Ans: RunAction ActionName, [IterationMode , IterationRange , Parameters]

Here the actions become reusable on making this call to any Action.

IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. "1-7"), or enter rngAll to run iterations on all rows.

If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction's RetVal argument.

32. How to export QTP results to an ".xls" file?
Ans : (a) By default it creates an "XML" file and displays the results

33. 3 differences between QTP & Winrunner?
Ans :
(a) QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
(b) QTP supports ".NET" application Automation not available in Winrunner
(c) QTP has "Active Screen" support which captures the application, not available in WR.
(d) QTP has "Data Table" to store script values , variables which WR does not have.
(e) Using a "point and click" capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

34. How to create a Runtime property for an object?

35. How to add a runtime parameter to a datasheet?

Ans:
DataTable.LocalSheet

The following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it.
MyParam=DataTable.LocalSheet.AddParameter("Time", "5:45")

36. What scripting language is QTP of?

Ans : Vbs

37. Analyzing the Checkpoint results

Standard Checkpoint: By adding standard checkpoints to your tests or components, you can compare the expected values of object properties to the object's current values during a run session. If the results do not match, the checkpoint fails.

38. Table and DB Checkpoints:

By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application.

The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails.

You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box.

Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments.

You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query.

Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.

There are two ways to define a database query:

(a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.
(b) Manually define an SQL statement.
The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint

39. Checking Bitmaps:
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. QuickTest 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.

When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy. For more information on test results of a checkpoint, see Viewing Checkpoint Results.

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 is loaded).

Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

40. Text/Text Area Checkpoint:

In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.

Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.

QuickTest automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed).

To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens

Checking XML:

XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.

XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.

You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:

An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is neededâ€”for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.
An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application's ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.
XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.
XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.

41. Object Repositories types, which & when to use?
Deciding Which Object Repository Mode to Choose
To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes.
In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:
You have only one, or very few, tests that correspond to a given application, interface, or set of objects.
You do not expect to frequently modify test object properties.
You generally create single-action tests.
Conversely, the shared object repository mode is generally the preferred mode when:
You have several tests that test elements of the same application, interface, or set of objects.
You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.
You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.

42. Can we Script any test case with out having Object repository? or Using Object Repository is a must?
Ans: No. U can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.

43. How to execute a WinRunner Script in QTP?
Ans : (a) TSLTest.RunTest TestPath, TestSet [, Parameters ] --> Used in QTP 6.0 used for backward compatibility
Parameters : The test set within Quality Center, in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center, this parameter is ignored.
e.g : TSLTest.RunTest "D:\test1", ""

(b)
TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ]
TSLTest.RunTestEx "C:\WinRunner\Tests\basic_flight", TRUE, FALSE, "MyValue"
CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends.
Parameters : Up to 15 WinRunner function argument

44. How to handle Run-time errors?
(a) On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure.
Using "Err" object msgbox "Error no: " & " " & Err.Number & " " & Err.description & " " & Err.Source & Err.HelpContext

45. How to change the run-time value of a property for an object?
Ans : SetTOProperty changes the property values used to identify an object during the test run.
Only properties that are included in the test object description can be set

46. How to retrieve the property of an object?
Ans : using "GetRoProperty".

47. How to open any application during Scripting?
Ans : SystemUtil , object used to open and close applications and processes during a run session.
(a) A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test
E.g : SystemUtil.Run "Notepad.exe"
SystemUtil.CloseDescendentProcesses (Closes all the processes opened by QTP)
48. Types of properties that Quick Test learns while recording?
Ans : (a) Mandatory (b) Assistive .
In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

49. What is the extension of script and object repository files?
Ans : Object Repository : .tsr , Script : .mts, Excel : Default.xls

50. How to supress warnings from the "Test results page"?
Ans : From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

51. When we try to use test run option "Run from Step", the browser is not launching automatically why?
Ans : This is default behaviour.

52. Does QTP is "Unicode" compatible?
Ans : QTP 6.5 is not but QTP 8.0 is expected to be Unicode compatabile by end of December 2004.

53. How to "Turn Off" QTP results after running a Script?
Ans : Goto "Tools > Options > Run Tab" and Deselect "View results when run session ends". But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

54. How to get "FontSize" of a "WebEdit"?

55. Is there anyway to automatically update the Datasource name in Database Checkpoints object when we migrate tests to a new release?

56. How to verify the Cursor focus of a certain field?
Ans : Use "focus" property of "GetRoProperty" method"

57. Any limitation to XML Checkpoints?
Ans : Mercury has determined that 1.4MB is the maximum size of a XML file that QTP 6.5 can handle

58. How to make arguments optional in a function?

Ans : this is not possible as default VBS doesn't support this. Instead you can pass a blank scring and have a default value if arguments r not required.

59. How to covert a String to an integer?
Ans : CInt()---> a conversion function available.

60. Inserting a Call to Action is not importing all columns in Datatable of globalsheet. Why?
Ans : Inserting a call to action will only Import the columns of the Action called

Quick Test Pro FAQ's

2008-07-17T09:21:00.000-07:00

What is QTP ?
QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications...

QTP is Mercury Interactive Functional Testing Tool.
Mercury QuickTest Professional: provides the industry's best solution for functional test and regression test automation - addressing every major software application and environment. This next-generation automated testing solution deploys the concept of Keyword-driven testing to radically simplify test creation and maintenance. Unique to QuickTest Professional’s Keyword-driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.

What’s the basic concept of QTP?
QTP is based on two concept-
 Recording
 Playback

Which scripting language used by QTP?
QTP using VB scripting.

How many types of recording facility are available in QTP?
QTP provides three types of recording methods-

* Context Recording (Normal)
 Analog Recording
 Low Level Recording

How many types of Parameters are available in QTP?
QTP provides three types of Parameter-
* Method Argument
* Data Driven
* Dynamic

What’s the QTP testing process?
QTP testing process consist of seven steps-
* Preparing to recoding
* Recording
* Enhancing your script
* Debugging
* Run
* Analyze
* Report Defects (more…)

How to Start recording using QTP?
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.

How to insert a check point to a image to check enable property in QTP?

Answer1:
AS you are saying that the all images are as push button than you can check the property enabled or disabled. If you are not able to find that property than go to object repository for that objecct and click on add remove to add the available properties to that object. Let me know if that works. And if you take it as image than you need to check visible or invisible property tht also might help you are there are no enable or disable properties for the image object.

Answer2:
The Image Checkpoint does not have any property to verify the enable/disable property.
One thing you need to check is:
* Find out form the Developer if he is showing different images for activating/deactiving i.e greyed out image. That is the only way a developer can show deactivate/activate if he is using an "image". Else he might be using a button having a headsup with an image.
* If it is a button used to display with the headsup as an image you woudl need to use the object Properties as a checkpoint.

How to Save your test using QTP?
Select File > Save or click the Save button. The Save dialog box opens to the Tests folder.
Create a folder which you want to save to, select it, and click Open.
Type your test name in the File name field.
Confirm that Save Active Screen files is selected.
Click Save. Your test name is displayed in the title bar of the main QuickTest window.

How to Run a Test using QTP?
1 Start QuickTest and open your test.

If QuickTest is not already open, choose Start > Programs > QuickTest Professional > QuickTest Professional.

. If the Welcome window opens, click Open Existing.
. If QuickTest opens without displaying the Welcome window, choose File > Open or click the Open button.
In the Open Test dialog box, locate and select your test, then click Open.

2 Confirm that all images are saved to the test results.
QuickTest allows you to determine when to save images to the test results.

Choose Tools > Options and select the Run tab. In the Save step screen capture to test results option, select Always.

Click OK to close the Options dialog box.

3 Start running your test.

Click Run or choose Test > Run. The Run dialog box opens.
Select New run results folder. Accept the default results folder name.
Click OK to close the Run dialog box.

How to open a new test using QTP?
1. If QuickTest is not currently open, choose Start > Programs > QuickTest Professional > QuickTest Professional. If the Welcome window opens, click Blank Test. Otherwise, choose File > New, or click the New button. A blank test opens. 2. . If QuickTest is already open, check which add-ins are loaded by selecting Help > About QuickTest Professional. If the Web Add-in is not loaded, you must exit and restart QuickTest. When the Add-in Manager opens, select the Web Add-in, and clear all other add-ins. Choose File > New, or click the New button. A blank test opens.

How to do Laod testing for web based Application?
1. Recording a scenerio in QTP of my web based application.
2. Make 100 copies of that scenerio and run the test (scenerio run for 100 times)
3. In that case, do the load of application on server.
4. The basic logic of running the copy 100 times is to create same scenerio as if 100 users were working.

What is the extension of script and object repository files?
Object Repository : .tsr , Script : .mts, Excel : Default.xls

How to supress warnings from the "Test results page"?
From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

When we try to use test run option "Run from Step", the browser is not launching automatically why?
This is default behaviour.

What's Checkpoints for QTP?
A checkpoint verifies that expected information is displayed in your application while the test is running.

QuickTest Professional offers the following types of checkpoints:
Checkpoint Type Description Example of Use
Standard Checkpoint Checks values of an object’s properties. Check that a radio button is selected.
Image Checkpoint Checks the property values of an image. Check that the image source file is correct.
Table Checkpoint Checks information in a table. Check that the value in a table cell is correct.
Page Checkpoint Checks the characteristics of a Web page. Check how long a Web page takes to load or if a Web page contains broken links.
Text / Text Area Checkpoint Checks that a text string is displayed in the appropriate place in a Web page or application window. Check whether the expected text string is displayed in the expected locatio
Bitmap Checkpoint Checks an area of a Web page or application after capturing it as a bitmap Check that a Web page (or any portion of it) is displayed as expected.
Database Checkpoint Checks the contents of databases accessed by an application or Web site Check that the value in a database query is correct.
Accessibility Checkpoint Identifies areas of a Web site to check for Section 508 compliancy. Check if the images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines.
XML Checkpoint Checks the data content of XML documents. Note: XML file checkpoints are used to check a specified XML file; XML application checkpoints are used to check an XML document within a Web page.

How to add a standard checkpoint in your 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.

How to add a page checkpoint to your 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. Note that this dialog box may include different elements, depending on where you click in the Active Screen.
3 Save the test.

How Does Run time data (Parameterization) is handled in QTP?
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.

What is keyword view and Expert view in QTP?
QuickTest’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

How QTP recognizes Objects in AUT?
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.

What are the types of Object Repositorys in QTP?
QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test. The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

If I give some thousand tests to execute in 2 days what do u do?
Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.

Does QTP is "Unicode" compatible?
QTP 6.5 is not but QTP 8.0 is expected to be Unicode compatabile by end of December 2004.

How to "Turn Off" QTP results after running a Script?
Goto "Tools > Options > Run Tab" and Deselect "View results when run session ends". But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

Explain about the Test Fusion Report of QTP ?
Once a tester has run a test, a TestFusion 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.

To which environments does QTP supports ?
QuickTest 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.

What's QuickTest Window?
Before you begin creating tests, you should familiarize yourself with the main QuickTest window.
The QuickTest window contains the following key elements:
. Title bar—Displays the name of the currently open test.
. Menu bar—Displays menus of QuickTest commands.
. File toolbar—Contains buttons to assist you in managing your test.
. Testing toolbar—Contains buttons to assist you in the testing process.
. Debug toolbar—Contains buttons to assist you in debugging tests.
. Test pane—Contains the Keyword View and Expert View tabs.
. Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.
. Data Table—Assists you in parameterizing your test.
. 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 Viewer by choosing View < Debug Viewer.)
. Status bar—Displays the status of the QuickTest application.

How does QTP identifes the object in the application
QTP identifies the object in the application by LogicalName and Class.
For example :
The Edit box is identified by
Logical Name : PSOPTIONS_BSE_TIME20
Class: WebEdit

If an application name is changes frequently i.e while recording it has name “Window1” and then while running its “Windows2” in this case how does QTP handles?
QTP handles those situations using “Regular Expressions..

Table and DB Checkpoints:
By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application. The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails. You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box. Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments. You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query. Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.

There are two ways to define a database query:
(a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.
(b) Manually define an SQL statement.
The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint

Checking Bitmaps:
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. QuickTest 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.
When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy. For more information on test results of a checkpoint, see Viewing Checkpoint Results.
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). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

Text/Text Area Checkpoint :
In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.
Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.
QuickTest automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed). To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens

Checking XML :
XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.
XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.
You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:
An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is needed—for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.
An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application's ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.
XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.
XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.

What are the Features & Benefits of Quick Test Pro(QTP)..?
1. Key word driven testing
2. Suitable for both client server and web based application
3. Vb script as the scriot language
4. Better error handling mechanism
5. Excellent data driven testing features

How to handle the exceptions using recovery secnario manager in Qtp?
You can instruct QTP to recover unexpected events or errors that occured 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

what is the use of Text output value in Qtp?
Output values enable to view the values that the application talkes during run time.When paramaterised, 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.

What information do the columns in the Keyword View show for each step?
As you recorded your test, QuickTest generated steps in the Keyword View representing each operation you performed in the Web browser.
The columns in the Keyword View show different information for each step, as follows:

. Item—Displays the item for the step (test object, utility object, function call, or statement) in a hierarchical icon-based tree.
. Operation—The operation to be performed on the item, for example, Click or Select.
. Value—The argument values for the selected operation, for example, the mouse button to use when clicking the image.
. Assignment—The assignment of a value to or from a variable so you can use the value later in the test.
. Comment—Any textual information you want to add regarding the step, for example, Return to page used in first step of the test.
. Documentation—Auto-documentation of what the step does, in an easy-to-understand sentence, for example, Click the “findFlights” image.

Why use Regular Expressions?
you created a text checkpoint that searched for a specific text string. You can use regular expressions to increase the flexibility and adaptability of your tests.
Regular expressions enable QuickTest to identify objects and text strings with varying values. You can use regular expressions when defining the properties of an object, the methods of an argument, when parameterizing a step, and when creating checkpoints with varying values.

Explain QTP Testing process ?
The QuickTest testing process consists of 6 main phases:

1. 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.

2. Recording a session on your application
As you navigate through your application, QuickTest 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.

2. Enhancing your test
o 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.
o 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.
o Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

3. Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

4. Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.

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

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

What is Parameterizing Tests?
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.

What is test object model in QTP ?
The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.

A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.
A run-time object is the actual object in your Web site or application on which methods are performed during the run session.
When you perform an operation on your application while recording, QuickTest:

? identifies the QuickTest test object class that represents the object on which you performed the operation and creates the appropriate test object
? reads the current value of the object’s properties in your application and stores the list of properties and values with the test object
? chooses a unique name for the object, generally using the value of one of its prominent properties
? records the operation that you performed on the object using the appropriate QuickTest test object method
For example, suppose you click on a Find button with the following HTML source code:

QuickTest identifies the object that you clicked as a WebButton test object. It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton:
It also records that you performed a Click method on the WebButton.
QuickTest displays your step in the Keyword View like this:
QuickTest displays your step in the Expert View like this:
Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").

How to analyzing Test Results using QTP?
When QuickTest finishes running the test, the Test Results window opens.
Initially, the Test Results window contains two panes for displaying the key elements of your test run.
. The left pane displays the results tree, an icon-based view of the steps that were performed while the test was running. The results tree is organized according to the Web pages visited during the test run and can be expanded (+) to view each step. The steps performed during the test run are represented by icons in the tree. You can instruct QuickTest to run a test or action more than once using different sets of data in each run. Each test run is called an iteration, and each iteration is numbered. (The test you ran had only one iteration.)
. The right pane displays the test results details. The iteration summary table indicates which iterations passed and which failed. The status summary table indicates the number of checkpoints or reports that passed, failed, and raised warnings during the test.
1 View the test results for a specific step.
In the results tree, expand (+) Test Recording Summary > Recording Iteration 1 (Row 1) > Action1 Summary > your application > your test name .
The Test Results window now contains three panes, displaying:
. the results tree, with one step highlighted
. the test results details of the highlighted step
. the Active Screen, showing a screen capture of the Web page on which the step was performed.

When you click a page in the results tree, QuickTest displays the corresponding page in the application view. When you click a step (an operation performed on an object) in the results tree, the corresponding object is highlighted in the application view. In this case, the Departing From text box is highlighted.

Explain the check points in QTP?
A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.

• A page checkpoint checks the characteristics of a Application
• A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
• An object checkpoint (Standard) checks the values of an object on a Application.
• An image checkpoint checks the values of an image on a Application.
• A table checkpoint checks information within a table on a Application
• An Accessiblity checkpoint checks the web page for Section 508 compliance.
• An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
• A database checkpoint checks the contents of databases accessed by your web site

In how many ways we can add check points to an application using QTP.
We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).

Explain in brief about the QTP Automation Object Model.
Essentially all configuration and run functionality provided via the QuickTest interface is in some way represented in the QuickTest automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in QuickTest have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the QuickTest automation object model, along with standard programming elements such as loops and conditional statements to design your program.

Discuss QTP Environment.
QuickTest Pro environment using the graphical interface and ActiveScreen 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 one test script.

Explain the concept of how QTP identifies object.
During recording qtp looks at the object and stores it as test object.For each test object QT 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 object. During test run,QT searches for the run time obkects that matches with the test object it learned while recording.

Object Repositories types, Which & when to use?
Deciding Which Object Repository Mode to Choose
To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes.
In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:

You have only one, or very few, tests that correspond to a given application, interface, or set of objects.
You do not expect to frequently modify test object properties.
You generally create single-action tests.
Conversely, the shared object repository mode is generally the preferred mode when:

You have several tests that test elements of the same application, interface, or set of objects.
You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.
You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.

Can we Script any test case with out having Object repository? or Using Object Repository is a must?
No. U can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.

How to execute a WinRunner Script in QTP?
(a) TSLTest.RunTest TestPath, TestSet [, Parameters ] --> Used in QTP 6.0 used for backward compatibility Parameters : The test set within Quality Center, in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center, this parameter is ignored.
e.g : TSLTest.RunTest "D:\test1", ""
(b)TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ] TSLTest.RunTestEx "C:\WinRunner\Tests\basic_flight", TRUE, FALSE, "MyValue" CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends. Parameters : Up to 15 WinRunner function argument

Why divide a test into three action calls?
When you create a new test, it contains a call to one action. By dividing your tests into calls to multiple actions, you can design more modular and efficient tests.

How To clear the AutoComplete?
1 In your Internet Explorer’s menu bar, choose Tools > Internet Options > Content tab.
2 Click AutoComplete in the Personal information area. The AutoComplete Settings dialog box opens.
3 In the Use AutoComplete for area, clear the User names and passwords on forms option.
4 Click OK to save your changes and close the AutoComplete Settings dialog box, then click OK again to close the Internet Options dialog box.

What is Object Spy in QTP?
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 object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
What is the Diff between Image check-point and Bit map Check point?
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. QuickTest 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).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

How many ways we can parameterize data in QTP ?
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, QuickTest 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 QuickTest 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 QuickTest generate a random number and insert it in a number of tickets edit field.

How do u do batch testing in WR & is it possible to do in QTP, if so explain?
Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid".The same is possible with QTP also. If our test cases are automated then by selecting "Run Testset" 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.

How to use the Object spy in QTP 8.0 version?
There are two ways to Spy the objects in QTP
1) Thru file toolbar
---In the File ToolBar click on the last toolbar button (an icon showing a person with hat). 2) Tru Object repository Dialog
---In Objectrepository 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 minimised then Hold the Ctrl button and activate the required window to and release the Ctrl button.

What is the file extension of the code file & object repository file in QTP?
File extension of
-- Per test object rep :- filename.mtr
-- Shared Oject rep :- filename.tsr
Code file extension id script.mts

How to Creating an Output Value using QTP?
1 Start QuickTest and open the Parameter test.
2 Save the test as Output.
3 Confirm that the Active Screen option is enabled.
4 Select the text you want to use as an output value.
5 Set the output value settings.
6 Modify the table checkpoint.
7 Save the test.
What does it mean when a check point is in red color? what do u do?
A red color indicates failure. Here we analyze the the cause for failure whether it is a Script Issue or Envronment Issue or a Application issue.

What do you call the window testdirector-testlab?
"Execution Grid". It is place from where we Run all Manual / Automated Scripts

How do u create new test sets in TD
Login to TD.
Click on "Test Lab" tab.
Select the Desired folder under which we need to Create the Test Set. ( Test Sets can be grouped as per module.) Click on "New Test Set or Ctrl+N" Icon to create a Test Set.

Explain the concept of object repository & how QTP recognises objects?
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 Ordianl identifier such as objects location onthe page or in the source code.

What are the properties you would use for identifying a browser & page when using descriptive programming ?
"name" would be another property apart from "title" that we can use. OR We can also use the property "micClass". ex: Browser("micClass:=browser").page("micClass:=page")....

I want to open a Notepad window without recording a test and I do not want to use SystemUtil.Run command as well How do I do this?
U can still make the notepad open without using the record or System utility script, just by mentioning the path of the notepad "( i.e., where the notepad.exe is stored in the system) in the "Windows Applications Tab" of the "Record and Run Settings window. Try it out. All the Best.
If an application name is changes frequently i.e while recording it has name, in this case how does QTP handles?

IF we use batch testing.the result shown for last action only.in that how can i get result for every action.
You can click on the icon in the tree view to view the result of every action
WinRunner Compared to QuickTest Pro

Environment Coverage Comparison:

Common environments shared by both WinRunner and QuickTest Pro:

Web-Related Environments IE, Netscape, AOL
JDK, Java Foundation Classes, AWT
Symantec Visual Café
ActiveX Controls
ERP/CRM Oracle: Jinitiator, 11i, NCA
Custom Client Server Windows
C++/C
Visual Basic
Operating Systems Windows 98, 2000, NT, ME, XP
Legacy 3270, 5250 Emulators
VT100

WinRunner Only Environments:
Custom Client/Server PowerBuilder
Forte
Delphi
Centura
Stingray
SmallTalk
ERP/CRM Baan
PeopleSoft Windows
Siebel 5, 6 GUI Clients
Oracle GUI Forms

QuickTest Pro Only Environments:
ERP/CRM SAP
Siebel 7.x
PeopleSoft 8.x
.Net WinForms
WebForms
.Net controls
Web Services XML, HTTP
WSDL, SOAP
J2EE, .Net
Multimedia RealAudio/Video
Flash

Feature Comparison:

Common features found in both WinRunner and QuickTest Pro:
Record/Replay ODBC & Excel Connectivity
Code Editor & Debugger Recovery Manager
Shared Object Repository Rapid Object Import
Numerous Checkpoints Analog
Script & Function Libraries

WinRunner Only Environments:
Function Generator Database Integration
Run Wizard TSL
MDI

QuickTest Pro Only Environments:
ActiveScreen TestGuard
Tree View ScriptFusion
Data Table VBScript
Function Generator*
(coming in v7.0) Run Wizard*
(coming in v7.0)
How to Import data from a ".xls" file to Data table during Runtime.
Datatable.Import "...XLS file name..."
DataTable.ImportSheet(FileName, SheetSource, SheetDest)
DataTable.ImportSheet "C:\name.xls" ,1 ,"name"

How to export data present in Datatable to an ".xls" file?
DataTable.Export "....xls file name..."

Syntact for how to call one script from another? and Syntax to call one "Action" in another?
RunAction ActionName, [IterationMode , IterationRange , Parameters]
Here the actions becomes reusable on making this call to any Action.
IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. "1-7"), or enter rngAll to run iterations on all rows.
If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction's RetVal argument.

How to export QTP results to an ".xls" file?
By default it creates an "XML" file and displays the results

How the exception handling can be done using QTP
It can be done Using the Recovery Scenario Manager which provides a wizard that gudies you through the process of defining a recovery scenario. FYI.. The wizard could be accesed in QTP> Tools-> Recovery Scenario Manager .......

How many types of Actions are there in QTP?
There are three kinds of actions:
non-reusable action—an action that can be called only in the test with which it is stored, and can be called only once. reusable action—an action that can be called multiple times by the test with which it is stored (the local test) as well as by other tests.
external action—a reusable action stored with another test. External actions are read-only in the calling test, but you can choose to use a local, editable copy of the Data Table information for the external action.

Analyzing the Checpoint results
Standard Checpoint :By adding standard checkpoints to your tests or components, you can compare the expected values of object properties to the object's current values during a run session. If the results do not match, the checkpoint fails.
How to handle Run-time errors?
On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure.
Using "Err" object msgbox "Error no: " & " " & Err.Number & " " & Err.description & " " & Err.Source & Err.HelpContext

What are the different scripting languages you could use when working with QTP ?
Visual Basic (VB),XML,JavaScript,Java,HTML

How to handle dynamic objects in QTP?
QTP has a unique feature called Smart Object Identification/recognition. QTP generally identifies an object by matching its test object and run time object properties. QTP may fail to recognise the dynamic objects whose properties change during run time. Hence it has an option of enabling Smart Identification, wherein it can identify the objects even if their properties changes during run time. Check this out-
If QuickTest is unable to find any object that matches the recorded object description, or if it finds more than one object that fits the description, then QuickTest ignores the recorded description, and uses the Smart Identification mechanism to try to identify the object. While the Smart Identification mechanism is more complex, it is more flexible, and thus, if configured logically, a Smart Identification definition can probably help QuickTest identify an object, if it is present, even when the recorded description fails.

The Smart Identification mechanism uses two types of properties:
Base filter properties—The most fundamental properties of a particular test object class; those whose values cannot be changed without changing the essence of the original object. For example, if a Web link's tag was changed from to any other value, you could no longer call it the same object. Optional filter properties—Other properties that can help identify objects of a particular class as they are unlikely to change on a regular basis, but which can be ignored if they are no longer applicable.

Explain the keyword createobject with an example.
Creates and returns a reference to an Automation object
syntax: CreateObject(servername.typename [, location])
Arguments
servername:Required. The name of the application providing the object.
typename : Required. The type or class of the object to create.
location : Optional. The name of the network server where the object is to be created.

What is a Run-Time Data Table? Where can I find and view this table?
-In QTP, there is data table used , which is used at runtime.
-In QTP, select the option View->Data tabke.
-This is basically an excel file, which is stored in the folder of the test created, its name is Default.xls by default.

How to do the scripting. Is there any inbuilt functions in QTP as in QTP-S. Whatz the difference between them? how to handle script issues?
Yes, there's an in-built functionality called "Step Generator" in Insert->Step->Step Generator -F7, which will generate the scripts as u enter the appropriate steps.

What is the difference between check point and output value.
An outPut value is a value captured during the test run and entered in the run-time but to a specified location. EX:-Location in Data Table[Global sheet / local sheet]
Types of properties that Quick Test learns while recording?
(a) Mandatory (b) Assistive . In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

Differences between QTP & Winrunner?
(a) QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
(b) QTP supports ".NET" application Automation not available in Winrunner
(c) QTP has "Active Screen" support which captures the application, not available in WR.
(d) QTP has "Data Table" to store script values , variables which WR does not have.
(e) Using a “point and click” capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script – without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

Few basic questions on commonly used Excel VBA functions.
common functions are:
Coloring the cell
Auto fit cell
setting navigation from link in one cell to other saving

How does Parameterization and Data-Driving relate to each other in QTP?
To datadrive we have to parameterize.i.e. we have to make the constant value as parameter, so that in each iteraration(cycle) it takes a value that is supplied in run-time datatable. Through parameterization only we can drive a transaction(action) with different sets of data. You know running the script with the same set of data several times is not suggestable, & it's also of no use.

What is the difference between Call to Action and Copy Action.?
Call to Action : The changes made in Call to Action , will be reflected in the orginal action( from where the script is called).But where as in Copy Action , the changes made in the script ,will not effect the original script(Action)

How to verify the Cursor focus of a certain field?
Use "focus" property of "GetRoProperty" method"

Any limitation to XML Checkpoints?
Mercury has determined that 1.4MB is the maximum size of a XML file that QTP 6.5 can handle

How to make arguments optional in a function?
this is not possible as default VBS doesn't support this. Instead you can pass a blank scring and have a default value if arguments r not required.
How to add a text checkpoint to your test to check whether 'welcome' is displayed in your welcome page.
1 Locate the page where you want to add a text checkpoint.

2 Create a text checkpoint.
In the Active Screen, under your page highlight the text welcome. Right-click the highlighted text and choose Insert Text Checkpoint. The Text Checkpoint Properties dialog box opens.
When Checked Text appears in the list box, the Constant field displays the text string you highlighted. This is the text QuickTest looks for when running the test.
Click OK to accept the default settings in this dialog box.
QuickTest adds the text checkpoint to your test. It is displayed in the Keyword View as a checkpoint operation on your welcome page

3 Save the test.

How to Running and Analyzing a Test with Checkpoints?
1 Expand the test and review your test.
Choose View > Expand All or use the * shortcut key on your number keypad.

2 Start running your test.
Click Run or choose Test > Run. The Run dialog box opens. Ensure that New run results folder is selected. Accept the default results folder name. Click OK. When the test run is completed, the Test Results window opens.

3 View the test results.
When QuickTest finishes running the test, the Test Results window opens. The test result should be Passed, indicating that all checkpoints passed. If one or more checkpoints had failed, the test result would be Failed.

4 View the results of the page checkpoint.
In the Details pane, you can review the details of the page checkpoint, which lists the items checked.

5 View the results of the table checkpoint.
In the Details pane, you can review the details of the table checkpoint. You can also review the values of the table cells (cell values that were checked are displayed in black; cell values that were not checked are displayed in gray).

6 View the results of the standard checkpoint.
In the Details pane, you can review the details of the standard checkpoint, which lists the properties that were checked and their values. The checkpoint passed because the actual values of the checked properties match the expected values.

7 View the results of the text checkpoint.
In the Details pane, you can review the details of the text checkpoint. The checkpoint passed because the actual text matches the expected text.

8 Close the Test Results window. Choose File > Exit.

How to Defining a Data Table Parameter for QTP?
1 Start QuickTest and open the Checkpoint test.
2 Save the test as Parameter.
3 Confirm that the Active Screen option is enabled.
4 Confirm that the Data Table option is enabled.
5 Select the text to parameterize.
6 Set the parameterization properties.

How to add a runtime parameter to a datasheet?
DataTable.LocalSheet
The following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it.
MyParam=DataTable.LocalSheet.AddParameter("Time", "5:45")
How to change the run-time value of a property for an object?
SetTOProperty changes the property values used to identify an object during the test run. Only properties that are included in the test object description can be set

How to retrieve the property of an object?
using "GetRoProperty".

How to open any application during Scripting?
SystemUtil , object used to open and close applications and processes during a run session.
(a) A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test
E.g : SystemUtil.Run "Notepad.exe" SystemUtil.CloseDescendentProcesses ( Closes all the processes opened by QTP )

How to covert a String to an integer?
CInt()---> a conversion function available.

Inserting a Call to Action is not Importing all columns in Datatable of globalsheet. Why?
Inserting a call to action will only Import the columns of the Action called

Differentiate the two Object Repository Types of QTP.
Object repository is used to store all the objects in the application being tested.2 types of oject repositoy per action and shared. In shared repository only one centralised repository for all the tests. where as in per action.for each test a separate per action repostory is created.

What the differences are and best practical application of each.
Per Action: For Each Action, one Object Repository is created. Shared : One Object Repository is used by entire application

Explain what the difference between Shared Repository and Per_Action Repository
Shared Repository: Entire application uses one Object Repository , that similar to Global GUI Map file in WinRunner Per Action: For each Action ,one Object Repository is created, like GUI map file per test in WinRunner

Have you ever written a compiled module? If yes tell me about some of the functions that you wrote.
I Used the functions for Capturing the dynamic data during runtime. Function used for Capturing Desktop, browser and pages.

What projects have you used WinRunner on? Tell me about some of the challenges that arose and how you handled them.
pbs :WR fails to identify the object in gui. If there is a non std window obk wr cannot recognize it ,we use GUI SPY for that to handle such situation.

Can you do more than just capture and playback?
I have done Dynamically capturing the objects during runtime in which no recording, no playback and no use of repository is done AT ALL.
-It was done by the windows scripting using the DOM(Document Object Model) of the windows.
Summary: QuickTest Pro
Summary:
QuickTest Professional provides an interactive, visual environment for test development.
Here is the description from the Mercury Interactive “How it Works” section of the QuickTest Pro web page:
Mercury QuickTest Professional™ allows even novice testers to be productive in minutes. You can create a test script by simply pressing a Record button and using an application to perform a typical business process. Each step in the business process is automated documented with a plain-English sentence and screen shot. Users can easily modify, remove, or rearrange test steps in the Keyword View.

QuickTest Professional can automatically introduce checkpoints to verify application properties and functionality, for example to validate output or check link validity. For each step in the Keyword View, there is an ActiveScreen showing exactly how the application under test looked at that step. You can also add several types of checkpoints for any object to verify that components behave as expected, simply by clicking on that object in the ActiveScreen.

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.

Advanced testers can view and edit their test scripts in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

Once a tester has run a script, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test script 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 Mercury Quality Management, you can share reports across an entire QA and development team.

QuickTest Professional also facilitates the update process. As an application under test changes, such as when a “Login” button is renamed “Sign In,” you can make one update to the Shared Object Repository, and the update will propagate to all scripts that reference this object. You can publish test scripts to Mercury Quality Management, enabling other QA team members to reuse your test scripts, eliminating duplicative work.

QuickTest Professional supports functional testing of all popular environments, including Windows, Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft, terminal emulators, and Web services.

- QuickTest Pro “How it Works” webpage from Mercury:
http://www.mercury.com/us/products/quality-center/functional-testing/quicktest-professional/works.html

We like QuickTest Pro and now prefer implementing it over WinRunner. When you get into advance testing scenarios, QuickTest Pro has more options and they are easier to implement compared to WinRunner in our opinion.

Do to the similarities in concept and features, an experienced WinRunner user can easily convert to QuickTest Pro and quickly become an efficient Test Automation Engineer!

We recommend that existing customers begin all new development with QuickTest Pro and use the built-in feature of calling WinRunner scripts from QuickTest Pro for all existing WinRunner scripts that they already have. As older scripts require updates and time permits, we recommend replacing them with QuickTest Pro scripts. Eventually you will be able to convert your test script library with all QuickTest Pro scripts.
Pros:
* Will be getting the initial focus on development of all new features and supported technologies.
* Ease of use.
* Simple interface.
* Presents the test case as a business workflow to the tester (simpler to understand).
* Numerous features.
* Uses a real programming language (Microsoft’s VBScript) with numerous resources available.
* QuickTest Pro is significantly easier for a non-technical person to adapt to and create working test cases, compared to WinRunner.
* Data table integration better and easier to use than WinRunner.
* Test Run Iterations/Data driving a test is easier and better implement with QuickTest.
* Parameterization easier than WinRunner.
* Can enhance existing QuickTest scripts without the “Application Under Test” being available; by using the ActiveScreen.
* Can create and implement the Microsoft Object Model (Outlook objects, ADO objects, FileSystem objects, supports DOM, WSH, etc.).
* Better object identification mechanism.
* Numerous existing functions available for implementation – both from within QuickTest Pro and VBScript.
* QTP supports .NET development environment (currently WinRunner 7.5 does not).
* XML support (currently WinRunner 7.5 does not).
* The Test Report is more robust in QuickTest compared to WinRunner.
* Integrates with TestDirector and WinRunner (can kick off WinRunner scripts from QuickTest).
Cons:
* Currently there are fewer resources (consultants and expertise) available due to QTP being a newer product on the market and because there is a greater Demand than Supply, thus fewer employee/consulting resources.
* Must know VBScript in order to program at all.
* Must be able to program in VBScript in order to implement the real advance testing tasks and to handle very dynamic situations.
* Need training to implement properly.
* The Object Repository (OR) and “testing environment” (paths, folders, function libraries, OR) can be difficult to understand and implement initially.
QuickTest Pro Questions Only
1. how many maximum actions can be performed in a single test
2. How to create the dynamic object repository in QTP?
3. What is difference between global sheet anh action sheet?
4. How to pass parameters from one action to another action.
5. How to perform Cross platform testing and Cross browser testing using QTP?Can u explain giving some exampl
6. how to connect the database through QTP
7. How to open multiple instances of an application from QTP? 2. How to recognize each instance and setting
8. This is the chain of question#: 15434What conditions we go for Reusable Scripts and how we create and
9. Can we call QTP test from another test using scripting.Suppose there are 4 tests and i want to call these
10. Is it possible to test a web application(java) with winrunner?otherwise is it possible to check with
11. How can we insert Text check point and Bit map check point ? if provide example script, it is greatefu
12. Can we mask a Code In .vbs file so that it is not viewable to others?
13. Is there any function to double click a particular row in a webtable?
14. what is the use of command tab in Debug viewer ?can we execute any user defined queries
15. What is Analog recording,What is the difference between analog recording and low level recording
16. what is database check point.
17. What is the use of function and sub function in QTP?
18. What is the new Version of QTP which is recently released in the Market?
19. How to call a funtion present in dll file in QTP Script.
20. I have n iterations of test run in QTP. I want to see the results of not only the latest (‘n’th) iteration
21. How to call from one action to another action in QTP?
22. What is the Difference Between Bit map Check point & Image Check pointPlease explain in detailText &
23. How can we do block commenting in QTP?
24. How to get the column count and column name from resultset in database connction program?
25. 1. How to write QTP scripts?2. Any related website resource to learn QTP?3. What steps the to be follwed
26. How to check an XML schema (XML Schema Validation--from XML file)? Ttell me about .XSD file format.
27. How to schedule tests in QTP?
28. Is Addins enough to work in Flex based applications? or do we have to get a licence for multimedia for
29. how to identify a 'web element' class object while recording and running in 'Event' mode of settings.
30. What are the new features available in QTP 8.2 compared with earlier versions?
31. Hi forum. Could any body tell me what is AMDOCS, and what are its models ? Best regrds.
32. What is difference between window(" ") and dialog(" ") in QTP while creating script?
33. How do you retrieve the Class name of a Test Object programmatically from within a script?
34. What is the best way to test UNIX (QTP, Winrunner or Xrunner)? If QTP supports let me know the brief
35. What is the Recovery Scenerio can apllied for any telephone line connection(Ex:BSNl,Airtel etc
36. what are advantages and disadvantages between internet explorer and netscape navigator (or) Internet
37. Anybody with an experience of testing Mainframe applications. I usually check the ActiveX and VB add-ins
38. Difference Between text and Textarea checkpoints in QTP
39. How to Handle dynamic WebList in QTP...Values in Weblist are different
40. What is the Hotkey that can be used for Hitting spacebar?
41. We are trying to avoid that anybody see our script after we wrote it. Did anybody know how to do this?
42. how can i insert database checkpoint in qtp-6.5
43. What are different execution modes available in QTP & explain them.
44. How can we recognize objects in Flex application using QTP? When I record scripts, it takes all objects
45. For the AS/400 application that takes data only thru the keyboard input and not even single mouse click
46. How to write QTP test results to an Excel application
47. How to write recovery scenario for below questions and what are the steps we will follow?if i click
48. If winrunner and QTP both are functional testing tools from the same company.why a separate tool QTP
49. How do we test Links using Quick Test Professional and confirm that the page we are requesting is seen
50. How do you test DLL files using QTP?
51. After importing external .xls datasheet in to Datatable of QTP, How to set NO of iterations run for
52. How to test Dynamic web pages using QTP
53. How to record Flex (1.0) objects using QTP?Post the code which works for this.
54. Advantage of using Mercury Quality Center over Test Director
55. How do we connect to Oracle database from QTP ?
56. Can any one pls tell me about how to configure the environment variables in qtp and how to use the variables
57. What is the process for creating an automated test script using QTP assuming you have reviewed the manual
58. How to use a data driver in QTP?
59. What is the method used to focus on particuler field.I need the script.I will give example.I flights
60. 1)what is the advantage and disadvantage of using Virtual Object wizard?2) How efficiently we can use
61. Without recording objects in Object Repository are we able to run scripts?
62. Can we call a QTP script from a main script without making it reusable?
63. wat is xml schema validation and how to perform schema validation for a file.wat is *.XSD extention
64. Can any body expalin me the differences between a reusable and a external action with example?
65. I need information on using FSO(file system object) also its significance
66. How to Run a script recorded in English flavor of my application and re-run the same script on different
67. How to write QTP test results to an Excel application, Please provide the exact code if possible ASAPThanks
68. What are the limitations for XML Checkpoints in QTP 8.0?
69. how good is QTP for testing siebel applications?whether QTP recognizes siebel objects or something else
70. How do I use text checkpoint in QTP as everytime I use this checkpoint in the excel sheet and highlight
71. How is automation used in QTP for regreession testing. Please give me a sample script.
72. Anybody explain me, the concept of checkpoint declaration in the QTP mainly for the Objects, Pages, Text
73. How can we validate the PDF file recognization and its content with the help of Mercury product QTP(Quick
74. What is Expert view in QTP?Can you explain with example?
75. What is the best way to do regression testing using QTP.
76. what is the use functions in QTP. public, private
77. How can we return values from userdefined function? anybody provide code with small example its great
78. how to retrive/update database by writing code in expert viewIn my case database is Accessmy dsn name="try"database
79. How can I import and/or merge an existing repository into my current test?
81. Hi,I was set the repository as per test mode and recorded my script. Now I wana to change the repository
82. What are Limitation of QTP?
83. what is difference between stub and driver?
84. What is meant by Source Control?
85. What is descriptive programming?
86. how to automate editing an XML file .because when i record the editing on an XML file and run it,some
87. What are the disadvantages or drawbacks in QTP?
88. 1. Each test that you run is displayed into the screen ... I'm looking for a way to run a test in background
89. I have faced one question in interviewhe has given one screen with one bitmap and one edit box.The original
90. What qt plus ? How we merge the files in qtp?What is feasibility study in automation?
91. when a script is recorded in quick test for connecting 10 rows in the database, can we change script
92. How do you test siebel application using qtp?
93. How to get Traceability matrix from TD?
94. How to import a test case present in ".xls" file to TD under a Test set?
95. How to attach a file to TD?
96. What do you to script when objects are removed from application?
97. How do you data drive an external spreadsheet?
98. Give me an example where you have used a COM interface in your QTP project?
99. How long have you used the product?
100. How to get "FontSize" of a "WebEdit"?
101. Is there anyway to automatically update the Datasource name in Database Checkpoints object when we migrate tests to a new release?
102. How to create a Runtime property for an object?

SILK TEST

2008-07-12T21:56:00.002-07:00

SilkTest is
• A powerful tool for running automated test cases on the front end
• A tool for testing Web based applications across different browsers
• Very very stupid – you have to tell it everything in its own language (4test)
• Inflexible when it comes to interpreting your commands
_ It cannot guess at what you mean
_ It requires a certain syntax with certain words
• This can be quite maddening
Different Versions in Silk Test.
1. Silk Test 5.0
2. Silk Test 5.2
3. Silk Test 5.6
4. Silk Test 6.0
5. Silk Test 6.5
6. Silk Test 7.1
Latest Version of the Silk Test is 7.5
Note: The Following Questions are based on the latest version of the Silk Test
Q1. How do I add steps to DefaultBaseState?
The easiest method is to add a BaseState () method to the main window of the application. That's
the one that wMainWindow is set to. If you define this method, it will be executed at the end of
DefaultBaseState (). Suggestion: By using GetTestCaseState (), you can make your method
behave differently depending on whether the testcase is starting or stopping. This function will tell
you whether the testcase is starting or stopping.
Q2. Where can I find all the methods for a class?
Use the Library Browser. Its invoked by choosing Help-->Library Browser from the SilkTest menu.
Select the class tab, then select the class you want to view. The methods for the class appear in
the right panel. You can click on a method and view its syntax. If you check the box marked Show
Inherited, all the methods from the ancestor classes will be shown. Its major disadvantage is that
you can't copy from it.
Q3. Why don't methods defined in a derived class inherit ?
177
When you create a class using winclass MoveableWin : MoveableWin, you're actually deriving a
new class which has the same name as the original class. All objects automatically become
instances of the new derived class. However, other derived classes, such as DialogBox in this
case, have already been inherited from the original MoveableWin. This happened at startup and
can't be changed. Therefore, any methods you added to the inherited MoveableWin class will not
be available for use by DialogBox objects
Q4. How can I change test frames in the middle of a testplan?
First you need to understand optionsets. This feature lets you save your configuration in a file.
The configuration includes your Agent Options, Runtime Options and Class Mappings. The
feature is very useful when you try to open your test frame on a new machine. The optionset
brings all the settings from one machine to another, including the test frame. This is also very
useful for a team.
Q5. Can I pass global variables from SilkOrganizer to SilkTest ?
Yes, you can just reference them directly. For example, if you have a list of string defined
in the test frame, you can pass the variable from SilkOrganizer as testdata or directly in the
testcase statement.
Q6. Is the Extension Kit difficult to use ?
No, if you have the cooperation of the developer (s). If they understand the value of adding
functionality for you and if you're perfectly clear about what you need, you will have very quick
success at implementing the EK. This assumes that the technology for them to retrieve the
information you want exists within their application. Sometimes with 3rd party controls, there is no
exposed API which provides what you need. Unfortunately, sometimes you will need to verify
some custom objects manually (visually).
Q7. Can I call Silk Scripts from an external shell program. ?
Yes. One way is to just call Silk and pass the name of the script using the command line
arguments. The complete list of arguments is shown below.
Command Line Options
Syntax:
optionset: filename
-m
Machine Name
-r
178
Script / Testplan / or Suite Name
-q
Quit SilkTest after the script or plan completes execution.
-query
Testplan query to run
-p
Post error count to calling program
-resexport
Output results files to rex files
partner -m LabMachine13 -q -query FunctionalTests -r InsertNewData.pln
Q8. What's the difference between SilkTest and QA Partner ?
Originally there was only one product, QA Partner. In 1996, Silk (later renamed SilkTest), was
introduced as the Web Testing tool. It was actually the same executable as QA Partner, but with
browser capabilities turned on. This turned out to be confusing for most customers. If you bought
Silk, you could just turn off the browser feature and then you'd have QA Partner. However, if you
bought QA Partner, you wouldn't have the ability to test browsers. Starting with SilkTest 5.0, there
is only one product again.
Q9. What is Immediate If?
Immediate If is a 4-test operator which is little known. It allows you to do an if-then-else
on a single line. The syntax is as follows:
boolean ? ReturnValueIfTrue : ReturnValueIfFalse
BOOLEAN bFirstTime = FALSE
STRING sGreeting = bFirstTime ? "Welcome" : "Welcome back"
Q10. When do you need to use the "this" keyword and when don't you?
The "this" keyword is used in window class methods to refer to the instance variable which is
calling the method at runtime. The "this" keyword is only required when you want to access a
data member which is uniquely defined in the instance. Otherwise its use is optional.
Example:
winclass DialogBox : DialogBox
Close ()
this.wCloseButton.Click ()
NewMethod ()
if (Exists ())
179
// Perform some steps
window DialogBox Test
tag "Test"
parent MyApplication
window wCloseButton = Exit
PushButton Exit
tag "Exit"
main ()
Test.Close ()
Notes:
In the close method above, the "this" keyword is required because the method needs to
reference a data member which is declared in the instance "Test". In the NewMethod
above, this.Exists () is not required, because it is referencing a method which is defined at
the class level.
Q11. Should I create a function or a method?
If the action you are automating is:
closely related to a specific window, create a method of that specific window. closely related to a
class of objects, create a method of that window class. more of a utility, not related to a window or
class of windows, create a function.
Q12. What does the recording statement do?
The recording statement set the following Agent Verification options to FALSE
o OPT_REQUIRE_ACTIVE
o OPT_VERIFY_ACTIVE
o OPT_VERIFY_CLOSED
o OPT_VERIFY_EXPOSED
This can be useful if you specifically want to turn these verifications off for a specific
block of code, but usually it is better to remove the recording statement after you record
the statements you need (run with these options set to TRUE)
Q13. When and why is the Sleep () statement needed?
Sometimes Silk can't tell when an application is busy. When this happens, Silk tries to
execute the next step which gets thrown away by the application or causes an error which
is usually very difficult to reproduce either manually or under debug mode. When this
happens, a well-placed Sleep (2) or Sleep (5) can often solve this annoying problem. A
180
few extra sleep statements to make sure that the application is ready to move forward
may be worth the small difference in the time it takes to execute your scripts.
14. What is WinClass?
Declares a window class for an application-specific window or control.
Note Window class declarations must appear outside of any function.
15. Features in silk 7.5
The list of New features in 7.5 are
1) Support for Infragistics Grid and Toolbar controls
2) Project packaging for relocating and emailing
3) Project Explorer enhancements
4) Java Custom Windows record and playback enhancements
5) Beta support for .NET Framework Version 2
6) Updated technology support
JDK 1.5
AOL 9 Security Edition
Sybase PowerBuilder 10
Silent Installation
Support for Microsoft's Source Code Control Integration
16. What is Frame File
The test frame file
The test frame file includes the following:
· A constant named wMainWindow
· A window of class BrowserChild
A constant named wMainWindow
This constant points to the home page of your application, that is, the page that was loaded when
you created the test frame. The recovery system uses wMainWindow to restore the browser to
that page when a test fails. Just as a non-Web application typically has a state where you want
the tests to start (the base state), Web applications also have a base state. Typically, it is the first
page in the application. See Web applications and the recovery system for more information.
A window of class BrowserChild The window has the same identifier as the value of
wMainWindow. It is this window that, by default, SilkTest loads in order to restore the base state.
The window declaration contains:
181
· The constant sLocation, which is the URL for the page. The recovery system uses
this constant to load the page when necessary.
· Two commented constants, sUserName and sPassword which specify the user name and
password to access the application. See Specifying username and password.
· Two commented constants, BrowserSize and bDefaultFont, which specify the size of the
browser window and the default font to use for displaying text. See Specifying browser size and
fonts.
· All the objects in the page, such as HtmlHeadings, HtmlText, HtmlLinks, HtmlText,
HtmlPushButtons, and so on
17. How to run the script in Remote Machine
Running tests on one remote target
There are three ways in SilkTest to specify that you want a script, suite, or testplan to run
on a remote target instead of the host:
· Enter the target Agent’s name in the host’s Runtime Options dialog. You also need to select a
network protocol in the dialog. If you have been testing a script by running SilkTest and the Agent
on the same system, you can then test the script on a remote system without editing your script
by using this method.
· Specify the target Agent’s name by enclosing it within brackets before the script
or suite name [Ohio]myscript.t · You can select "(none)" in the host’s Runtime Options dialog and
then specify the target Agent’s name in a call to the Connect function in your script. For example,
to connect to a machine named Ontario:
testcase MyTestcase ()
Connect ("Ontario")
// Call first testcase
DoTest1 ()
// Call second testcase
DoTest2 ()
Disconnect ("Ontario")
When you are only driving one remote target, there is no need to specify the current machine; all
testcase code will automatically be directed to the only connected machine. When you use the
multi-application support functions, you will not have to make explicit calls to Connect; the support
functions will issue these calls for you.
18. What is Results File
182
A results file provides information about the execution of the testcase, script, suite, or testplan. By
default, the results file has the same name as the executed script, suite, or testplan, but with a
.res extension (for example, find.res). Whenever you run tests, SilkTest generates a results file,
which indicates how many tests passed and how many failed, describes why tests failed, and
provides summary information. You can invoke comparison tools from within the results file that
pinpoint exactly how the runtime results differ from your known baselines. Testplan results files
offer additional features, such as the ability to generate a Pass/Fail report or compare different
runs of the testplan. When SilkTest displays a results file, on the menu bar it includes the Results
menu, which allows you to manipulate the results file and locate errors. The Results menu
appears only when the active window displays a results file.
A .res file can be opened by multiple users, as long as no test is in process. This means you
cannot have 2 users run tests at the same time and write to the same results file. You can run a
test on the machine while the file is open on the other machine. However, you must not add
comments to the file on the other machine, or you will corrupt the .res file and will not be able to
report the results of the test. If you add comments to the file on both machines, the comments will
be saved only for the file that is closed (and therefore saved) first. By default, the results file
displays an overall summary at the top of the file, including the name of the script, suite, or
testplan; the machine the tests were run on; the number of tests run; the number of errors and
warnings; actual errors; and timing information. To hide the overall summary, click on the
summary and select Results/Hide Summary. For a script or suite results file, the individual test
summaries contain timing information and errors or warnings. For a testplan results file, the
individual test summaries contain the same information as in the overall summary plus the name
of the testcase and script file.
While SilkTest displays the most current version of the script, suite, or testplan, by default
SilkTest saves the last five sets of results for each script, suite, or testplan executed. (To change
the default number, use the Runtime Options dialog.) As results files grow after repeated testing,
a lot of unused space can accumulate in the files. You can reduce a results file’s size with the
Compact menu option. The format for the rest of a testplan results file follows the hierarchy of test
descriptions that were present in the testplan. Test statements in the testplan that are preceded
by a pound sign (#) as well as comments (using the comment statement) are also printed in the
results file, in context with the test descriptions.
To change the default name and directory of the results file, edit the Runtime Options dialog.
19. How to Generate a Testplan Completion report
183
To measure your QA department’s progress in implementing a large testplan, you can generate a
Completion report. The Completion report considers a test complete if the test description is
linked to a testcase, with two exceptions:
1 If the testcase statement invokes a data-driven testcase and a symbol being passed
to the data-driven testcase is assigned the value ? (undefined), the test is considered
incomplete.
2 If the testcase is manual and marked as Incomplete in the Update Manual Tests
dialog, the test is considered incomplete. (A manual testcase is indicated with the
testcase:manual syntax; for more information, see indicating manual tests in a testplan .
To generate a testplan completion report:
1 Open the testplan you want to report on.
2 Select Testplan/Completion Report to display the Testplan Completion Report
dialog.
3 In the Report Scope group box, indicate whether the report is for the entire plan or
only for those tests that are marked.
4 To subtotal the report by a given attribute, select an attribute from the Subtotal by
Attribute field.
5 Click Generate. The testplan editor generates the report and displays it in the
lower half of the dialog. If the testplan is structured as a master plan with associated
subplans, the testplan editor opens any closed subplans prior to generating the report.
You can:
· Print the report.
· Export the report to a comma-delimited ASCII file. You can then bring the report
into a spreadsheet application that accepts comma- delimited data.
· Chart (graph) the report, just as you can chart a Pass/Fail reportFor more information, see
Producing a Pass/Fail chart (everything in that section also applies to charting Completion
reports, except for the description of adding results from another execution of the testplan, which
applies only to Pass/Fail reports).
20. What is a TestCase
A test case has three stages
Each testcase that you record should have the following stages:
184
1 Stage 1: The testcase drives the application from the initial state to the state you
want to test.
2 Stage 2: The testcase verifies that the actual state matches the expected (correct)
state. (Your QA department might use the term baseline to refer to this expected state.)
This stage is the heart of the testcase.
3 Stage 3: The testcase cleans up the application, in preparation for the next
testcase, by undoing the steps performed in stage 1.
Each test case is independent
Each testcase you record should perform its own setup in stage 1, and should undo this setup in
stage 3, so that the testcase can be executed independently of every other testcase. In other
words, the testcase should not rely upon the successful or unsuccessful completion of another
testcase, and the order in which it is executed should have no bearing on its outcome.
If a testcase relies on a prior testcase to perform some setup actions, and an error causes
the setup to fail or, worse yet, the application to crash, all subsequent testcases will fail
because they cannot achieve the state where the test is designed to begin.
A testcase has a single purpose
Each testcase you record should verify a single aspect of the application in stage 2. When
a testcase designed in this manner passes or fails, it’ s easy to determine specifically what aspect
of the target application is either working or not working.
If a testcase contains more than one objective, many outcomes are possible. Therefore, an
exception may not point specifically to a single failure in the software under test but rather to
several related function points. This makes debugging more difficult and time consuming and
leads to confusion in interpreting and quantifying results. The net result is an overall lack of
confidence in any statistics that might be generated. Note But there are techniques you can use
to do more than one verification in a testcase. See Performing more than one verification in a
testcase.
A testcase starts from a base state
In order for a testcase to be able to function properly, the application must be in a stable
state when the testcase begins to execute. This stable state is called the base state. The
recovery system is responsible for maintaining the base state in the event the application
185
fails or crashes, either during a testcase’s execution or between testcases.
DefaultBaseState
To restore the application to the base state, the recovery system contains a routine called
DefaultBaseState that makes sure that
· The application is running and is not minimized
· All other windows (for example, dialogs) are closed
· The main window of the application is active
If these conditions are not sufficient for your application, you can customize the recovery
system.
Defining test requirements
When defining test requirements, the goal is to rigorously test each application feature.
To do so, you need to decide which set of inputs to a feature will provide the most
meaningful test results.
21. How to Enter the TestData
Entering the testdata statement manually
1 Open up a new line after the test description and indent the line one level.
2 Enter the testdata statement as follows, if the testcase expects:
· one or more variables, use this syntax: testdata: data [,data], where data is any valid 4Test
expression
· a record, use the same syntax as above, but open and close the list of record fields with curly
braces: testdata: {data [,data]}, where data is any valid 4Test expression
Note Be sure to follow the testdata keyword with a colon. If you enter the keyword correctly, the
statement appears in dark red, the default color. Otherwise, the statement appears in either blue
or black, indicating the compiler is interpreting the line as a description.
Specifying unique and shared data
If a data value is unique to a single test description: you should place it in the plan at the same
level as the test description, using the testdata statement. You can add the testdata statement
using the Testplan Detail dialog or type the testdata statement directly into the testplan.
186
If data is common to several tests: you can factor out the data that is common to a group of tests
and define it at a level in the testplan where it can be shared by the group. To do this, you define
symbols and assign them values. Using symbols results in less redundant data, and therefore,
less maintenance.
Using the Testplan Detail dialog to enter the testdata statement
1 Place the insertion point at the end of the test description. If a testdata statement is not
associated with a test description, the compiler generates an error.
2 Select Testplan/Detail. To provide context, the multi-line list box at the top of the Testplan Detail
dialog displays the line in the testplan that the cursor was on when the dialog was invoked,
indicated by the black arrow icon. If the testcase and script associated with the current test
description are inherited from a higher level in the testplan, they are shown in blue; otherwise,
they are shown in black.
3 Enter the data in the Test Data field, separating each data element with a comma.
Remember, if the testcase expects a record, you need to enclose the list of data with the list
constructor operator (the curly braces); otherwise, SilkTest interprets the data as individual
variables, not a record, and will generate a data type mismatch compiler error. 4 Click OK.
SilkTest closes the Testplan Detail dialog closes and enters the testdata statement and data
values in the plan.
22. What is a Mater Plan.
Dividing a testplan into a master plan and subplans
If several engineers in your QA department will be working on a testplan, it makes sense to break
up the plan into a master plan and subplans. This approach allows multi-user access, while at the
same time maintaining a single point of control for the entire project. The master plan contains
only the top few levels of group descriptions, and the subplans contain the remaining levels of
group descriptions and test descriptions. Statements, attributes, symbols, and test data defined in
the master plan are accessible within each of the subplans. Subplans are specified with an
include statement. To expand the subplan files so that they are visible within the master plan,
double-click in the left margin next to the include statement. Once a subplan is expanded inline,
the subplan statement changes from red (the default color for statements) to magenta, indicating
that the line is now read-only and that the subplan is expanded inline. At the end of the expanded
subplan is the marker, which indicates the end of the subplan file.
23. How to create a Sub Plan
187
Creating a subplan
You create a subplan in the same way you create any testplan: by opening a new testplan file
and entering the group descriptions, test descriptions, and the testplan editor statements that
comprise the subplan, either manually or using the Testplan Detail dialog.
24. What is a Lock
About locks
When first opened, a master plan and its related subplans are read-only. This allows many users
to open, read, run, and generate reports on the plan. When you need to actually edit the master
plan or a subplan, you must first acquire a lock, which prevents others from making changes that
conflict with your changes.
25. What is the importance of options menu
Options menu
The Options menu contains the following commands:
General opens the General Options dialog, which you use to set such aspect s of general system
behavior as the editor and your workspace.
Editor Font opens the Editor Font dialog, which allows you to select a screen font in the family,
size, and style of your choice.
Editor Colors opens the Editor Colors dialog, which you use to set the screen colors for various
elements of 4Test code, results information, and the testplan (if available).
Runtime opens the Runtime Options dialog, which allows you to specify settings that SilkTest
uses when it runs a script.
Agent opens the Agent Options dialog, which allows you to set global options for how the SilkTest
Agent software interacts with the application under test.
Extensions opens the Extensions dialog, which you use to enable extensions and fault trapping
for applications under test on your host machine.
Recorder opens the Recorder Options dialog, which allows you to specify settings that SilkTest
uses when recording.
SilkPerformer Recorder opens the SilkPerformer Recorder Options dialog which you use to set
recording options for SilkTest's SilkPerformer Recorder.
Class Map opens the Class Map dialog, which you use to map custom classes to standard
classes supported by SilkTest.
Property Sets opens the Property Sets dialog, which allows you to create, modify, combine, and
delete property sets, which are used to verify properties in testcases.
188
Source Control is available if you have a software control (version control) application installed.
Displays cascading menu that allows you to manage your SilkTest test files with your installed
software control application. This is not available with SilkTest International.
Test Manager URLs opens the SilkCentral URLs dialog, which you can use to change the "home
page" address (URL) for the Issue Manager and Test Manager consoles that are displayed in
embedded browser windows in SilkTest.
Open Options Set opens the Open Options Set dialog, a standard file-opening dialog that you can
use to load the set of custom Agent, runtime, and class map options and Library Browser Help
files that you want to be in effect for the current suite, script, or testplan.
Save New Options Set opens the Save Options Set As dialog, which you use to save the current
set of Agent, runtime, and class map options and Library Browser Help files. Close Options Set
deactivates the current options set. This command is available only when a set of custom Agent,
runtime, and class map options is in effect. The file name disappears from the title bar. The
default options are now in effect.
n option-file-name displays a list of from 1 to n file names. Each is a custom options file that you
have loaded during the current work session. File names are prefaced by an integer, n, where the
last-loaded options file is listed first. You can click on a file name to have a new set of options in
effect. Alternatively, you can select a file name by its number; for example, to load the options in
the second file in the list, press Alt+O+2.
26. What is the importance of Results Menu
Select displays the Select Results dialog, which allows you to chose which set of results to
display. You can also use this dialog to add a comment to individual results sets. This dialog is
available only when the active window is a results window. Move to description of Select Results
dialog: By default, SilkTest saves the results of five executions per script, suite, or testplan. To
change the default number of results saved, edit the History Size option in the Runtime Options
dialog, available by clicking Options/Runtime.
Merge displays the Merge Results dialog, which you use to combine the active results file with the
results file of your choice. This dialog is available only when the active window is the testplan
editor results window. For more information, see Merging testplan
results.
Delete displays the Delete Results dialog. When you select a set of results and click OK, SilkTest
deletes it. This dialog is available only when the active window is a results window.
Extract displays the Extract Results dialog, which allows you to place selected information from a
results file in ASCII format into a new editor window or a file or send the information to a printer.
This dialog is available only when the active window is a results window.
189
Export displays the Export Results dialog, which you can use to export your results to a
structured file that is suitable for further processing by an application such as a spreadsheet. This
dialog is availlable only when the active window is a results window.
Send to Issue Manager displays the Send Results dialog, which you can use to send your results
directly to Issue Manager, the Segue product that you can use to manage your application’s bug
reports, enhancement requests, and documentation issues. This dialog is available only when the
active window is a results window. For more information, see sending results to Issue Manager.
Convert to Plan displays the Convert Results to Plan dialog, which allows you to transform a
results file into a testplan. This dialog is available only when the active window is a results
window and you have run a script, a suite, or a single testcase from a script.
Compact removes unused space in a results file, thereby reducing the file size. This command is
available only when the active window is a results window for a testplan. Show Summary displays
the results summary for the current suite, testplan, script, or testcase, including the start and
elapsed time, and error totals. This command is available only when the active window is a
results window. By default, a summary is shown for the script.
Hide Summary hides the display of results summary of the current suite, script, testplan, or
testcase. To have the summary hidden by default, see see Overall results summary.
This dialog is available only when the active window is a results window.
View Options displays the View Options dialog that lets you specify which information you want
displayed in the results window and how you want the information sorted.
Goto Source displays a script file associated with the current results file, if it is closed, and makes
it the active window. If the cursor was positioned at an error message in the results file, SilkTest
positions the cursor at the error line in the script. If the cursor was positioned at the results for a
particular testcase, SilkTest positions the cursor at the beginning of the testcase in the script file.
This dialog is available only when the active window is a results window.
View Differences opens the Difference Viewer when you click on the icon. This command is
available only when the active window is a results window, and the current line of the results file
displays a box icon preceding an error message. For more information, see Finding application
logic errors.
Mark Failures in Plan marks all testcases in the testplan that generated errors during the last plan
execution and makes the testplan the active window. A black stripe in the margin denotes the
marked testcases. Mark Failures in Plan is useful if you want to fix errors and rerun only failed
tests. This dialog is available only when the active window is a the testplan editor results window.
Update Expected Value replaces the expected value in the testcase with the actual value when
an error message is selected. This command is available only when the active window is a results
190
window. This works for certain error messages, namely those that contain a box icon and are
neither bitmap nor table verification errors. This command updates data within a testcase, not
data passed in from the testplan. It also makes the associated script file active.
Pass/Fail Report displays the Results Pass/Fail Report dialog, which generates an onscreen
report on the number and percentage of tests that have passed. This dialog is available only
when a results file produced by running a testplan is the active window.
Compare Two Results opens the Compare Two Results... which lets you to see results that have
changed from a previous run of the testplan. This command is available only when the active
window is a results window for a testplan.
Next Result Difference locates the next difference between two results files. You use this
command after you click Results/Compare Two Results. This command is available only when a
results file produced by running a testplan is the active window.
Next Error Difference locates the next difference between two results files that is due to the
pass/fail state of a test changing (skipping over differences resulting from the addition or removal
of tests). You use this command after you click Results/Compare Two Results. This command is
available only when a results file produced by running a testplan is the active window. For more
information, see Comparing different runs of a testplan.
27. What is the importance of Record Menu
Record menu
The Record menu contains the following commands.
Window Declarations opens the Record Windows Declarations dialog. Use this dialog to record
descriptions, called window declarations, of the GUI objects in your application and insert them
into a declarations file, called an include file (*.inc).
Application State opens the Record Application State dialog which you use to define an
application state routine that SilkTest runs before it executes your testcase.
Testcase opens the Record Testcase dialog which you use to record an entire testcase,
specifying the application state of your choice and including verification statements. Method
opens the Record Method dialog which you use to record a method for a class or window
declaration.
Actions opens the Record Actions dialog where you record actions you perform to test an
application.
191
Class opens the Record Class dialog where you record a new Visual Basic, Active X, or Java
class declaration.
Window Identifiers opens the Record Window Identifiers dialog which you use to record a fully
qualified GUI object name.
Window Locations opens the Record Window Locations dialog which you use to record the x, y
locations of a graphical control, such as a toolbar.
SilkPerformer Script opens the Record SilkPerformer Script dialog which you use to record a
SilkPerformer script from SilkTest.
28. What is the importance of Run Menu
Run menu
The Run menu contains the following commands.
Compile compiles the testplan, suite, or script and all dependent files (such as include files), if
they have changed since they were last compiled.
Compile all compiles the script or suite and all dependent include files, even if they have not
changed since they were last compiled. If the Save object files during compilation checkbox is
enabled on the Runtime Options dialog, then Compile All will create object files (*.o).
Note If the Save object files during compilation checkbox is not enabled, SilkTest does not create
object files (*.o) when you select Run/Compile all. In order to force SilkTest to create an object file
without enabling the Save object files during compilation checkbox, you must modify the source
file and compile or save it. (Compiling saves modified files, and saving saves source, object, and
backup files.)
Run compiles and runs the 4Test script, suite, or testplan in the active window.
Run All Tests executes all the tests in the testplan, first expanding any subplans. This command
is available only for the testplan editor.
Run Marked Tests executes only the marked tests in the testplan, first expanding any subplans.
This command is available only for the testplan editor.
192
Debug reads the script in the active window into a debugging window and enters debugging
mode. This is available only when the file in the active window is a script.
Application State opens the Run Application dialog where you run or debug an application state
defined in your test frame file or the active script file.
Testcase opens the Run Testcase dialog where you can select a testcase to run or debug.
Show Status hides or shows the Runtime Status dialog when running a script, suite, testcase, or
testplan on a target machine that is not the host machine.
Abort terminates the script, suite, testcase, or testplan that is currently executing. This command
is available only when a program is being run or debugged on a target machine other than the
host machine.
29. What is the Importance of Debug Menu
Debug menu
The Debug menu contains the following commands, all of which are available only in
debugging mode.
Abort terminates execution of the script you are debugging. Abort appears when you have
executed scripts on a target machine.
Exit quits debugging mode.
Finish Function executes the script until the current function returns.
Reset frees memory and all variables, and clears the call stack of the script you are debugging.
Run and Debug/Continue runs the script in the debugging window until the first breakpoint, if any,
is reached. Execution stops just before the line with the breakpoint.
Run to Cursor sets a temporary breakpoint (indicated by a hollow red circle in the margin) on the
line containing the cursor. SilkTest immediately runs the script, stopping at the current line. The
breakpoint is cleared after it is hit.
Step Into is available only after using Debug/Run and execution has stopped at a breakpoint.
193
Executes the current line of 4Test code in the active script or in a file called by the active script. If
the current line has a breakpoint, SilkTest executes the line. If the current line contains a function
call, control passes into the function; SilkTest stops at the first statement. Step Over is available
only after using Debug/Run and execution has stopped at a breakpoint. Executes the current line
of 4Test code in the active script or in a file called by the active script, without stepping into any
functions called by the current line. Control stops at the next statement.
30. What is Data Driven Testing
Working with data driven testcases
This information will be helpful to know when you are working with data driven testcases.
· When you are working with a data driven testcase, the 4Test Editor contains additional menu
selections and toolbars for you to use.
· SilkTest can data drive only one testcase at a time.
· You cannot duplicate testcase names. Data driven testcases in the same script must have
unique names.
· The Classic 4Test editor is not available with data driven testcases (in .g.t files).
· You cannot create data driven testcases from testcases in .inc files; you can only create data
driven testcases from testcases in .t or .g.t files. However, you can open a project, add the *.inc,
select the testcase from the testcase folder of the project, and then select data drive. · When you
data drive a [use '

DATABASE TESTING

2008-07-12T21:56:00.001-07:00

1. what SQL statements have you used in Database Testing?
2. How to test data loading in Data base testing
Using with Query analyser.
3. What is way of writing testcases for database testing?
For writing test cases in Database first one should define the project name, then module,Bug
number,objective,steps/action undertaken,expected result,actual result, then status, priority and
severity.
4. What is Database testing?
5. What we normally check for in the Database Testing?
In DB testing we need to check for, 1. The field size validation 2. Check constraints. 3. Indexes
are done or not (for performance related issues) 4. Stored procedures 5. The field size defined in
the application is matching with that in the db.
6. How to Test database in Manually? Explain with an example
We should also check the non editable fields thru databasefor example,If a field is non editable
via front end, then the user should not be allowed to add a record thru database also
1. How do you rename all of the jobs to support your new File-naming conventions?
2. Does the selection of 'Clear the table and Insert rows' in the ODBC stage send a
Truncate statement to the DB or does it do some kind of Delete logic.
3. Tell me one situation from your last project, where you had faced problem and How did
u solve it?
4. The above might rise another question: Why do we have to load the dimensional tables
first, then fact tables:
5. How will you determine the sequence of jobs to load into data warehouse?
6. What are the command line functions that import and export the DS jobs?
7. What is the utility you use to schedule the jobs on a UNIX server other than using
Ascential Director?
8. How would call an external Java function which are not supported by DataStage?
175
9. What will you in a situation where somebody wants to send you a file and use that file
as an input or reference and then run job.
10. Read the String functions in DS
11. How did u connect with DB2 in your last project?
12. What are Sequencers?
13. How did you handle an 'Aborted' sequencer?
14. What are other Performance tunings you have done in your last project to increase the
performance of slowly running jobs?
15. How did you handle reject data?
16. If worked with DS6.0 and latest versions what are Link-Partitioner and Link-Collector
used for?
17. What are Routines and where/how are they written and have you written any routines
before?
18. What are OConv () and Iconv () functions and where are they used?
19. How did u connect to DB2 in your last project?
20. Do u know about METASTAGE?
21. Do you know about INTEGRITY/QUALITY stage?
22. Explain the differences between Oracle8i/9i?
23. How good are you with your PL/SQL?
24. Did you work in UNIX environment?
25. What other ETL's you have worked with?
26. What versions of DS you worked with?
27. What is DS Designer used for - did u use it?
28. What is DS Administrator used for - did u use it?
29. What is DS Director used for - did u use it?
30. What is DS Manager used for - did u use it?
31. What are Static Hash files and Dynamic Hash files?
32. What is Hash file stage and what is it used for?
33. Have you ever involved in updating the DS versions like DS 5.X, if so tell us some the
steps you have taken in doing so?
34. Did you Parameterize the job or hard-coded the values in the jobs?
35. How do you merge two files in DS?

QTP INTERVIEW QUESTIONS AND ANSWERS

2008-07-05T00:03:00.000-07:00

1. How can an object from a per action repository be called to another per action
repository?

2. How you write scripts in QTP? What's the main process in QTP? How do you run
scripts in QTP?

3. What is the command in QTP to invoke IE Brow?
SystemUtil.Run "iexplore"

4. Hi,I am new to QTP, please tell me how to invoke an application in QTP.Forexample:In
winrunner we use

5. differenced between quick test proffesional version 5.6 and 8.2
These are the new features which are available in QTP8.2 and which are not present in 6.5
version.Keyword View: Lets you easily build and maintain tests without writingVBScripts.Auto-
Documentation: Provides improved test clarity and the ability toview test steps in plain
English.Step Generator: Allows

6. How would u manipulate the script so that when the test is run it takes a new login
name?
You can parameterize the values in the Gobal data table sheet, whatever the number of rows you
enter in this data table will instruct QuickTest to run same number of new login name you've
enter.

7. How can i add a action (external action) programatically?
You can add an external Action programatically using the CommandRunAction ActionName,
[IterationMode , IterationRange]Before you can use the RunAction statement in the Expert View
for an external action, you must first call or copy the external action into your test by choosing
Insert > Copy

8. How can i call a external action which is not added external action of an action. Means I
want to call
Yes u can do it by copying the Action c to Action A...In QTP 8.2 there is an menu called insert-
Copy of Action...

9. what is meant by SOURCE CONTROL ?
It is used to hold all the bulids of diff versions

10. how and what kind of Vb functions do u use in qtp?
You can use The following functionsAsc Function====CBool Function===CByte
Function===CCur Function===CDate Function===CDbl Function===Chr Function===CInt
Function===CLng FunctionCSng FunctionCStr FunctionHex FunctionOct Function===etc

11. how can u discribe the basic flow of automation with conditional and programatic
Executing of operators flow in the automation code if the question is that then my answer is
===For example: z = 78 * (96 + 3 + 45)There are five operators in this expression: =, *, (), +, and
another +. According to the rules of operator precedence, they are evaluated

12. HOW CAN I IMPLEMENT ERROR HANDLING IN QTP,I KNOW WITH RECOVERY
MANAGER BUT HOW PLZ GIVE ME DETAILED TO
U can do it thru Recovery Manager..Eg...Suppose there is an Edit box called Uname n
PWD...Just type in uname n don't enter in PWD..It displays a pop up msg called plz,,enter
PWD...Then stop recording..Goto Recovery MGR and call POPUP exception handling./../

13. How to recall a function in QTP
There also u follow the same procedure. See the sample codeFunction addition(x,y) z= x+y
msgbox zEnd FunctionCall addition(1,2)Call addition(2,2)I think i am clear :)

14. Give one example where you have used Regular Expression?
While validating 'Date format' .

15. How can I implement error handling in QTP, I know with Recovery Mangaer but how
please give me detailed

16. How to select particular value from the combo box in the current page which is
entered in the previous

17. If you have the same application screen with 7 drop down boxes and approximately 70
values how do you Record the 7 test objects (dropdown boxs) and there will be many 70 properties ( and their
associated bvalues) Drop Down Box 1

18. When there is a task that gets repeated in multiple scripts, what do you do in QTP?
Split the action related to that task, make it Reusable & then call that Action as many times as
needed.

19. what is the descrirptive progrmaing?.what is the use of descriptive programing?
Descriptive programming is used to identify the objects that are not/cannot be stored in the object
repository. Descriptive programming can be implemented by creating and using a Description
object.

20. I Have an interview in Qtp..Please could any one give me the hints what will they ask in
interview..this

21. How to instruct QTP to display errors and ther description in the test results instead of
halting execution Make use of Reporter.Reportevent eg.var=statementif var="True" ThenReporter.Reportevent
0,"Step Name","Description of the Passed step"elseReporter.Reportevent 1,"Step
Name","Description for the failed step"End IfI hope thats it :)

22. How you write scripts in qtp?what's the main process in qtp?How do you run scripts
in Qtp?Please anyone

23. What is descriptive programming?
Please see Questions Number 13 for answer. Its just 4 Questions above this questions. You can
find answer there.Thanks, Venkat

24. How to add run-time parameter to a datasheet?
Try using this line of code.DataTable("Col Name",dtGlobalSheet/LocalSheet)="Col Value"The
only disadvantage with tihs code is, u will be able to see the parameter till the script is running,
once stopped the parameter will vanish from the data table.

25. how to load the *.vbs or test generating script in a new machine?
Execute File statement can be included as part of the test script inorder to execute the vbs files.

26. how can u write a script without using a GUI in QTP?
GUI in Qtp?do you mean to say Object repository?without OR,tester need to write descriptive
tests,where you would directly assign property values and write methods.you do not need to save
OR.

27. How can we write scripts without having GUI(means u dont have any GUI and u want
to write a script in

28. Can we update the database though Qtp.

29. I am using the QTPlus Repositories Merge Utility to merge all my different repositories
into a single
Merge Utility have a lot of problems, try don't use this for file biggest the 8 MB

30. if a error occur during the excution of QTP script. how can we get the name of the
current object that
Use Err.descriptionExample. msgbox "Error:"&err.description

31. What is the procedure to test flash applications using QTP?

32. how to fetch test data from Database by using QTP?
In order to fetch test data from Database we have to create a adobdb connection object to
connect with data base. the syntax is .... >CreateObject("Adodb.connection").

33. how to handle java tree in QTP
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 recognise the objects there select
the tree option.Add the properties to be recognised.Then the QTP will start

34. what if storage limit of shared object repository exceeds its limit(2 MB).how this kind
of situation One can use advanced object repository Editor from Sirus SQA

35. Explain as to how would you design the driver code for a keyword based test script.

36. Testing > QTPWhich feature of QTP would you like to improve ?How would you go
about implementing it ?(This

37. How can we do the Frame work in QTP

38. how many types of recording modes in QTP?describe each type with an example
where we use them?
3 types of recording modes in QTP.1.norma 2.analog mode 3.low level recording mode.pls
describe where we use them exactly..

39. What is the file extension of the code file & object repository file in QTP?
.TSR

40. I want to open a Notepad window without recording a test and I do not want to use
SystemUtil.Run command
Another alternative to open a notepad is to use ShellObject. Check out with the following
example:Dim aSet a = WScript.CreateObject ("WSCript.shell")a.run "notepad.exe"

41. How many types of Actions are there in QTP?
In qtp 3 types of action r there 1)re-usable2)no-reusable3)Nested

42. How to do the scripting. Is there any inbuilt functions in QTP as in QTP-S. Whatz the
difference
there's an in-built functionality called "Step Generator" in Insert->Step->Step Generator -F7,
which will generate the scripts as u enter the appropriate steps.

43. Explain the concept of object repository & how QTP recognises objects?
with QTP 8.2 ,there available QTP Plus,setup.It provides Repositories Merge Utility.The Object
Repository Merge Utility enables user to merge Object repository files into a single Object
repository file.

44. How do you data drive an external spreadsheet?
Import from External Spreadsheet File by selecting Import then From File . Which 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 sheet of the table, and the first row in the

45. IF we use batch testing.the result shown for last action only.in that how can i get
result for every
click on the icon in the tree view to view the result of every action

46. How to handle dynamic objects in QTP?
Using GETRO Property we will handle the runtime objects.

47. Can you do more than just capture and playback?
Yes you can do more than capture/playback. Descriptive Programming is the answer to this
question. We can write scripts without recording and it would still work fine.

48. How to handle the exceptions using recovery secnario manager in Qtp?
There are 4 trigger events during which a recovery scenario should be activated. They are 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

49. What are the Features & Benefits of Quick Test Pro(QTP)..?
Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality
Center. Introduces next-generation “zero-configuration” Keyword Driven testing technology in
QuickTest Professional 8.0 — allowing for fast test creation, easier maintenance, and more
powerful data-driving capability

50. How does Parameterization and Data-Driving relate to each other in QTP?

51. Explain in brief about the QTP Automation Object Model.

52. What is a Run-Time Data Table? Where can I find and view this table?
The test results tree also includes the table-shaped icon that displays the run-time Data Table—a
table that shows the values used to run a test containing Data Table parameters or the Data
Table output values retrieved from a test while application test run.

53. What are the different scripting languages you could use when working with QTP ?
This will also support java script, but i hve not tries refer Quick test plus help for each function
they have give code in vbs and js.

54. How do you test siebel application using qtp?
In SWE section u need to addAutomationEnable = TRUE and at the same time you need to use
SWECmd= AutoOn in the URL

55. How the exception handling can be done using QTP
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

56. What is the difference between check point and output value.
additional comment on Above comment:An output value is a value retrieved during the
runsession and entered into runtime table or data table subsequently it can be used as input
value in your test.

57. What are the properties you would use for identifying a browser & page when using
descriptive programming
Logical Name of BrowserLogical Name of Pagee.g. Browser("myBrowser").Page("myPage")

58. What projects have you used WinRunner on? Tell me about some of the challenges
that arose and how you
pbs :WR fails to identify the object in gui. If there is a non std window obk wr cannot recognize it
,we use GUI SPY for that to handle such situation

59. Differentiate the two Object Repository Types of QTP.
In Qtp there are 2 object repositories, they are1.Shared Object Repository2.Per Action Mode,by
default it's per action mode.we will use shared OR for calling a particular action,it's like calling
external libraries.we will use per action for a particular action ie, for one action only.

60. Explain the concept of how QTP identifies object.
During recording qtp looks at the object and stores it as test object.For each test object QT 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 object. During test run,QT

61. What is the difference between Call to Action and Copy Action.?
when u insert a call to action,they r read only in the calling test.It can be modified in the original
test.where as come to copy action,you can make changes to the copied action,your changes will
not effect the original action where it created.

62. have you ever written a compiled module? If yes tell me about some of the functions
that you wrote.
functions for Capturing the dynamic data during runtime. Function used for Capturing Desktop,
browser and pages.

63. Explain what the difference between Shared Repository and Per_Action Repository
In Shared reporsitory, one object is used in more than one actions and in per action reporsitory,
everytime in every action, objects are stored differently and are not shared.

64. Discuss QTP Environment.
QuickTest Pro environment using the graphical interface and ActiveScreen 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 one test script.

65. What the differences are and best practical application of each.
Per Action: For Each Action, one Object Repository is created. Shared : One Object Repository
is used by entire application

66. Few basic questions on commonly used Excel VBA functions.
common functions are: Coloring the cell Auto fit cell setting navigation from link in one cell to
other saving

67. Explain the keyword createobject with an example.
Createobject:Creates and returns a reference to an Automation object.Example:Dim
ExcelSheetSet ExcelSheet = CreateObject("Excel.Sheet")

68. How long have you used the product?

69. How to use the Object spy in QTP 8.0 version?

70. Give me an example where you have used a COM interface in your QTP project?
com inteface appears in the scenario of front end and back end.for eg:if you r 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 wil be one among those intefaces.

71. what is the use of Text output value in Qtp?
Answer posted by shreethik on 2005-06-09 08:36:38: Output values enable to view the values
that the application talkes during run time.When paramaterised, 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

72. Where can I get Quck Test pro(QTP Pro) software.. This is Just for Information
purpose Only.
Introduction to QuickTest Professional 8.0, Computer Based Training: Please find the step to get
QuickTest Professional 8.0 CBT Step by Step Tutorial and Evaluation copy of the software. The
full CBT is 162 MB. You will have to create account to be able to download evaluation copies of
CBT and Software.Click

Testing

2008-07-02T10:25:00.000-07:00

Explain testing process of your company?

Is functional and black box testing same or not

Diff stages between open and fixed status in defect bug cycle

What is the difference between functional testing and regression testing?
What are the deferent defect statuses?
What is the difference between severity and priority?

How you assign severity for a defect?

What is test deliverables?

Black box testing: Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.

White box testing: based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing: the most ‘micro’ scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
1. What is load testing? - Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine weather it can handle peak usage periods.
2. What is Performance testing? - Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction.
wsp to http witch part will convert in wap
What is Defect Leakage?
Defect leakage occurs at the Customer or the End user side after the application delivery. After the release of the application to the client, if the end user gets any type of defects by using that application then it is called as Defect leakage. This Defect Leakage is also called as Bug Leak.

What are the contents in an effective Bug report?
Project, Subject, Description, Summary, Detected By (Name of the Tester), Assigned To (Name of the Developer who is supposed to the Bug), Test Lead ( Name ), Detected in Version, Closed in Version, Date Detected, Expected Date of Closure, Actual Date of Closure, Priority (Medium, Low, High, Urgent), Severity (Ranges from 1 to 5), Status, Bug ID, Attachment, Test Case Failed (Test case that is failed for the Bug)

What is Bug Life Cycle?

Bug Life Cycle is nothing but the various phases a Bug undergoes after it is raised or reported.
New or Opened, Assigned, Fixed, Tested, closed

What is the difference between Bug, Error and Defect?

Error: It is the Deviation from actual and the expected value.
Bug: It is found in the development environment before the product is shipped to the respective customer.
Defect: It is found in the product itself after it is shipped to the respective customer.

Negative testing –
Testing the system using negative data is called negative testing, e.g. testing the password where it should be minimum of 8 characters so testing it using 6 characters is negative testing.

Explain Load, Performance and Stress Testing with an Example.
Load Testing and Performance Testing are commonly said as positive testing where as Stress Testing is said to be as negative testing.
Say for example there is a application which can handle 25 simultaneous user logins at a time. In load testing we will test the application for 25 users and check how application is working in this stage, in performance testing we will concentrate on the time taken to perform the operation.

Where as in stress testing we will test with more users than 25 and the test will continue to any number and we will check where the application is cracking.

What are SDLC and STLC? Explain its different phases.
SDLC
 Requirement phase
 Designing phase (HLD, DLD (Program spec))
 Coding
 Testing
 Release
 Maintenance
STLC
 System Study
 Test planning
 Writing Test case or scripts
 Review the test case
 Executing test case
 Bug tracking
 Report the defect

What is Ad-hoc testing?
Ad hoc testing is concern with the Application Testing without following any rules or test cases.
For Ad hoc testing one should have strong knowledge about the Application.

What is the difference between structural and functional testing?

Structural testing is a "white box" testing and it is based on the algorithm or code.
Functional testing is a "black box" (behavioral) testing where the tester verifies the functional specification.

What is Re- test? What is Regression Testing?

Re- test - Retesting means we testing only the certain part of an application again and not considering how it will effect in the other part or in the whole application.

Regression Testing - Testing the application after a change in a module or part of the application for testing that is the code change will affect rest of the application.

What is UAT testing? When it is to be done?

UAT testing - UAT stands for 'User acceptance Testing. This testing is carried out with the user perspective and it is usually done before the release.

What software testing types can be considered?

Black box testing –
This type of testing doesn’t require any knowledge of the internal design or coding. These Tests are based on the requirements and functionality.

White box testing –
This kind of testing is based on the knowledge of internal logic of a particular application code. The Testing is done based on the coverage of code statements, paths, conditions.

Unit testing – The 'micro' scale of testing; this is mostly used to test the particular functions or code modules. This is typically done by the programmer and not by testers; it requires detailed knowledge of the internal program design and code. It cannot be done easily unless the application has a well-designed architecture with tight code; this type may require developing test driver modules or test harnesses.

Sanity Testing or Smoke Testing – This type of testing is done initially to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing the systems in every 5 minutes or corrupting databases, the software may not be in a 'sound’ condition to proceed for further testing in its current state.

Functional Testing – This a commonly used black-box testing geared to check the functional requirements of an application; this type of testing should be done by testers.

Integration Testing – This testing is combining the ‘parts’ of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to the client/server and distributed systems.

Incremental Integration testing –
This is continuous testing of an application when a new functionality is added the existing ones; it checks the application functionality by verifying whether it works separately before all parts of the program are completed, in this type it will be checked whether to introduce test drivers or not; this is done by programmers or by testers.

Regression Testing – This is testing the whole application again after the fixes or the modifications are done on the software. This is mostly done at the end of the Software development life cycle. Mostly Automated testing tools are used for this type of testing.

System testing – This is a type of black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.

End-to-end testing – This is similar to system testing; this involves testing of a complete application environment such as interacting with a database, using network communications, or interacting with other hardware, applications and so on.

UAT (User Acceptance Testing) – This type of testing comes on the final stage and mostly done on the specifications of the end-user or client.

Usability testing – This testing is done to check the 'user-friendliness' of the application. This depends on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

Compatibility testing – Testing how well the software performs in a particular hardware, software, operating system, network etc.

Comparison testing – This is nothing comparing the software strengths and weakness with another competing product.

Mutation testing – This is another method for determining if a set of test data or test cases is useful, by purposely introducing various code changes or bugs and retesting with the original test data or cases to determine whether the 'bugs' are detected.

Describe the difference between validation and verification

Verification is done by frequent evaluation and meetings to appraise the documents, policy, code, requirements, and specifications. This is done with the checklists, walkthroughs, and inspection meetings.

Validation is done during actual testing and it takes place after all the verifications are being done.

What is the difference between QA and testing?

Testing involves operation of a system or application under controlled conditions and evaluating the results. It is oriented to 'detection'.

Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.

What is quality assurance?

Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.

What is the purpose of the testing?

Software testing is the process used to help identify the Correctness, Completeness, Security and Quality of the developed Computer Software.

Software Testing is the process of executing a program or system with the intent of finding errors.

1. What is Software Testing?
2. What is the Purpose of Testing?
3. What types of testing do testers perform?
4. What is the Outcome of Testing?
5. What kind of testing have you done?
6. What is the need for testing?
7. What are the entry criteria for Functionality and Performance testing?
8. What is test metrics?
9. Why do you go for White box testing, when Black box testing is available?
10. What are the entry criteria for Automation testing?
11. When to start and Stop Testing?
12. What is Quality?
13. What is Baseline document, Can you say any two?
14. What is verification?
15. What is validation?
16. What is quality assurance?
17. What is quality control?
18. What is SDLC and TDLC?
19. What are the Qualities of a Tester?
20. When to start and Stop Testing?
21. What are the various levels of testing?
22. What are the types of testing you know and you experienced?
23. What exactly is Heuristic checklist approach for unit testing?
24. After completing testing, what would you deliver to the client?
25. What is a Test Bed?
26. What is a Data Guidelines?
27. Why do you go for Test Bed?
28. What is Severity and Priority and who will decide what?
29. Can Automation testing replace manual testing? If it so, how?
30. What is a test case?
31. What is a test condition?
32. What is the test script?
33. What is the test data?
34. What is an Inconsistent bug?
35. What is the difference between Re-testing and Regression testing?
36. What are the different types of testing techniques?
37. What are the different types of test case techniques?
38. What are the risks involved in testing?
39. Differentiate Test bed and Test Environment?
40. What ifs the difference between defect, error, bug, failure, fault?
41. What is the difference between quality and testing?
42. What is the difference between White & Black Box Testing?
43. What is the difference between Quality Assurance and Quality Control?
44. What is the difference between Testing and debugging?
45. What is the difference between bug and defect?
46. What is the difference between verification and validation?
47. What is the difference between functional spec. and Business requirement specification?
48. What is the difference between unit testing and integration testing?
49. What is the diff between Volume & Load?
50. What is diff between Volume & Stress?
51. What is the diff between Stress & Load Testing?
52. What is the Diff between Two Tier & Three tier Architecture?
53. What is the diff between Client Server & Web Based Testing?
54. What is the diff between Integration & System Testing?
55. What is the Diff between Code Walkthrough & Code Review?
56. What is the diff between walkthrough and inspection?
57. What is the Diff between SIT & IST?
58. What is the Diff between static and dynamic?
59. What is the diff between alpha testing and beta testing?
60. What are the Minimum requirements to start testing?
61. What is Smoke Testing & when it will be done?
62. What is Adhoc Testing? When it can be done?
63. What is cookie testing?
64. What is security testing?
65. What is database testing?
66. What is the relation ship between Quality & Testing?
67. How do you determine, what to be tested?
68. How do you go about testing a project?
69. What is the Initial Stage of testing?
70. What is Web Based Application Testing?
71. What is Client Server Application Testing?
72. What is Two Tier & Three tier Architecture?
73. What is the use of Functional Specification?
74. Why do we prepare test condition, test cases, test script (Before Starting Testing)?
75. Is it not waste of time in preparing the test condition, test case & Test Script?
76. How do you go about testing of Web Application?
77. How do you go about testing of Client Server Application?
78. What is meant by Static Testing?
79. Can the static testing be done for both Web & Client Server Application?
80. In the Static Testing, what all can be tested?
81. Can test condition, test case & test script help you in performing the static testing?
82. What is meant by dynamic testing?
83. Is the dynamic testing a functional testing?
84. Is the Static testing a functional testing?
85. What are the functional testing you perform?
86. What is meant by Alpha Testing?
87. What kind of Document you need for going for an Functional testing?
88. What is meant by Beta Testing?
89. At what stage the unit testing has to be done?
90 Who can perform the Unit Testing?
91. When will the Verification & Validation be done?
92. What is meant by Code Walkthrough?
93. What is meant Code Review?
94. What is the testing that a tester performs at the end of Unit Testing?
95. What are the things, you prefer & Prepare before starting Testing?
96. What is Integration Testing?
97. What is Incremental Integration Testing?
98. What is meant by System Testing?
99. What is meant by SIT?
100 .When do you go for Integration Testing?
101 Can the System testing be done at any stage?
102. What are stubs & drivers?
103. What is the Concept of Up-Down & Down-Up in Testing in integration testing?
104. What is the final Stage of Integration Testing?
105. Where in the SDLC, the Testing Starts?
106. What is the Outcome of Integration Testing?
107. What is meant by GUI Testing?
108. What is meant by Back-End Testing?
109. What are the features, you take care in Prototype testing?
110. What is Mutation testing & when can it be done?
111. What is Compatibility Testing?
112. What is Usability Testing?
113 What is the Importance of testing?
114. What is meant by regression Testing?
115. When we prefer Regression & what are the stages where we go for Regression Testing?
116. What is performance testing?
117. What is the Performance testing; those can be done Manually & Automatically?
118 What is Volume, Stress & Load Testing?
119. What is a Bug?
120. What is a Defect?
121. What is the defect Life Cycle?
122. What is the Priority in fixing the Bugs?
123. Explain the Severity you rate for the bugs found?
124. Diff between UAT & IST?
125. What is meant by UAT?
126. What all are the requirements needed for UAT?
127. What are the docs required for Performance Testing?
128. What is risk analysis?
129. How to do risk management?
130. What are test closure documents?
131. What is traceability matrix?
132. What ways you followed for defect management?
133. What is diff between Smoke Testing and Sanity Testing?

Answers

1. What is Software Testing?

A. Testing involves operation of a system or application under controlled conditions and evaluating the results, the controlled conditions should include both normal and abnormal conditions.
Testing is a process of executing a program with the intend of finding the errors.

2. What is the Purpose of Testing?

A. The purpose of testing is
1· To uncover hidden errors
2· To achieve the maximum usability of the system
3· To Demonstrate expected performance of the system
3. What types of testing do testers perform?
A. Two types of testing 1.White Box Testing 2.Black Box Testing.

4. What is the Outcome of Testing?
A. The outcome of testing will be a stable application which meets the customer Req's.

5. What kind of testing have you done?
A. Usability, Functionality, System testing, regression testing, UAT
(it depends on the person).

6. What is the need for testing?

A. The Primary need is to match requirements get satisfied with the functionality and also to answer two questions
1· Whether the system is doing what it supposes to do?
2· Whether the system is not performing what it is not suppose to do?

7. What are the entry criteria for Functionality and Performance testing?
A. Entry criteria for Functionality testing is Functional Specification /BRS (CRS)/User Manual. An integrated application, Stable for testing.

Entry criteria for Performance testing is successfully of functional testing, Once all the requirements related to functional are covered and tested, and approved or validated.

8. What is test metrics?
A. *

9. Why do you go for White box testing, when Black box testing is available?
A. A benchmark that certifies Commercial (Business) aspects and also functional (technical) aspects is objectives of black box testing. Here loops, structures, arrays, conditions, files, etc are very micro level but they arc Basement for any application, So White box takes these things in Macro level and test these things

Even though Black box testing is available, we should go for White box testing also, to check the correctness of code and for integrating the modules.

10. What are the entry criteria for Automation testing?
A. Application should be stable. Clear Design and Flow of the application is needed.

11. When to start and Stop Testing?
A. This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done.
Common factors in deciding when to stop are:

Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a specified point
Bug rate falls below a certain level
Beta or alpha testing period ends

12. What is Quality?
A. It ensures that software is a Bug free, delivered in time, with in budget, meets customer requirements and maintainable. Quality standards are different in various areas like accounting department might define quality in terms of Profit.

13. What is Baseline document?
A. The review and approved document is called as baseline document (i.e)Test plan, SRS.

14. What is verification?
A. To check whether we are developing the right product according to the customer requirements r not. It is a static process.

15. What is validation?
A. To check whether we have developed the product according to the customer requirements r not. It is a Dynamic process.

16. What is quality assurance?
A. Quality Assurance measures the quality of processes used to create a quality product.
1. It is a system of management activities.
2. It is a preventive process.
3. It applies for entire life cycle.
4. Deals with Process.

17. What is quality control?
A. Quality control measures the quality of a product
1. It is a specific part of the QA procedure.
2. It is a corrective process.
3. It applies for particular product.
4. Deals with the product.

18. What is SDLC and TDLC?
A. Software development life cycle (SDLC) is life cycle of a project from starting to ending of the project.
1. Requirements Specification.
2. Analysis
3. Design
4. Coding 5. Testing
6. User acceptance test (UAT) 7. Maintenance

Software Test Life Cycle (STLC) is a life cycle of the testing process.
1. Requirements Specification.
2. Planning
3. Test case Design 4.Execution
5. Bug Reporting . 6. Maintenance

19. What are the Qualities of a Tester?
A. Tester should have qualities like
1. Ability to break 2.paitence 3.communication
4. Presentation 5.team work. 6. Negative thinking with good judgment skills

20. When to start and Stop Testing?
A. repeat

21. What are the various levels of testing?
A. The various levels of testing like
1· Ad - Hoc testing
2. Sanity Test
3. Regression Testing
4. Functional testing
5· Web Testing

22. What are the types of testing you know and you experienced?
A. I am experienced in Black Box testing.

24. After completing testing, what would you deliver to the client?
A. It is depend upon what you have specified in the test plan document. The contents delivers to the clients is nothing but Test Deliverables.
1. Test plan document 2.Master test case document 3.Test summary Report.
4. Defect Reports.

25. What is a Test Bed?
A. Test bed means under what test environment (Hardware, Software set up) the application will run smoothly.

26. What is a Data Guidelines?

27. Why do you go for Test Bed?
A. We will prepare test bed because first we need to identify under which environment (Hardware, Software) the application will run smoothly, then only we can run the application smoothly without any interceptions.

28. What is Severity and Priority and who will decide what?
A. Severity and priority will be assigned for a particular bug to know the importance of the bug.
Severity: How severely the bug is effecting the application.
Priority: Informing to the developer which bug to be fix first.

29. Can Automation testing replace manual testing? If it so, how?
A. Yes, it can be done manually when the project is small, having more time. We can test with minimum number of users.

30. What is a test case?
A. A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.

31. What is a test condition?
A. The condition required to test a feature.(pre condition)

32. What is the test script?
A. Test script is the script which is generated by an automation tool while recording a application features.

33. What is the test data?
A. Test data means the input data (valid, invalid data) giving to check the feature of an application is working correctly.

34. What is an Inconsistent bug?
A. the bug which is occurring

35. What is the difference between Re-testing and Regression testing?
A Re-testing: Executing the same test case by giving the no. of inputs on same build.
Regression testing: Executing the same test case on a modified build.

36. What are the different types of testing techniques?
A. 1.white Box testing 2.Black Box testing.

37. What are the different types of test case techniques?
A. 1. Equilance Partition. 2. Boundary Value Analysis. 3. Error guessing.

38. What are the risks involved in testing?

39. Differentiate Test bed and Test Environment?
A. Both are same.

40. What ifs the difference between defect, error, bug, failure, fault?
A. Defect: While executing the test case if u found any mismatch, the u will report
it to the development team, that is called defect.

Bug: Once the developer accepts your defect, then it is called as a bug.

Error: it may be program error or syntax error.

41. What is the difference between quality and testing?
A. QA is more a preventive thing, ensuring quality in the company and therefore the product rather than just testing the product for software bugs?

TESTING means "quality control"

Quality control measures the quality of a product
Quality Assurance measures the quality of processes used to create a quality product.

42. What is the difference between White & Black Box Testing?
A. White Box Testing: Based on the knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.

Black Box testing:- not based on any knowledge of internal design or code.
Tests are based on requirements and functionality.

43. What is the difference between Quality Assurance and Quality Control?
A. Refer Question no.16 & 17
Quality Assurance measures the quality of processes used to create a quality product.
Quality control measures the quality of the product.

44. What is the difference between Testing and debugging?
A. The Purpose of testing is to show the program has bugs.
The Purpose of debugging is find the error/ misconception that led to failure and implement program changes that correct the error.

45. What is the difference between bug and defect?
A. Defect: While executing the test case if u found any mismatch, the u will report it to the development team that is called defect.

Bug: Once the developer accepts your defect, the it is called as a bug.

46. What is the difference between verification and validation?
A. Refer Question no.14 & 15

47. What is the difference between functional spec. and Business requirement specification?
A.
48. What is the difference between unit testing and integration testing?
A. Unit Testing: It is a testing activity typically done by the developers not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code.
Integration testing: testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

49. What is the diff between Volume & Load?
A. Load, stress testing comes under performance testing.
Load Testing: To test the performance of the application by gradually increasing the user loads.

Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.

Volume Testing: To test whether it can able to send max data according to client req's.

50. What is diff between Volume & Stress?
A. Refer Question no.49

51. What is the diff between Stress & Load Testing?
A. Refer Question no.49

52. What is the Diff between Two Tier & Three tier Architecture?
A. Two Tier Architecture: It is nothing but client server Architecture, where client will hit request directly to server and client will get response directly from server.

Three tier Architecture: It is nothing but Web Based application, here in between client and server middle ware will be there, if client hits a request it will go to the middle ware and middle ware will send to server and vise-versa.

53. What is the diff between Client Server & Web Based Testing?
A. Refer Question no.52

54. What is the diff between Integration & System Testing?
A. Integration testing: Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

System Testing: System testing will conducted on the entire system to check whether
it is meeting the customer requirements r not.

55. What is the Diff between Code Walk through & Code Review?

56. What is the diff between walk through and inspection?
A. Walk through: A 'walk through' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required
Inspection: Inspection is an formal meeting, here every thing discussed will be documented such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, The result of the inspection meeting should be a written report.

57. What is the Diff between SIT & IST?

58. What is the Diff between static and dynamic?
A. Static Testing: Test activities that are performed without running the software is called Static Testing, it includes inspections, walk through and desk checks.

Dynamic testing: Test activities that are performed by running the software is called dynamic Testing.

59. What is the diff between alpha testing and beta testing?
A. Alpha Testing: alpha testing will be performed by client in our environment with dummy data, in this phase some major bugs can be allowed, later which will be solved by our development team.

Beta testing: beta testing will be performed by client in his environment with real data, in this phase no bugs can be allowed.

Deepak K R
 What is Multimedia Messaging?

 When will MMS be introduced?
 When will the consumers see this service?
 Why is MMS important?
 How would MMS look like to the end users?
 What are some examples of MMS services?
 What content types does MMS support?
 I don't have an MMS phone; can I receive / send MMS messages?
 Can MMS messages be sent to an email address?
 How does the user's MMS experience compare to that of SMS?
 Are there any MMS phones available now?
 Does MMS need 3GSM?
 How big can an MMS message be?
 How fast is an MMS message from phone to phone?
 How does MMS compare to EMS?
 How does MMS compare to email?

 How is the MMS environment different from SMS?
 Is anyone setting standards for MMS?
 What is the connection between MMS and WAP?
 Does MMS require network changes?
 How interoperable are MMS messages across manufacturers?
What is Multimedia Messaging?
Multimedia messaging is a next generation message service. Multimedia messaging allows a variety of message elements to be sent to a user and these can contain text, animations, photographs, sounds and in future streaming audio and video. Users can compose their own messages, receive rich content messages from content providers and forward them onto their own contacts.
back to top
When will MMS be introduced?
Some operators have already launched and many more will launch this summer (2002).
When will the consumers see this service?
Many operators are planning to launch before Christmas 2002.
back to top

Why is MMS important?
For the subscriber MMS takes messaging out of the basic text users are used to and allows them to enjoy a much better messaging - more like they are used to via email or the Internet e.g. to send a greetings card or photograph of themselves.
For network operators MMS is important as it is the basis for a wide range of next generation services that pave the way for the improved 3G bandwidth to show its use, drive demand for data bandwidth and consequently increase operator revenues.
How would MMS look like to the end users?
Some of the first phones are introducing colour so this is a substantial improvement over black & white text. Initial devices may maintain the conventional size display but allow colour or grey scale images. The main thing users will see is that the experience is much more dynamic - a snapshot album of thumbnail images, a sequence of a cartoon e.g. Dilbert, captions and sounds combined with images.
Back to top
What are some examples of services on MMS?
Taking a snapshot via a camera phone and sending to a friend
Receiving cartoon strips
Composing your own animated picture messages and sending to friends
Sending audio files
Sending pictures & audio files with simultaneous playback
Advertising
Music download & play (really with 3G)
Storing pictures to an on line album
Remote surveillance
What content types does MMS support?
MMS is based on common Internet technologies currently supported on a variety of content types which would include plain text, HTML, audio in a variety of formats including an efficient new standard AMR and soon MP3, pictures as GIF, JPEG, PNG and in the future video using MPEG4
back to top
I don't have an MMS phone; can I receive / send MMS messages?
You would need to be on a network that supports MMS; steps are being taken to allow MMS's to be supported at various capabilities by non MMS phone users e.g. by converting as far as possible to WAP. There are restrictions which are things like if you only have an SMS capable phone you might have to access your MMS messages using an internet connection.
Back to top
Can MMS messages be sent to an email address?
Yes, it is possible to do this - although your operator will need to support this capability
How does the user's MMS experience compare to that of SMS?
The experience is far superior especially with devices with colour displays, sound, text and picture sequences.
Are there any MMS phones available now?
The Ericsson T68i was the first phone available and we are starting to see more of these in user’s hands. Nokia have also started shipping their 7650 camera enabled MMS phone and another model is due soon. Many more models are expected.
Back to top
Does MMS need 3G?
Not at all, we're advising GPRS is the minimum although it works over circuit switched GSM it is costly to run. 3G will benefit capabilities such as streaming audio / video for example downloading full MP4 video clips may take too long over GPRS.
How big can an MMS message be?

There is not a network limit but initial devices are specifying minimum support for 30k - it's really a manufacturer limit concerning the amount of memory
How fast is an MMS message from phone to phone?
It could parallel an email message - might normally appear near instantaneous but could be delayed by load on servers and by who's sending from where to where or by network outages. It is not however designed to be real time.
back to top
How does MMS compare to EMS?
EMS is delivered via SMS and this means it can be very costly and is using limited control channel capacity in a GSM network. EMS also supports picture messaging/ animation but MMS is much more capable of serving up multiple media together and also you wouldn't enjoy the experience of more complex media e.g. photographs, sound and video.
How does MMS compare to email?
It has many similarities to rich email content but delivered in a mobile friendly way. In fact MMS uses email technologies to underpin the technical capabilities. Some aspects of MMS will exceed standard email capabilities e.g. true control over sequences which conventional email doesn't handle.
back to top
How is the MMS environment different from SMS?
MMS requires network operators to install MMS Server/ Relay equipment which integrates with existing infrastructure and connects to content providers, email gateways. SMS uses a control channel whereas MMS uses the data channel.
Is anyone setting standards for MMS?
The principle standards body is 3GPP for MMS though they use work by other standards bodies such as the WAP forum to assist in certain areas. The GSM association is active in collecting operator requirements to address to 3GPP to help advance these standards.
back to top
What is the connection between MMS and WAP?
MMS capability uses many services of WAP to make it work - particularly the lower level WAP transport mechanisms which are optimised for operation over the GSM radio interface. MMS also uses WAP's push mechanism to transparently notify users of receipt of a new message.
Does MMS require network changes?
It requires additions of infrastructure components to handle the store & forward functions of MMS. MMSCs have to connect into other network components like HLRs, a network must also be WAP capable and realistically GPRS capable. And for proper service GPRS global roaming is required.
back to top
How interoperable are MMS messages across manufacturers?
At a technical level the vendor community and operators have created an interoperability group to ensure maximum reliability in inter-working. Initially there may be differences between devices which will mean that there will be situations where an MMS composed on one device is not well rendered on another and this parallels a web page for a PC not looking good on a PDA.
Sending WAP Push Messages
Click here to return to the Now SMS/MMS Gateway Home Page

To send a WAP Push message via a menu driven interface, please see the help section titled “Web Menu Interface”. This section describes how to send a WAP Push programmatically via URL parameters.

WAP Push messages are specially formatted SMS messages that display an alert message to the user, and give the user the option of connecting directly to a particular URL via the mobile phone’s WAP browser.

For example, an e-mail application might send an alert that tells the user they have new e-mail, with a URL link to connect directly to a WAP e-mail application.

The WAP specifications define a format for applications to create XML-based “PAP” (Push Access Protocol) documents that can be posted to an operator’s “PPG” (Push Proxy Gateway), in order to deliver a WAP push message to a mobile device.

Unfortunately, the complexity of this format, and the reluctance of operators to open their “PPG” to just anyone, has made it difficult for developers to deploy “WAP Push” in their applications.

The Now SMS/MMS Gateway makes it easy to generate and deliver “WAP Push” messages. While the gateway does not support all of the options available via the PAP-based PPG interface, it does implement “WAP Push” in an elegantly simple solution.

To send a WAP Push message, use the following URL format:

http://127.0.0.1:8800/?PhoneNumber=xxxxxxxx&WAPURL=name.domain/path&Text=abc+def+ghi

For 127.0.0.1, please substitute the IP address or host name assigned to your gateway PC. (Note: 127.0.0.1 is a local loopback address that can be utilized when you are connecting to the gateway from the same computer.)

For 8800, please substitute the port number that the gateway is configured to use.

Substitute the phone number that you wish to send the SMS message to for the “xxxxxxxx” in the “PhoneNumber” parameter. Use either the local phone number format, or the international phone number format (your network provider may or may not allow you to send to international phone numbers). If the international phone number format is used, note that you must substitute “%2B” for the “+” character, because of URL escaping restrictions. For example, to send an SMS to +447778001210, use %2B447778001210 instead.

The alert text for the WAP Push message is contained in the “Text” parameter, and utilizes the same format as described in “Sending Text Messages”.

Note that there are two types of “WAP Push” messages, “Service Indication (SI)” and “Service Load (SL)”. The “SL” format can be selected by including “WAPSL=1” as a URL parameter, and does not support a “Text” parameter, while the “SI” format does. (By specification, the “SL” format was designed to tell the browser to connect to a URL without user intervention. However, for security reasons, mobile phones will always display a prompt before connecting to a URL. Therefore, the lack of a text parameter makes the “SL” format considerably less user-friendly than the “SI” format, and in practice, most users will exclusively use the “SI” format.)

The URL to be pushed to the mobile device is specified in the “WAPURL” parameter. Note that the “http://” portion of the URL is not necessary and is assumed. Also note that it may be necessary to escape some URL characters, please refer to the table in the “Sending Text Messages” section for common characters that must be escaped.

QUICK TEST PROFESSIONAL

2008-07-02T10:21:00.000-07:00

QUICK TEST PROFESSIONAL

QuickTest Professional enables you to test standard Windows applications, Web objects, ActiveX controls, and Visual Basic applications.QuickTest Professional facilitates creating tests and business components by recording operations as you perform them on your application.

Test—A collection of steps organized into one or more actions, which are used to verify that your application performs as expected.

Business Component—A collection of steps representing a single task in your application. Business components (also known as components) are combined into specific scenarios to build business process tests in Mercury Quality Center with Business Process Testing.

Testing process in QTP
The quick Testing process consist of 7 main phases:
Preparing to record
Recording a session
Enhancing Your Test
Debugging your test
Running your test
Analyzing the Test Results
Reporting Defects

The Test pane contains two tabs to view your test or component—the Keyword View and the Expert View.
Keyword View
The Keyword View enables you to create and view the steps of your test or component in a keyword-driven, modular, table format. Each step in your
test or component is a row in the Keyword View, comprised of individual parts which you can easily modify. You create and modify tests or
components by selecting items and operations in the Keyword View and entering information as required.
Expert View
In the Expert View, QuickTest displays each operation performed on your application in the form of a script, comprised of VBScript statements. The
Expert View is a script editor with many script editing capabilities. For each object and method in an Expert View statement, a corresponding row exists
in the Keyword View.

Active Screen
The Active Screen provides a snapshot of your application as it appeared when you performed a certain step during a recording session. Additionally,
depending on the Active Screen capture options that you used while recording, the page displayed in the Active Screen can contain detailed
property information about each object displayed on the page.
Recording a Test or Component
You create a test or component by recording the typical processes that users perform. QuickTest records the operations you perform, displays them as steps in the Keyword View, and generates them in a script.
Recording Mode:
Analog Recording:
This enables to record the exact mouse and keyboard operations performed in relation to either the screen or the application window.
Low level recording:
This mode records at the object level and records all the run time objects as window or winobject test objects. This mode can be used if the co ordinate of the objects are important for the test or component.
Synchronization Test:
We can insert a synchronization point which instructs the quick test to pause the test untill an object property achieves the value you specify. When doing this Quick test generates a wait property statement in the Expert view.
We can also insert Exist or wait statements that instructs Quick test to wait untill an object exists or to wait a specified ammount of time before continuing the test or component.
CheckPoints:
Quick test provides many checkpoints to check if the application or the website function properly. A Checkpoint is a verification point that compares a current value for a specified property with the expected value for that property.
Types of Checkpoint:
Standard Checkpoint - Checks values of an object’s properties.
Image Checkpoint - Checks the property values of an image
TableCheckpoint - Checks information in a table
Page checkpoint - Checks the characteristics of a Web page
Text /Text Area Checkpoint - Checks that a text string is displayed in the appropriate place in a Web page or application window
Bitmap Checkpoint - Checks an area of a Web page or application after capturing it as a bitmap
Database Checkpoint - Checks the contents of databases accessed by an application or Web site
Accessibility - Checkpoint Identifies areas of a Web site to check for Section 508 compliancy
XML Checkpoint - Checks the data content of XML documents
Data Driver:
Quick test enables to expand the scope of the basic test or component by replacing fixed values with parameters. This process, known as parameterization, greatly increases the power and flexibility of your test or component. A parameter is a variable that is assigned a value from an external data source or generator. When testing the applications, we may want to check how it performs the same operations with multiple sets of data. This can be done in Quick test by the Data Driver.
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, QuickTest uses a different value from the Data Table. When you parameterize a step in a test using the Data Table, you must decide whether you want to make it a global Data Table parameter or an action Data Table parameter.
Global Data Table parameters take data from the global sheet in the Data Table. The global sheet contains the data that replaces global parameters in each iteration of the test. By default, the test runs one iteration for each row in the global sheet of the Data Table.
Action Data Table parameters take data from the action’s sheet in the Data Table. The data in the action’s sheet replaces the action’s parameters in each iteration of the action. By default, actions run only one iteration.
Parameterizing the value of a checkpoint property enables you to check how an application or Web site performs the same operation based on different data.
Regular Expression Syntax
Regular expressions enable QuickTest to identify objects and text strings with varying values. You can use regular expressions when defining the properties of an object, the methods of an argument, when parameterizing a step, and when creating checkpoints with varying values. A regular expression is a string that specifies a complex search phrase. By using special characters such as a period (.), asterisk (*), caret (^), and brackets ([ ]), you define the conditions of the search.
Recovery Manager:
Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results. This is a problem particularly when running tests or components unattended—the test or component is suspended until you perform the operation needed to recover.
The Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario—a definition of an unexpected event and the operation(s) necessary to recover the run session.
A recovery scenario consists of the following:
Trigger Event—The event that interrupts your run session.
Recovery Operation(s)—The operation(s) that need to be performed in order to continue running the test or component.
Post-Recovery Test Run Option—The instructions on how QuickTest should proceed once the recovery operations have been performed, and from which point in the test or component QuickTest should continue, if at all.

QTP Frame Work

2008-07-02T10:13:00.000-07:00

QTP Frame Work

1.2 Approach for Test Automation

Description

Approach for Test Automation is used for building a strategy for automation starting from the Requirement phase till the deployment phase. Approach for automation begins with finding out the conditions and business rules given by the client and grouping similar conditions, business rules together as Test cases or Test Scenarios.

Steps involved in Approach for Test Automation are as follows:

 Requirement gathering from the client
 Understanding and Analyzing the Requirement
 Grouping the requirement into Test cases
 Preparing the Design for Automation
 Building Scripts depending on the Design
 Review of Scripts at Offshore
 Delivery to the Client

For example in the Unilever project:

Since it is Project for Automation of SAP, Team was divided into two,
SAP Consultants.
Testing Team.

Requirement gathering from the client included knowledge transfer at onsite, where all the transactions including the customized transactions where explained to the SAP Consultants of satyam, Under standing of requirements was done at the client side, Depending on the flow of transactions, all the transactions where grouped together as different scenarios. While SAP Consultants where onsite for gathering Requirements, Work done at the offshore was to analyze on the appropriate version of the QTP Tool to be used and to get licenses for QTP, user accounts for SAP access, Installation of QTP and SAP.

All the Identified Scenarios which consists of different transactions where explained to Testing Team. Then common functionalities where identified, and grouped together as different Test cases.

After defining different Test cases, design for automation of scripts was done, where Reusability was one of the main aspects, where all the transactions, which are common in the scenarios, are identified as Reusable transactions.

Automation Framework:

For Quality deliverables, important things that should be followed are:

 Following common coding structure for all the scripts
 Consistent coding conventions
 Use of Reusability for making code efficient and minimal
 Efficient use of Object Repository
 Use of Error and Exception handling Functions
 Use of Data table object, Environment variables for using data

For example in the Unilever project:

Coding Structure used is that there will a main Action for all the scripts which is named as corresponding Test case name, This Action intern will call all the other actions (Each Transaction used in the script would be an action) in the script. Importing and Exporting of sheets is also done in this main action. Importing of sheets is done at the beginning before calling other actions and exporting of sheets is done at the last. Sheets corresponding to all the actions in the scripts are imported, so that the data in the fields of the Imported sheets are used as input data to the script, output data from the script is also collected and exported to the corresponding sheet.

There are many transactions which are reused in the scripts, similar transactions (Actions) are made as reusable so that its not required to record those transactions again and again, which ever transaction was common among scripts, were recorded in one script and is reused in all the scripts where the transaction is required.

Error handling in the unilever automation is done by using Recovery Scenario where each Recovery scenario calls a function which handles the recovery by exiting all the other transactions (actions) when recovery fires. Major types of Recovery used in this project where Popup Window, Object state and on Error Recoveries. In Error handling using Recovery, all the common types of exceptions or errors are given common Recovery scenarios using regular expressions, which minimized the number of Recovery scenarios and Functions used.

Design for Structure of Scripts used in Unilever Project:

Main Action, which calls all the other Called Actions
Actions (transactions) in the script

Calls

Ex: S014_001 (Action Name) Ex: ME21N (Action Name
Which is same as the
Transaction name in
SAP)

Design of the Approach for Test Automation is given below

Design for Automation of Test cases for Unilever Foods:

It’s a description of Automating a test case belongs to SAP by explaining a scenario S014-081

Scenario Objective: Moving a Material from Raw Material Storage Location to a Production Storage Location, Creating a Transfer Requirement and a Transfer Order.
Note: The phase in blue color indicates where more efforts are required in analyzing and recording to generate a script.

QTP Framework in SAP Automation

Guidelines followed for identification of Test Cases for Automation

 Tests that need to run once and those that need frequent human intervention are usually not worth the investment to automate and have not been considered for automation.
 As Automated testing can be used to verify the performance of application paths that are used with a high degree of frequency when the software is running in full production e.g. creating customer records, Invoicing and other high volume activities where software failure would occur frequently have been considered.

 Mission critical processes like core activities like sales order processing are prime candidates for automated testing and have been considered for automation.

 Repetitive Testing
 Applications with Long Life span – Longer the application in production greater the benefits from automation.
 Avoiding dynamic screens. Though possible to automate this increases the complexity of the script.
 Avoiding screens where objects are created dynamically
 Avoiding business scenarios where complex hardware is involved
 Selecting a row in a table results in an additional challenge from. Some automation tools provide the facility to read each row in a table and for focusing on a specific row. If the numbers of rows were very high the execution time of the script would be high. This leads to performance issues of the recorded script. Hence, it is better to prove the business scenario wherein tables with row selections figure by identifying a fixed row number. This scenario is faced very frequently in enterprise applications as in pricing tables and leads to the complexity of the script and subsequently the effort.
 Avoiding scenarios that require high degree of coding while automating so that script’s complexity is reduced and high maintainability of the script is ensured.

2. Introduction to QTP

2.1 QTP Environment Compatibility
QTP (version) supports a wide range of working environments and thereby can be used for practically any application.

Core Environments Supported by QTP:

- Windows applications (MFC)
- Visual Basic
- Java
- ActiveX

Enterprise Applications:

- SAP
- Siebel
- PeopleSoft
- Oracle

Web Technologies:

- HTML
- DHTML
- JavaScript

Browsers:

- Internet Explorer
- Netscape
- AOL

Emerging Technologies:

- .NET winforms, webforms, web services
- J2EE Web services
- XML, WSDL, UDDI

Terminal Emulators:

- 3270
- 5250
- VT100

Server Technologies:

- Oracle
- Microsoft
- IBM
- BEA
- ODBC
- COM / COM+

Multimedia:

- Flash
- RealAudio / RealVideo
- Windows Media Player

Operating Environment

Operating Systems Supported:
Windows XP/2000/NT
Windows 95/98/ME
Databases Supported: (Not Applicable)
Networks Supported: TCP/IP
Programming Languages Supported: JavaScript
Java
HTML
Visual Basic (VB)
XML
Middleware Supported: Microsoft .NET

2.2 Versions of QTP

QTP 6.5:
To successfully install and run QTP6.5, following minimum system requirements are required :
Computer/Processor: IBM-PC or compatible with a Pentium® II 266 MHz microprocessor (366 MHz recommended).
Operating System: Windows® 98 Second Edition, Windows® 2000—Service Pack 3,
Windows NT® 4.0—Service Pack 6a,
Windows® Me, or Windows® XP—Service Pack 1.
Memory: 128 MB of RAM (256 MB recommended)
Free Hard Disk Space: 150 MB of free disk space for a compact installation or 200 MB for a typical or complete installation
Browser: Microsoft Internet Explorer 5.0–6.0.

Supported Environments
QuickTest Professional supports creating, recording, and running tests in the environments described below.
 Standard Windows Applications
1. Win32 API
2. MFC
 Visual Basic Applications
Visual Basic 6.0
 Browsers
 Microsoft Internet Explorer 5.01–6.0 (required)
 Netscape Navigator 4.06–4.7x (optional)
 Netscape 6.1, Netscape 6.22, and Netscape 6.23 (optional)
 AOL 5.0 and 6.0 (optional)

ActiveX Grid Controls
In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Grid controls:

Name ProgId
FarPoint Spreadsheet 2.5 FPSpread.Spread.1
FarPoint Spreadsheet 3.0 FPSpread.Spread.2
FarPoint Spreadsheet 3.5 FPSpread.Spread.3
FarPoint Spreadsheet 6.0 FPSpread.Spread.4
FarPoint Spreadsheet 3.0 (OLEDB) FPSpreadADO.fpSpread.2
FarPoint Spreadsheet 3.5 (OLEDB) FPSpreadADO.fpSpread.3
FarPoint Spreadsheet 6 (OLEDB) FPSpreadADO.fpSpread.4
Microsoft Grid 1.0 MSGrid.Grid
Microsoft DataBound Grid 5.0 MSDBGrid.DBGrid
Microsoft Flex Grid 6.0 MSFlexGridLib.MSFlexGrid.1
Sheridan Data Grid 2.0 SSDataWidgets.SSDBGridCtrlApt.1
Sheridan Data Grid 3.1 SSDataWidgets.SSDBGridCtrlApt.3
Apex True DataBound Grid 5.0 TrueDBGrid50.TDBGrid
Apex True DataBound Grid 6.0 TrueDBGrid60.TDBGrid
Apex True OLE DB Grid 6.0 TrueOleDBGrid60.TDBGrid

ActiveX Calendar Controls
In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Calendar controls:
Name ProgId
Microsoft Date and Time Picker Control 6.0 (SP4) MSComCtl2.DTPicker.2
Microsoft MonthView Control 6.0 (SP4) MSComCtl2.MonthView.2

Multimedia Applications
QTP6.5 supports testing on the following multimedia applications:
 Microsoft Windows MediaPlayer controls, version 6.0 and higher
 RealPlayer controls supported for Internet Explorer browsers (the controls within applications containing browser controls are not supported)
 Macromedia Flash 4 or 5 objects that are ActiveX controls in Internet Explorer. You can also test Macromedia Flash 6 clips containing only Flash 4 or 5 commands.
Additional Environments
QuickTest Professional add-ins support other environments such as Java, .NET Windows and Web Forms, SAP solutions, Oracle, Siebel, PeopleSoft, Web Services, and terminal emulator applications. For more information about QuickTest Professional add-ins, contact your sales representative or Mercury Interactive Customer Support.
Note for QuickTest Professional 6.0 and earlier:
Java support and Oracle support are now available as separate add-ins to QuickTest Professional 6.5 and are no longer part of the core product.

QTP 8.0:

System Requirements
To successfully install and run QTP8.0, you need the following minimum system requirements:
Computer/Processor: IBM-PC or compatible with a Pentium II 266 MHz microprocessor (366 MHz recommended).
Operating System: Windows 2000-Service Pack 3 or Service Pack 4, Windows XP-Service Pack 1, or Windows 2003 Server.
Memory: 128 MB of RAM (256 MB recommended).
Free Hard Disk Space: 250 MB of free disk space for application files and folders, and an additional 120 MB of free disk space on the system disk (the disk on which the operating system is installed).
After Quick Test Professional is installed, it is recommended to have at least 150 MB free disk space on the system disk for the operating system and Quick Test Professional to run correctly.
Browser: Microsoft Internet Explorer 5.5 Service Pack 2-6.0.

Supported Add-ins
The following external QuickTest 6.5.x add-ins are supported for use with QuickTest Professional 8.0:
 Java Add-in 6.5
 Oracle Add-in 6.5
 PeopleSoft Add-in 6.5
 Terminal Emulator Add-in 6.5
 .NET Add-in 6.5.1
 SAP solutions Add-in 6.5.1

Note: Siebel Add-in 6.5, the .NET Add-in 6.5, the Add-in for SAP solutions 6.5, or any 6.0 add-ins,cannot be used with QuickTest Professional 8.0.1
Supported Environments and Programs
QuickTest Professional 8.0 supports creating, recording, and running tests or components using the environments and programs described below.
 Standard Windows Applications
1.Win32 API
2.MFC
 Visual Basic Applications
Visual Basic 6.0
Note: Visual Basic .NET applications are supported by the QuickTest Professional .NET Add-in.
 Browsers
 Microsoft Internet Explorer 5.5 Service Pack 2-6.0 (required)
 Netscape 6.1, Netscape 6.22, Netscape 6.23, Netscape 7.02, and Netscape 7.1 (optional)
 AOL 8.0 and 9.0 (optional)

ActiveX Grid Controls
In addition to basic support of ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Grid controls:

Name ProgId
FarPoint Spreadsheet 2.5 FPSpread.Spread.1
FarPoint Spreadsheet 3.0 FPSpread.Spread.2
FarPoint Spreadsheet 3.5 FPSpread.Spread.3
FarPoint Spreadsheet 6.0 FPSpread.Spread.4
FarPoint Spreadsheet 3.0 (OLEDB) FPSpreadADO.fpSpread.2
FarPoint Spreadsheet 3.5 (OLEDB) FPSpreadADO.fpSpread.3
FarPoint Spreadsheet 6 (OLEDB) FPSpreadADO.fpSpread.4
Microsoft Grid 1.0 MSGrid.Grid
Microsoft DataBound Grid 5.0 MSDBGrid.DBGrid
Microsoft Flex Grid 6.0 MSFlexGridLib.MSFlexGrid.1
Sheridan Data Grid 2.0 SSDataWidgets.SSDBGridCtrlApt.1
Sheridan Data Grid 3.1 SSDataWidgets.SSDBGridCtrlApt.3
Apex True DataBound Grid 5.0 TrueDBGrid50.TDBGrid
Apex True DataBound Grid 6.0 TrueDBGrid60.TDBGrid
Apex True OLE DB Grid 6.0 TrueOleDBGrid60.TDBGrid

ActiveX Calendar Controls
In addition to built-in support for ActiveX properties and methods, QuickTest Professional supports context-sensitive recording and verification on the following ActiveX Calendar controls:
Name ProgId
Microsoft Date and Time Picker Control 6.0 (SP4) MSComCtl2.DTPicker.2
Microsoft MonthView Control 6.0 (SP4) MSComCtl2.MonthView.2

Microsoft Excel
When using Microsoft Excel files with QuickTest Professional 8.0(for example, to import or export data to or from the Data Table), you can work with Microsoft Excel 2000, 2002, 2003, and XP.

Microsoft Query
When using Microsoft Query with QuickTest Professional 8.0 (for example, for Database checkpoints), you can work with Microsoft Query 2000, 2002, 2003, and XP.

Additional Environments
QuickTest Professional add-ins support other environments such as Java, .NET Windows and Web Forms, SAP Solutions, Oracle, Siebel, PeopleSoft, Web Services, and terminal emulator applications. For more information on QuickTest Professional add-ins, contact your sales representative or Mercury Interactive Customer Support.

3. Add-Ins

3.1 Types of Add-Ins

QTP version Add-ins

8.2 Java add-in 6.5
Oracle add-in 6.5

Siebel add-in 8.0
Terminal Emulator add-in 8.0
. Net add-in 8.2

Default Add-Ins: Active X Controls, Web &Visual Basic

8.0 . Net add-in 6.5.1
Sap add-in 6.5.1
Java add-in 6.5
PeopleSoft add-in 6.5
Oracle add-in 6.5
Terminal Emulator add-in 6.5

Default Add-Ins: Active X Controls, Web &Visual Basic

6.5 . Net
Web
Java
XML
Default Add-Ins: Active X controls, Multimedia, Visual Basic, Web

Note: Quick Test Professional Siebel add-in 6.5 and Web services add-in 6.0 cannot be used with Quick Test 8.0.
 The add-ins for Quick Test Professional 6.0 cannot be used with Quick Test Professional 6.5. If you are using Quick Test Professional 6.5, you will need to get the 6.5 version of your add-in.

3.2 Conditions for Add-ins

3.2.1 Java Add-In

When testing Java applets in a Web browser, you must load the Web add-in as well as the Java Add-in, and use the Web tab of the Record and Run Settings
Dialog box to specify your record and run preferences. To test Java applets or applications running on Netscape 4.x’s built-in JVM (not Java Plug-ins), confirm that the Netscape 4.x browser is already installed before installing the Quick Test Professional Java Add-in. When testing Java applets in a Web browser web Add-in as well as java add-in must be loaded .To create a checkpoint, parameterize a step, or to add a method from individual java applets, the Java Add-in must be loaded.

3.2.2 .Net Add-In
The .Net add-in is required to support objects developed in .Net .In some cases, even though the application has been developed using .Net, when the page is sent to the browser, it is a plain HTML page. Quick Test Professional can recognize HTML controls like edit fields, buttons etc. without the .Net add-in. However, if a Web application contains complex controls like ActiveX or other controls developed in .Net like ASP.Net server controls, it is required to use the .Net add-in to achieve object recognition.
3.2.3 Sap Add-In
The Sap add-in is required for all SAP applications. In SAP application Grid Tables, Status Bar messages, Labels can be identified only if SAP Add-in is installed.

4. Conventions

The Conventions for Naming for test cases, Scripts and Actions vary from Project to Project depending upon the Client.

4.1 Test Case Naming Conventions:
Test cases should be named in a manner that enables easy identification of the corresponding Use case (or the Scenario) for which the Test Case is written. The Onlooker should be able to trace the test case back to the use cane name or Scenario name by the name of the Test Case. Consistency should be maintained in following the hierarchy of naming.

Use Case
Or Test Case
Scenario

For example:

Example 1: Considering that Each Use case is associated with one Test case. If the name of the Use Case were UC_001 then the Test case name would be TC_001.

Example 2: In the Unilever Automation Project, SAP transactions are divided into different modules, in those modules different transactions are grouped together as a scenario, so for writing the test case for a particular scenario naming convention used is module name followed by scenario name.

For Module IMWM, if S014_01 is the scenario name, so name of the test case for the S014_01 scenario was given as IMWM_S014_01.

4.2 Script and Action Naming Conventions:
Similar to the Test case naming, Script naming should be done consistently with clarity and traceability. Typically each Test Script is prepared corresponding to each Test Case. Every Test Case contains one or more Conditions. Each Condition can be represented by an action in the script.

Use Case

Test Case

Condition1 Condition2 Condition3 ………

Test Case Test script

Condition 1 Action1

Condition2 Action2

Therefore for a Test Script corresponding to a Test Case named TC_001 would be QTS_001.The hierarchy should be maintained in case the use cases or test cases are nested.

E.g.: TC_01_014 would have a QTP Test Script as QTS_01_014.

Action Naming:
Each Test Script can contain one or more Actions, with one or more actions representing a test Condition.
Actions can be named in 2 ways:
1. Functionality of the Action
2. Hierarchy of the Action in the Test Script.

1. Functionality of the Action:
Typically Actions are segregated by their functionality in the Test Script. Therefore it would be easier to understand the Action if the name of the action represents the Functionality.

For E.g.: An Action written or recorded for logging the user should be named as Login or Authentication for easy understandability.
An Action for booking tickets should be named as Book_Tickets
An Action for exiting the application named as Exit.

This also adds a huge advantage when the Actions are made reusable. Reusable Actions can be used between various scripts. When an Action is to be made reusable the action should be named as REUSE_(Action name).
Example: REUSE_Login.

2. Hierarchy of the Action in the Script:

Since Actions are a part of the Test Script, for purpose of Clarity and tracking, Actions can be named as per Hierarchy.

For e.g.: Test Case Name  TC_01
QTP Test Script Name  QTS_01
Name of 1st action in the Script  QTS_01_01
Similarly Name of 9th Action in the ScriptQTS_01_09

4.3 Variables and Constants:

QTP Scripts are in VB Script. Therefore, the naming conventions for variables can be followed alike VB Script Naming Conventions.

General Conventions followed in VBScript are:

Data Type Prefixes:

By using data type prefixes, your variables always indicate what they are designed for. I'm using just six prefixes:

Prefix Data Types Example
b Boolean (true or false) bChecked = True
d Date/time dStartTime = Now
i All numeric data types
(Byte, Integer, Currency, Long, Single, Double) iTax = iPrice * 0.076
o Objects Set oFile = Nothing
s Strings sTitle = "Welcome!"
u User interface elements uPara.style.display = "block"

Constants Prefix:

Usually there are only a handful of constants in any scripts. Indicating the data type therefore is less important for constants. Prefix letter c for all constants can be used.
e.g. Const cTitle = "Welcome!"
UDocument.title = cTitle

4.4 DataSheet Naming and Parameter Naming Conventions:

Every QTP Test Script contains 2 types of sheets.
1. Global data sheet
2. Local data sheets

The Global data sheet, which is a common sheet for all the actions of the script, is named by default as dt_globalsheet. This can be renamed as Global for all the Scripts for consistency.

Typically, Each Action in the Script contains one data sheet, which is local to the Action. This is by default, named after the Action to which it belongs. Therefore the name of the datasheet follows directly the name of the Action, which when named following its naming conventions, can be used efficiently for the data sheet too.

Parameter Naming:

Various Types of Parameters used in QTP are:

1) Test Parameters

a) Test Input Parameters: These should be named as IN_(relevant variable name). ‘In’ denoting that it’s an input parameter for the Test in whole. The name following IN should be a relevant name for the variable, denoting the purpose of its use. This should also comply with the standard variable naming conventions.
Example: IN_bFlag, IN_iIncrement etc.,

b) Test Output Parameters: On the similar lines of Input Parameters, these should be named as OUT_(relevant variable name). OUT representing that it’s an output parameter.
Example: OUT_sStatus.

2) Action Parameters

a) Action Input Parameters: These are local to Action of a Test. These can be named as ACTIN_(variable name). ACTIN denoting that it’s an Action Input Parameter.
Example: ACTIN_iResult

b) Action Output Parameters: These could be named as ACTOUT_(var name).
Example: ACTOUT_bFlag

3) Environment Variables:

Environment variables are either built-in or User defined. Built-in variables cannot be declared named by the user, so their naming convention is not discussed.

User Defined Environment Variables are either Internal or External.
Internal Variables: ENV_INT_(variable name)
External Variables: ENV_EXT_(Variable name)

4.5 Function Naming Conventions

Functions should be named as Func_(name). This can provide clarity and difference between a Reusable Action and a Function that can be used within Actions.
Example: Func_Save , Func_Add

5. Settings
5.1 QTP Test Settings
Before Running or Recording any test on QTP, the QTP Test settings need to be set as per the requirements of the Test. Setting these Test Settings before starting a Test plays a crucial part in the behavior of the test.

These can be found at the path Test>Settings. A dialog box pops up, in which various tabs are present which allow one to set
 Properties of the test like Add-Ins used
 Run time Preferences
 Resources like files, data tables, and repository to be used.
 Parameters required in the Test.
 Environment variables used
 Web navigation
 Recovery Scenarios

Note: For further details about the use of each tab, refer to QTP Test Settings

5.2 Record and Run Settings
After Setting the Test Settings at Test>Settings, the next important settings for actually recording the application and running it for Testing are to be set at the Test>Record and Run Settings. This dialog box opens automatically, when recording a test for the first time. The details of which application to record are set in this dialog box.

For further details about these settings refer to Record and Run Settings.

5.3 Active Screen Capture Level
One of the most useful fetaures of QTP is the various views it provides, out of which Active view is the most unique.The selection of the appropriate Active Screen Capture level influences the storage space, properties stored and the view of the Active screen. The selection can be made by going to Tools>Options>Active Screen.
The Active screen settings can also set at the Test>Record and Run Settings.
The active screen capture level can be set to any of the 4 levels i.e. Complete, Partial, Minimum and None.

For details about each capture level, refer to ActiveScreen Capture Level.

5.4 Object Repository
When a test is recorded, QTP adds each object on which an operation is performed, to the Tools>object repository. Objects can be added to the repository while editing the tests too.While recording, Objects are added to the repository in either of the two ways:
a. Object Repository per Action
b. Shared Object Repository.

The settings can be changed by going to
Test>Settings>Resources>Object Repository Type

In the Per-Action mode, objects are identified and separated on the basis of each action and the corresponding object repository for the test is created in the test folder.In the Shared mode, the user may choose a location to save the shared object repository files for all the tests.
All the Objects recorded during a test,and their properties can be seen and manipulated in the Tools>Object Repository.There are provisions in this Object Repository Dialog box to add new objects,spy objects, find and replace property values etc.

The First Section of Object Repository Dialog Box contains provisions to
a. Add Objects : A Button to add new objects to the repository.
b. Highlight: To highlight the object selected in the repository, when the application
is open.
c. Object Spy: To Spy any Object, to see its Properties.
d. Export: To Export any objects to an outside location.

The second section of the dialog box contains provision to Find, Replace, Add, and Remove the properties of an object in the Repository also set any default values for the properties.

5.5 Expert View

While recording Tests in QTP, there are 3 important views that enable us to understand clearly, the various representations of the Script. They are
a. Expert View
b. Keyword View: Hierarchical Representation of Actions
c. Active Screen View: Pictorial view of the currently active Screen.

In the Expert View, QTP displays each operation performed on the application in the form of a script. The script is comprised of VBScript statements and the view is a script
editor with many script editing capabilities. For each object and method in an Expert View statement, a corresponding row exists in the Keyword View and a corresponding Active Screen in the Active Screen view, which enables easy traceability.

Fig: Active Screen Component corresponding to Expert View Statement

Fig: Keyword view and Active Screen view corresponding to one expert view statement

5.5.1 Step Generator:

If the user is familiar with VBScript, the user can add and update statements and enhance the tests and components with programming. After the test or an Action is recorded, its power and flexibility can be increased by adding recordable and non-recordable VBScript statements as required for tasks like Check Points,Datatables etc.,.These additional steps can be added either manually or using Insert>Step >Step Generator .whenever a step is added to a script, then any Syntax errors of the step can be Identified in its Keyword view.

The Step Generator enables you to add steps quickly and easily, by selecting from a range of context-sensitive options and entering the required values.The generated step gets added at the position of cursor in the expert view.
The Step Generator enables you to add steps quickly and easily, by selecting from a range of context-sensitive options and entering the required values. In the Step Generator dialog box you can define steps that use:
 test object methods and properties
 utility object methods and properties
 calls to library functions, VBScript functions, and internal script functions

5.6 Setting related to the Application Used:
The different kind of Applications that can be tested using QTP are windows applications,web based(java and .Net),SAP,Oracle etc.Apart from the windows applications using MFC and simple web applications(which can be run with default add-ins), rest all applications require a special Add-in to be purchased to do the testing.Each

Add-in which is bought and installed, results in a new tab in all the setting dialog boxes , using which various setting options can be chosen.It purely depends on the type of application , how to choose a particular setting option.
Example of a SAP Add-in :

Fig: The Add-in manager dialog with SAP add-in

Fig: Record and Run Settings with a SAP Add-in.
For detailed information of the settings of the tabs other than the special tabs refer Record and run settings.

6. Objects

6.1 Objects
Objects are the things which contains different properties and methods.

For Example: Window is said to be an object which consists of properties such as Exist, GetROProperty and methods such as ChildObjects, Activate, maximize, minimize etc.

Property:

Property describes about the object defined, each object has different properties, which is necessary to describe the object, which differentiates the given object with other objects.

For example: If we take a window object, we first have to define to which class it belongs to which is one of the property, it belongs to a window class. Exist is a property which is common to many objects which returns true if that object exists.

Methods:

Methods are functions, which are used for changing the properties of the object that is in order to manipulate with the object properties we use.

For example: If we take a window object, Activate is a method used to activate the window object, thus by using Activate method Activate property of the present window object is set to true, thus the window object will be activated if not in activated mode.

Sample for Object hierarchy:

In the above sample of code, there are two main Objects, one is Dialog and the other is Window object. This objects contain child objects, For Dialog object which is named as “Login” has WinEdit object with name as “Agent Name:” as childobject, here Set is the method used to set a text into the WinEdit object.

“Set” is the method associated with “WinEdit” object

7. Data Table

In QTP scripting there are many objects that are used, One of the Objects used in QTP scripting is DataTable Object.

7.1 Datatable Object and related Functions:
Description

Basic use of Datatable object is to create an object for adding, deleting, updating data of an excel sheet used.

Main functions of the datatable object:

 Importsheet : This function is used to Import sheet into the script, so that all the data in the imported sheet can be used in the script.

Syntax:

Datatable.Importsheet(“nameofExcelfilewithpath”,
“nameofthesourcesheet”, “nameofthedestinationsheet”)

 Exportsheet : This function is used to Export sheet from the script, all the data including output values are stored in the default sheet for the action, this sheet is exported and stored in a specified location using this function.

Syntax:

Datatable.Exportsheet(“nameofExcelfilewithpath”,
“Nameofthesheet”)

 Addsheet : Used for adding a sheet into the script file.

 GetRowCount: This function is used to get the no of rows in a particular sheet.

Syntax:

Datatable.AddSheet(“Sheetname”).GetRowCount

 GetCurrentRow: This function is used to get the current row of a particular sheet.

When an action is run by using run setting as “run on all rows”, that action will run as many times as the number of rows in the excel sheet of the action, in order to find the row for which action is running currently we use GetCurrentRow function.

Syntax:

Datatable.GetSheet(“Sheetname”).GetCurrentRow

7.2 Organizing Data Sheets for Global & Local variables

Description

There are two types of sheets in any QTP Script, they are

Globalsheet
Localsheet

Globalsheet: Globalsheet in any script is unique, Globalsheet is used in order to store values in the sheet and the values stored in Globalsheet can be used in all the actions.

For storing a value in the global sheet we use the following function:

Datatable.Value(“Fieldname”,”Global”) = Value

For using the values from the global sheet we use the following function:

Value = Datatable.Value(“Fieldname”,”Global”)

Localsheet: Each and every action in the script will have its own Localsheet, name of the Localsheet of a particular action is same as the action name.

For using the data from the Local sheet we use following function:

Datatable.Value(“Fieldname”,dtlocalsheet)
Or
Datatable.Value(“Fieldname”,”Sheetname”)

Organization of Global and Local sheets with the actions used in the script are shown below:

7.3 Parameterizing using Data driven Wizard
Description
The Data Driver enables you to quickly parameterize several (or all) property values for test objects, checkpoints, and/or method arguments containing the same constant value within a given action.
You can choose to replace all occurrences of a selected constant value with a parameter, in the same way that you can use a Find and Replace All operation instead of a step-by-step Find and Replace process. QuickTest can also show you each occurrence of the constant so that you can decide whether or not to parameterize the value.
If any property of an object is taken, that property can be parameterized using Data driven Wizard,

Different steps for parameterization using Data driven Wizard is as follows:

 Go to tool bar option Tools and select Data Driver option
 We will get a list of all the properties of all the objects which can be parameterized (i.e. for all the objects where a value for a property is given in the script)

For example consider script for entering Login name which is as follows
Dialog("Login").WinEdit("Agent Name:").Set "name"
The Set property of WinEdit Object appears in the list of Datadriver with “name” as Value representing the Set property of “Agent Name” Editbox, which is as given below:

 Select a value which should be parameterized and click on “Parameterize” button.
 There will be two options to be selected as given below:

Step-by-step Parameterization: Enables you to view the current values of each step containing the selected value. For each step, you can choose whether or not to parameterize the value, and if so, which parameterization options you want to use, the Next button is enabled when you select this option, this will enable us to select an other instance of the constant selected and parameterize that instant, it will continue the same process till all the instances of the given value are done.

Parameterize all: Enables you to parameterize all occurrences of the selected value throughout the action.
When you select this option the Parameter details area is enabled. The Finish button is enabled when you select this option.

Here Parameter tab can be selected using the button given at the “Parameter” radio button, and in the next screen select the datatable Field from where the property for which the value belongs is parametererized, click on “Finish” button thus all the instances of the value selected for parameterization will be parameterized.

7.4 Importing and Exporting Datasheets:
Description

Importing and Exporting of Datasheets are used for reading, writing and manipulating the data in an excel sheet.

Importing Datasheet:
Description
Imports a sheet of a specified file to a specified sheet in the run-time Data Table. The data in the imported sheet replaces the data in the destination sheet (see SheetDest argument).

Note: All the fields in the imported sheets should match with the data used in the script.
There are two functions for Importing, Importing the whole excel file and Importing the sheets in the file.

Function for Importing the whole Excel file:

Imports the file into the script with all the sheets which are there in the excel file.

Note: Sheets in the excel file should match with the Actions in the script to use the data efficiently, since action name and corresponding sheet name should be same.

Syntax:

Import “filenamewithpath”

Function for Importing the sheets from the excel file:

Imports the specified sheet into the script.

Syntax:

Importsheet “filenamewithpath”,”sourcesheetname”,
”destinationsheetname”

Exporting Datasheet:
Description
Exports a specified sheet of the run-time Data Table to the specified file.
 If the specified file does not exist, a new file is created and the specified sheet is saved.
 If the current file exists, but the file does not contain a sheet with the specified sheet name, the sheet is inserted as the last sheet of the file.
 If the current file exists and the file contains the specified sheet, the exported sheet overwrites the existing sheet.
Same as Importing, There are two functions for Exporting, Exporting the whole excel file and Exporting the sheets in the file.

Function for Exporting the whole Excel file:

Exports the file into the script with all the sheets which are there in the excel file.

Syntax:

Export “filenamewithpath”

Function for Exporting the sheets from the excel file:

Exports the specified sheet into the script.

Syntax:

Exportsheet “filenamewithpath”,”sourcesheetname”,
”destinationsheetname”

8. Actions

8.1 Actions Settings
You can use the Run tab of the Action Call Properties dialog box to instruct QuickTest to run only one iteration on the called action, to run iterations on all rows in the Data Table, or to run iterations only for certain rows in the Data Table.

8.2 Iterations using rows
The Run tab includes the following options:
Option Description
Run one iteration only Runs the called action only once, using the row in the action's data sheet that corresponds to the current global iteration number. If the action's data sheet contains fewer rows than the global sheet, the last row of the action's data sheet is used for each subsequent test iteration.

For example, suppose an action's data sheet has two rows and the global sheet has four rows. If you choose to run one iteration only for the action and you choose to run iterations on all rows of the global data sheet, then during each iteration of the test, this action will run only one iteration. The data that the action parameters use during each repetition of the test are based on the iteration number for the test.
During the first iteration of the test, Data Table parameters in the action take data from the first row of the action's data sheet. In the second iteration of the test, Data Table parameters in the action take data from the second row of the action's data sheet. In the third and subsequent iterations of the test, the Data Table parameters in the action continue to take data from the second i.e. the last row of the action's data sheet.
Run on all rows Runs the called action with the number of iterations according to the number of rows in the action's Data Table.
Run from row __ to row __ Runs the called action with the number of iterations according to the specified row range.

The Run tab of the Action Call Properties dialog box applies to individual action calls and refers to the rows in the action's data sheet.

8.3 Action Template
Creating an Action Template

If you want to include one or more statements in every new action in your test, you can create an action template. For example, if you always enter your name as the author of an action, you can add this comment line to your action template. An action template applies only to actions created on your computer.
To create an action template:
1. Create a text file containing the comments, function calls, and other statements that you want to include in your action template. The text file must be in the structure and format used in the Expert View.
2. Save the text file as ActionTemplate.mst in your \dat folder. All new actions you create contain the script lines from the action template.
Only the file name ActionTemplate.mst is recognized as an action template.
To view the Action template refer to

8.4 Script Startup
 Check for the required add-ins for an application.
 Include action template for every test containing script id, Action name, Action Description, Recovery scenario used etc.
 Every action, scenario must be specified with an appropriate name.
 Check for mandatory input fields for all iterations in the datasheets that are being imported.

Example:
The Resources tab of the Test Settings dialog box can be used to associate specific files with the test, such as Data Table files.

The option area Other location instructs Quick Test to use data stored in the specified Data Table location. The Data Table can be any Microsoft Excel (.xls) file.

For a sample external file refer to Sample External File

 Check for the “Data table iterations” under the test settings for which the test has to be run.

For further details refer to QTP test settings doc.

8.5 Splitting Actions, Re-usable Actions, Internal/External Actions
Actions help divide your test into logical units, specific activities that you perform in your application.

A test is made up of calls to actions. When you create a new test, it contains a call to a single action or create tests that call multiple actions by inserting calls to them, to make the design more modular and efficient tests.
There are three kinds of actions:
 reusable action—an action that can be called multiple times by the test with which is stored in the local test as well as by other tests.
 external action—a reusable action stored with another test. External actions are read-only in the calling test. They can be modified only in the test with which they are stored.
 Non-resuable-actions —an action that can be called only in the test with which it is stored, and can be called only once.

For further details on creation & splitting of actions refer to Actions.

9. Object Repository

9.1 Per Action/Shared Object Repository:
Setting the Shared /per action Object Repository option
To set only one test to use the Shared Object Repository option:
1. Click the "New" button or go to File -> New to open a new test.
2. Go to Test -> Settings.
3. Select the Resources tab.
4. In the Object repository type box, select one of the options:

 Select "Per-action" to set the Object Repository mode for your test to the Object Repository per action mode.
Below are some of the factors based on which Per Action option is selected
 Whenever there are no common objects across transactions
 Ease of building object repository.
 Loading of per Action object repository takes less time as the size is less
 Select "Shared" to set the Object Repository mode for your test to the Shared Object Repository mode.
Below are some of the factors based on which Shared Action option is selected
 Whenever there are common objects across transactions
 Maintenance of object repository is very easy
 Whenever size of object repository is 1MB
5. If you selected Shared in step 4, specify the Shared Object Repository file you want to use as the test's Object Repository file. To specify a file, enter the Object Repository file name or click the "Browse" button and select a resource file (*.tsr) from the Open dialog box. To create a new Shared Object Repository file, enter a new file name in the Shared box.

Note: These steps need to be done in a new script. Once you have modified the script, you will not be able to change the option.

To set all new scripts to use a Shared Object Repository:

For Quick Test Professional 6.5 and above
1. Click the New button or go to File -> New to open a new test.
2. Go to Test -> Settings.
3. Select the Resources tab.
4. Select the Shared option for the "Object-repository type".
5. Specify the Shared Object Repository file you want to use as the test's Object Repository file. To specify a file, enter the Object Repository file name or click the ellipse button <...> and select a resource file (*.tsr) from the Open dialog box. To create a new Shared Object Repository file, enter a new file name and path in the Shared box.
6. Click the "Set as Default" button.
7. Click and .

9.2 Merging of two object repositories:
General:
The Object Repository File Merge Utility allows users to merge object repository files into a single file. This utility is intended for an advanced user that builds powerful tests.
The Merge Utility allows you to merge the content of one Object Repository to another one thus giving you the flexibility and the power in controlling the content of the Object Repository and the ability to dynamically change this content.
Conflicts:
The implementation of the merge algorithm is quite simple when the object repository files have different objects in them, or if all objects had only exact replicas in other files. Due to the nature of the operation it is often not the case. For example, if we try to merge two object repositories from tests that were recorded at different time points, between which some test objects properties have changed (e.g. whether a button is enabled) then the same object exists in the two repositories with different properties. We call this a description conflict as the two objects have the same name, but different descriptive properties. It can also be that the user has decided to modify the automatically assigned logical name of an object (for example, in order to create a shorter name) in one repository but not in the other. In this case, two objects will exist with different logical names, but with the same descriptive properties. We call this a name conflict.
Resolving Conflicts:
It is not trivial to identify and handle conflicting objects. The user might want to merge two objects that were not initially the same, or decide to keep two objects that for the inexperienced eye would seem identical. For example, recording on web browsers would likely generate identical logical names for browsers that have nothing in common. It is also likely that if the text on a button has changed, new tests would record a new logical name for it, even though the object behavior has not changed. It is therefore possible to either keep the two objects (and their subtrees) separated, to assume that the two objects are actually the same object, or to ignore one of the conflicting object. We will discuss these choices later in detail.
Note: The Merge Utility works only on machines where QTP8.0 is installed.

Merge Object Repositories Utility
Main Window:
This utility is designed to supply simple access to the functionality implemented by the ObjectRepositoryMgr COM component. As the operation is not trivial, the UI has many options to select, so we will discuss the different options in detail.

For different options of Merging refer to Merging of Object Repositories.

9.3 Limitations:
1. Mercury Interactive recommends that you keep the Object Repository under 1 MB and perform regular backups. If the size crosses more than 1MB loading of object repository takes lot of time .
2. The limitation on the number of Actions is 255. The reason is that each Action has a data table sheet. The Formula 1 control has a limitation of 255 sheets so the limitation is

255 Actions per test. You may be able to add additional Actions after reaching the 255 "limit", however those Actions will not be able to access a local data sheet.
Note: If you are calling reusable Actions, you may be able to have more than 255 Actions within the script. This can be accomplished if you are calling the same Action more than one time within the script. The data sheet for the Action will only be loaded once. This applies to "call to" Actions only.
Example:
In a new script, insert a "call to" a reusable Action. When the Action is added to the script, you will see the data sheet added to the data table. Insert another "call to" to the same Action. The data sheet will not be added again.

10. Variables

In QTP scripting there are mainly 3 types of variable that we use. They are:
 Action Parameters.
 Environment Variables.
 VB Variables, which we declare in the script.

10.1 Action Parameters
Action parameters enable you to transfer values between actions and their nested actions in your test, from your test to a top-level action, or from a step in a top-level action back to the script or action that ran (called) your test. For example, you can output a value from a step in a nested action and store it in an output action parameter, and then use that value as input in a later step in the calling parent action.
You define the parameters that an action can receive and the output values that it can return in the Parameters tab of the Action Properties dialog box. You specify the actual values that are provided to these parameters and the locations in which the output values are stored in the Parameter Values tab in the Action Call Properties dialog box.

You can specify input parameters for an action so it can receive input values from elsewhere in the test. Input values for an action can be retrieved from the test (for a top-level action) or from the parameters of the action that calls it (for a nested action). You can also specify output parameters for an action, so that it can output values for use later in the test, or pass values back to the application that ran (called) the test.

Setting Action Parameters

You can specify input parameters for an action so that steps in the action can use values supplied from elsewhere in the test. Input values for an action parameter can be retrieved from the test (for a top-level action) or from the parameters of the action that calls it (for a nested action). You can specify output parameters for an action, so that it can return values for use later in the test. For each input or output action parameter, you define a name and a type. You can also specify a default value for each action input parameter, or you can use the default value that QuickTest provides for the parameter value type that you choose. The default value is saved with the action and is used by the action if a value is not defined for a parameter in the action call. You can define, modify, and delete input and output parameters in the Parameters tab of the Action Properties dialog box.

To add a new input or output action parameter:
1. Click the Add button next to the Input parameters or Output parameters lists to add a new parameter to the appropriate list. A row for the new parameter is added to the relevant list.
2. Click in the Name box and enter a name for the parameter.
3. Select the value type for the parameter in the Type box. You can select one of the following types:
o String—A character string enclosed within a pair of quotation marks, for example, "New York". If you enter a value and do not include the quotation marks, QuickTest adds them automatically when the value is inserted in the script during the test run. The default value is an empty string.
o Boolean—A true or false value. If you select a Boolean value type, you can click in the Default Value column and click the arrow to select a True or False value. The default value is True.
o Date—A date string, for example, 3/2/2005. If you select a Date value type, you can click in the Default Value column and click the arrow to open a calendar from which you can select a date. The default value is today's date.

o Number—Any positive or negative number. The default value is 0.
o Password—An encrypted password value. If you select a Password value type, the password characters are masked when you enter the password in the Default Value field. The default value is an empty string.
o Any—A variant value type, which accepts any of the above value types. Note that if you select the Any value type, you must specify the value in the format that is required in the location where you intend to use the value. For example, if you intend to use the value later as a string, you must enclose it in quotation marks. When you specify a value of Any type, QuickTest checks whether it is a number. If the value is not a number, QuickTest automatically encloses it in quotation marks. If you are editing an existing value, QuickTest automatically encloses it in quotation marks if the previous value had quotation marks. The default value is an empty string.
4. If you are defining an input action parameter, click in the Default Value box and enter a default value for the parameter or you can leave the default value provided by QuickTest for the parameter value type. The default value is required so that you can run the action without receiving parameter values from elsewhere in the test.
5. If you wish, click in the Description box, then enter a description of the parameter, for example, the purpose of the parameter in the action.
To modify an existing action parameter:
1. Select the parameter you want to modify from the Input parameters or Output parameters list.
2. Modify the values as necessary in the edit boxes of the parameter row.
To delete an existing action parameter:
1. Select the parameter you want to delete from the Input parameters or Output parameters list.
2. Click the Delete button . The parameter is removed from the list.

10.2 Test Parameters
In the Parameters tab of Test Settings, you can define input parameters that pass values into your test or component and output parameters that pass values from your test or

component to external sources. You can also use the Parameters tab to modify or delete existing test or component parameters

The Parameters tab contains two parameter lists:
 Input parameters—Specifies the parameters that receive values from sources that are external to the test or component.
 Output parameters—Specifies the parameters that pass values to sources that are external to the test or component.

You can edit an existing parameter by selecting it in the appropriate list and modifying its details.
You can add and delete input and output parameters for your test or component using the parameter control buttons:

Option Description
Adds a parameter to the appropriate parameter list. Enter a name for the new parameter and select the parameter type. You can enter a description for the parameter, for example, the purpose of the parameter in the component. If you are defining an input parameter, enter a default value for the parameter in the Default Value column.
You define test or component parameters in the same way you define action parameters.
Removes the selected parameter from the test or component.
Defining Values for Input Parameters
When the test or component runs, QuickTest uses the default value for each defined input parameter if a specific value has not been defined for the parameter in either QuickTest or Quality Center.
When you run a test or business component from QuickTest, input parameter values for tests and components are taken from in the Input Parameters tab of the Run dialog box.
Using Test or Component Parameters
Once you have defined test or component parameters, you insert them in your test or component by specifying the test or component parameter name with the Parameter reserved object, in the format: Parameter("ParameterName").

10.3 Environment Variables
QuickTest can insert a value from the Environment variable list, which is a list of variables and corresponding values that can be accessed from your test. Throughout the test run, the value of an environment variable remains the same, regardless of the number of iterations, unless you change the value of the variable programmatically in your script.
There are three types of environment variables:
 User-Defined Internal—variables that you define within the test. These variables are saved with the test and are accessible only within the test in which they were defined.

You can create or modify internal, user-defined environment variables for your test in the Environment tab of the Test Settings dialog box or in the Parameter Options dialog box.
Tip: You can also create environment output values, which retrieve values during the test run and output them to internal environment variable parameters for use in your test.
 User-Defined External—variables that you predefine in the active external environment variables file. You can create as many files as you want and select an appropriate file for each test, or change files for each test run. Note that external environment variable values are designated as read-only within the test.

 Built-in—variables that represent information about the test and the computer on which the test is run, such as Test path and Operating system. These variables are accessible from all tests, and are designated as read-only.
Note: QuickTest also has a set of predefined environment variables that you can use to set the values of the Record and Run Settings dialog options. You should not use the names of these variables for any other purpose.

10.4 Variable passing from one Action to another
QuickTest enables you to retrieve values in your test or component and to store them as output values. You can subsequently retrieve these values and use them as input at a different stage in the run session. You can pass variables from one action to another by setting Action Call Parameter Values. You use the Parameter Values tab of the Action Call Properties dialog box to specify the values of input action parameters used by the called action and to specify the locations in which you want to store output action parameter values. You can also parameterize the value used for a particular input action parameter using any available parameter type.

The actual input and output action parameters that an action can receive or return, and their types, are defined in the Action Properties dialog box. If you do not set a value for an input action parameter in the Action Call Properties dialog box, the default value that is specified in the Action Properties dialog box is used.

You can specify a location in which to store the output action parameter values, which can be used in the called action.

To specify a location in which to store an output action parameter value:
1. In the Output parameters area, click in the Store In box for the parameter and enter a variable name.

If we choose variable to store the value, then the value is stored in a run-time variable for the duration of the run session. You can accept the default name assigned to the variable or enter a different variable name.
Alternatively, you can click the output storage button in the Store In box to open the Storage Location Options dialog box in which you can specify a location for storing the output value. You can select to store the value in a test or action parameter, a Data Table parameter, or an environment parameter.
2. Repeat this procedure for each output action parameter value in the list.

10.5 Scope of Variables
Mainly there are two types of variables: action parameters and environment variables.
An action's parameters are stored with the action and are the same for all calls to that action. If you change the action parameters defined for an action, and then view the action properties for a call to that same action in a different part of the test, you can see the action parameters have changed. However, the actual values specified for input action parameters and the locations specified for action output parameters can be different for each call to the action. When you insert a call to a copy of an action, the copy of the action is inserted with the action parameters and action call parameter values that were defined for the action you copied. When you split an action, the action parameters are copied to both actions. The action call values for the second action are taken from the default values of that action's parameters.
Environment variables can be accessed from your test. Throughout the test run, the value of an environment variable remains the same, regardless of the number of iterations, unless you change the value of the variable programmatically in your script.
There are three types of environment variables:
 User-Defined Internal—variables that you define within the test. These variables are saved with the test and are accessible only within the test in which they were defined.
You can create or modify internal, user-defined environment variables for your test in the Environment tab of the Test Settings dialog box or in the Parameter Options dialog box.
 User-Defined External—variables that you predefine in the active external environment variables file. You can create as many files as you want and select an appropriate file for each test, or change files for each test run. Note that external environment variable values are designated as read-only within the test.

 Built-in—variables that represent information about the test and the computer on which the test is run, such as Test path and Operating system. These variables are accessible from all tests, and are designated as read-only.

11. Check Points

A checkpoint is a verification point that compares a current value for a specified property with the expected value for that property.

11.1 Types of Checkpoints
In QTP the following types of checkpoints can be inserted to check various objects in a Web site or application.
 Standard Checkpoint checks the property value of an object in your application or Web page. The standard checkpoint checks a variety of objects such as buttons, radio buttons, combo boxes, lists, etc. For example, you can check that a radio button is activated after it is selected or you can check the value of an edit field.
Note: Standard checkpoints are supported for all add-in environments
 Image Checkpoint checks the value of an image in the application or Web page. For example, we can check that a selected image's source file is correct.
Note: Image checkpoint can be created by inserting a standard checkpoint on an image object.
Image checkpoints are supported only for the Web environment
 Bitmap Checkpoint checks an area of a Web page or an application as a bitmap. For example, consider a Web site that can display a map of a city the user specifies. The map has control keys for zooming. We can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, we can check that the map zooms in correctly.
Note: Bitmap checkpoints are supported for all add-in environments
 Table Checkpoint checks information within a table. For example, suppose an application or Web site contains a table listing all available flights from New York to San Francisco. You can add a table checkpoint to check that the time of the first flight in the table is correct.

Note: You create a table checkpoint by inserting a standard checkpoint on a table object.
Table checkpoints are supported for Web and ActiveX environments & for many other external add-in environments.
 Text Checkpoint checks that a text string is displayed in the appropriate place in the application or a Web page. For example, consider an application or Web page that displays the sentence Flight departing from New York to San Francisco. We can create a text checkpoint that checks that the words "New York" are displayed between "Flight departing from" and "to San Francisco".
Text checkpoints are supported for all add-in environments
 Text Area Checkpoint checks that a text string is displayed within a defined area in a Windows application, according to specified criteria. For example, suppose your Visual Basic application has a button that says View Doc , where is replaced by the four digit code entered in a form elsewhere in the application. You can create a text area checkpoint to confirm that the number displayed on the button is the same as the number entered in the form.
Text area checkpoints are supported for Standard Windows, Visual Basic, and ActiveX add-in environments Text area checkpoints are also supported for some external add-in environments.
 Accessibility Checkpoint identifies areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For example, guideline 1.1 of the W3C Web Content Accessibility Guidelines requires you to provide a text equivalent for every non-text element. You can add an Alt property check to check whether objects that require the Alt property under this guideline, do in fact have this tag.
Accessibility checkpoints are supported for the Web environment
 Page Checkpoint checks the characteristics of a Web page. For example, you can check how long a Web page takes to load or whether a Web page contains broken links.
Note: You create a page checkpoint by inserting a standard checkpoint on a page object.
Page checkpoints are supported for the Web environment

 Database Checkpoint checks the contents of a database accessed by your Web site. For example, you can use a database checkpoint to check the contents of a database containing flight information for your Web site.
Database checkpoints are supported by all environments.
 XML Checkpoint checks the data content of XML documents in XML files or XML documents in Web pages and frames. XML checkpoints (Web page/frame) are supported for the Web environment; XML checkpoints (file) are supported by all environments
For more specific information refer to Checkpoints

Adding checkpoints in a test in QTP
There are several ways to add checkpoints.
 To add checkpoints while recording
 To add a checkpoint while editing the test
For more information refer to Checkpoints

11.2 Output Values for Verification
The following are the categories of output values that can be created:
 Standard Output Values
 Text Output Values
 Text Area Output Values
 Database Output Values
 XML Output Values
For more information refer to Checkpoints

Adding output values in a test in QTP
 To add checkpoints while recording
 To add a checkpoint while editing the test
For more information refer to Checkpoints
Output Values Properties Dialog Box

The Output Value Properties dialog box enables you to choose which property values to output and to define the settings for each value that you select.
Note: If you insert an output value on a Web page, the Page Output Value Properties dialog box opens. This dialog except that it contains two additional option areas, HTML verification and All objects in page. These options are relevant only for checkpoints and are disabled when defining output values.

The output values can be output to either of these locations:
 Global\Local Sheet
 Environment variables
 Action\Test Parameter.
This option is given in the output options dialog box

12. Reusable Library

Description

When forming a new product the traditional engineer can take advantage of ready-made subassemblies. To the test engineer, reusable software components offer the same possibilities; the same components can be incorporated into many whole new systems, thus saving the considerable time and effort it can take to generate new software.

Starting with an introduction to software reuse and a discussion of its feasibility, the authors go on to consider how the components that may be found could be used. The reusable library was designed with reuse very much in mind, making it essentially a small, but invaluable, library.

12.1 Introduction
In QTP we can create VBScript library files containing VBScript functions, subroutines, classes, modules, etc., and then associate the files with our test. We can call any VBScript function, subroutine, etc., contained within any library file that is associated with our test. Any text file written in standard VBScript syntax can act as a library file.

a) Functions
i. Built-In

ii. User defined

We can specify the default library files for all new tests in the Test Settings dialog box (Test > Settings > Resources tab). We can also edit the list of associated library files for an existing test in the Test Settings dialog box. Note that once a test is created, the list of files specified in the Test Settings dialog box is independent of the files set as default in the Test Settings dialog box. Changes to the default library files list in the Test.

12.2 How to establish a Reusable Library
a. Defining Resource Settings for Your Test
We can use the Resources tab of the Test Settings dialog box to associate specific files with your test, such as VBScript library files and Data Table files, and to specify the object repository mode and file to use for our test. We can also set the currently associated library files and object repository settings as the default settings for all new tests.

b. Executing Externally-Defined Functions from Your Test
We can create a VBScript file and call its functions, subroutines, classes, etc., from an action in your test or from an associated library file by inserting an ExecuteFile statement in our action or library file.

When we run our test, the ExecuteFile statement executes all global code in the specified file in order to make all definitions in the file available from the global scope of the action's (or library file's) script.
To execute an externally-defined function:
1. Create a VBScript file using standard VBScript syntax.
2. Store the file in any folder that you can access from the machine running your test.
3. Add an ExecuteFile statement to an action in your test or in an associated library file using the following syntax:
ExecuteFile FileName
where FileName is the absolute or relative path of our VBScript file.
1. Use the functions, subroutines, classes, etc., from the specified VBScript file as necessary in your action or within other functions in an associated library file.

12.3 How to use this Reusable Library.

13. Regular Expressions

13.1 Description
While creating checkpoints we have an option only to search or check for a specific text string or a specific value of a property. To increase the flexibility and adaptability of the tests we use regular expressions.
Regular Expressions enable Quick Test to identify objects and text strings with varying values.

A regular expression is a string that specifies a complex search phrase. By using special characters we define the conditions of the search.

The most common expressions that can be used to create regular expressions are:

1. Using the Backslash Character
A backslash (\) instructs Quick Test to treat the next character as a literal character, if it is otherwise a special character. The backslash (\) can also instruct Quick Test to recognize certain ordinary characters as special characters.
For example, consider a Web site called:
mercurytours.mercuryinteractive.com
The period would be mistaken as an indication of a regular expression. To indicate that the period is not part of a regular expression, you would write it as follows:
mercurytours\.mercuryinteractive\.com

2. Matching Any Single Character
A period (.) instructs Quick Test to search for any single character (except for \n). For example:
welcome.
matches welcomes, welcomed, or welcome followed by a space or any other single character. A series of periods indicates the same number of unspecified characters.
To match any single character including \n, enter: (.|\n)

3. Matching Any Single Character in a List
Square brackets instruct QuickTest to search for any single character within a list of characters. For example, to search for the date 1967, 1968, or 1969, write: 196[789]

4. Matching Any Single Character Not in a List

When a caret (^) is the first character inside square brackets, it instructs QuickTest to match any character in the list except for the ones specified in the string. For example: [^ab]
matches any character except a or b.

5. Matching Any Single Character within a Range

In order to match a single character within a range, you can use square brackets ([ ]) with the hyphen (-) character. For instance, to match any year in the 1960s, write: 196[0-9]

A hyphen does not signify a range if it is displayed as the first or last character within brackets, or after a caret (^).
For example, [-a-z] matches a hyphen or any lowercase letter.

6. Matching Zero or More Specific Characters

An asterisk (*) instructs QuickTest to match zero or more occurrences of the preceding character. For example:
ca*r matches car, caaaaaar, and cr.
7. Matching One or More Specific Characters
A plus sign (+) instructs QuickTest to match one or more occurrences of the preceding character. For example:
ca+r matches car and caaaaaar, but not cr.
8. Matching Zero or One Specific Character

A question mark (?) instructs Quick Test to match zero or one occurrences of the preceding character. For example:
ca?r matches car and cr, but nothing else.
9. Grouping Regular Expressions
Parentheses (()) instruct Quick Test to treat the contained sequence as a unit, just as in mathematics and programming languages.
Using groups is especially useful for delimiting the argument(s) to an alternation operator ( | ) or a repetition operator ( * , + , ? , { } ).
10. Matching One of Several Regular Expressions
A vertical line (|) instructs QuickTest to match one of a choice of expressions. For example: foo|bar
causes QuickTest to match either foo or bar.
fo(o|b)ar
causes Quick Test to match either fooar or fobar.
11. Matching the Beginning of a Line
A caret (^) instructs QuickTest to match the expression only at the start of a line, or after a newline character.
For example: book
matches book within the lines—book, my book, and book list, while
^book
Matches book only in the lines—book and book list
12. Matching the End of a Line
A dollar sign ($) instructs Quick Test to match the expression only at the end of a line, or before a new line character. For example: book
Matches book within the lines—my book, and book list, while a string that is followed by ($), matches only lines ending in that string. For example: book$
Matches book only in the line—my book.

13.Matching Any AlphaNumeric Character Including the Underscore
\w instructs QuickTest to match any alphanumeric character and the underscore (A-Z, a-z, 0-9, _).
For example:
\w* causes QuickTest to match zero or more occurrences of the alphanumeric characters—A-Z, a-z, 0-9, and the underscore (_). It matches Ab, r9Cj, or 12_uYLgeu_435.
For example:
\w{3} causes Quick Test to match 3 occurrences of the alphanumeric characters A-Z, a-z, 0-9, and the underscore (_). It matches Ab4, r9_, or z_M.
14. Matching Any Non-AlphaNumeric Character
\W instructs QuickTest to match any character other than alphanumeric characters and underscores. For example:
\W matches &, *, ^, %, $, and # .
15. Combining Regular Expression Operators
You can combine regular expression operators in a single expression to achieve the exact search criteria you need.
For example, you can combine the `.' and `*' characters in order to find zero or more occurrences of any character (except \n).
For example, start.*
matches start, started, starting, starter, etc.
You can use a combination of brackets and an asterisk to limit the search to a combination of non-numeric characters. For example:
[a-zA-Z]*

Creating checkpoints with Regular Expressions
Regular expressions are generally used in the context of creating checkpoints to check a range of values.
For more information on creating checkpoints with regular expressions refer Regular Expressions

Analyzing a Test with Regular Expressions
When the test run is completed, the Test Results window opens.
1. Examine the checkpoint results.
In the results tree, expand (+) Test RegExpression Summary > RegExpression Iteration 1 (Row 1) > Action1 Summary > Flight Reservations > Fax Order No. 12
Select CheckPoint "Fax Order No\. [0-9][0-9]".

The checkpoint passed because the text was displayed in the format specified by the regular expression.

14. Recovery Scenario

You can instruct Quick Test to recover from unexpected events and errors that occur in your testing environment during a test run.
Unexpected events, errors, and application crashes during a test run can disrupt your test and distort test results. This is a problem particularly when running tests unattended—the test is suspended until you perform the action needed to recover.
The Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario—a definition of an unexpected event and the operation(s) necessary to recover the test run. For example, you can instruct Quick Test to detect a Printer out of paper message and recover the test run by clicking the OK button to close the message and continue the test.

A recovery scenario consists of the following:
 Trigger Event—The event that interrupts your test run. For example, a window that may pop up on screen, or a Quick Test test run error.
 Recovery Operation(s)—The operation(s) that need to be performed in order to continue running the test. For example, clicking an OK button in a pop-up window, or restarting Microsoft Windows.
 Post-Recovery Test Run Option—The instructions on how Quick Test should proceed once the recovery operations have been performed, and from which point in the test Quick Test should continue, if at all. For example, you may want to restart a test from the beginning, or skip a test step entirely and continue with the next step in the test.

Recovery scenarios are saved in recovery scenario files. A recovery scenario file is a logical collection of recovery scenarios, grouped according to your own specific requirements.

To instruct Quick Test to perform a recovery scenario during a test run, you must first associate it with that test. A test can have any number of recovery scenarios associated with it. You can prioritize the scenarios associated with your test to ensure that trigger events are recognized and handled in the required order.

When you run a test for which you have defined recovery scenarios and an error occurs, Quick Test looks for the defined trigger event(s) that caused the error. If a trigger event has occurred, Quick Test performs the corresponding recovery and post-recovery operations.

You can also control and activate your recovery scenarios during the test run by inserting Recovery statements into your test.

Note: If you choose On error in the Activate recovery scenarios box in the Recovery tab of the Test Settings dialog box, the recovery mechanism does not handle triggers that occur in the last step of a test. If you chose this option and need to recover from an unexpected event or error that may occur in the last step, you of a test can do this by adding an extra step to the end of your test.

14.1 Exceptional Handling using Recovery Scenarios
The Recovery Scenario Manager dialog box enables you to create recovery scenarios and save them in recovery files. You create recovery scenarios using the Recovery Scenario Wizard, which leads you through the process of defining each of the stages of the recovery scenario. You then save the recovery scenarios in a recovery file, and associate them with a specific test or tests.

Creating a Recovery File

You save your recovery scenarios in a recovery file. A recovery file is a convenient way to organize and store multiple recovery scenarios together. You can create a new recovery file or edit an existing one.

For more information on creating a Recovery File refer to Creating a Recovery File

Saving the Recovery Scenario in a Recovery File

After you create or modify a recovery scenario in a recovery file using the Recovery Scenario Wizard, you need to save the recovery file.

To save a new or modified recovery file:
1. Click the Save button . If you added or modified scenarios in an existing recovery file, the recovery file and its scenarios are saved. If you are using a new recovery file, the Save Attachment dialog box opens.

Tip: You can also click the arrow to the right of the Save button and select Save As to save the recovery file under a different name.

2. Choose the folder in which you want to save the file.

3. Type a name for the file in the File name box. The recovery file is saved in the specified location with the file extension .qrs.

Tip: If you have not yet saved the recovery file, and you click the Close button in the Recovery Scenario Manager dialog box, Quick Test prompts you to save the recovery file. Click Yes, and proceed with step 2 above. If you added or modified scenarios in an existing recovery file, and you click Yes to the message prompt, the recovery file and its scenarios are saved.

Managing Recovery Scenarios

Once you have created recovery scenarios, you can use the Recovery Scenario Manager to manage them.

The Recovery Scenario Manager contains the following recovery scenario icons:
Icon Description
Indicates that the recovery scenario is triggered when a window pops up in an open application during the test run.
Indicates that the recovery scenario is triggered when the property values of an object in an application match specified values.
Indicates that the recovery scenario is triggered when a step in the test does not run successfully.
Indicates that the recovery scenario is triggered when an open application fails during the test run.

The Recovery Scenario Manager enables you to manage existing scenarios by:
 Viewing Recovery Scenario Properties
 Modifying Recovery Scenarios
 Deleting Recovery Scenarios
 Copying Recovery Scenarios between Recovery Scenario Files

Viewing Recovery Scenario Properties

You can view properties for any defined recovery scenario.

To view recovery scenario properties:
1 In the Scenarios box, select the recovery scenario whose properties you want to view.
2 Click the Properties button . Alternatively, you can double-click a scenario in the
Scenarios box. The Recovery Scenario Properties dialog box opens.

The Recovery Scenario Properties dialog box displays the following read-only information about the selected scenario:

 General tab—Displays the name and description defined for the recovery scenario, plus the name and path of the recovery file in which the scenario is saved.
 Trigger Event tab—Displays the settings for the trigger event defined for the recovery scenario.
 Recovery operation tab—Displays the recovery operation(s) defined for the recovery scenario.
 Post-Recovery Operation tab—Displays the post-recovery operation defined for the recovery scenario.

Modifying Recovery Scenarios

You can modify the settings for an existing recovery scenario.

To modify a recovery scenario:
1 In the Scenarios box, select the scenario that you want to modify.
2 Click the Edit button . The Recovery Scenario Wizard opens, with the settings you defined for the selected recovery scenario.
3 Navigate through the Recovery Scenario Wizard and modify the details as needed.

Deleting Recovery Scenarios
You can delete an existing recovery scenario if you no longer need it. When you delete a recovery scenario from the Recovery Scenario Manager, the corresponding information is deleted from the recovery scenario file.

Note: If a deleted recovery scenario is associated with a test, Quick Test ignores it during the test run.

To delete a recovery scenario:
1 In the Scenarios box, select the scenario that you want to delete.
2 Click the Delete button . The recovery scenario is deleted.

Copying Recovery Scenarios between Recovery Scenario Files

You can copy recovery scenarios from one recovery scenario file to another.

To copy a recovery scenario from one recovery scenario file to another:
1 In the Scenarios box, select the recovery scenario that you want to copy.
2 Click the Copy button . The scenario is copied to the Clipboard.
3 Click the Open button and select the recovery scenario file to which you want to copy the scenario, or click the New button to create a new recovery scenario file in which to copy the scenario.
4 Click the Paste button . The scenario is copied to the new recovery scenario file.

Note: If a scenario with the same name already exists in the recovery scenario file, you can choose whether you want to replace it with the new scenario you have just copied.

Setting the Recovery Scenarios List for Your Tests

After you have created recovery scenarios, you associate them with selected tests so that Quick Test will perform the appropriate scenario(s) during the test runs if a trigger event occurs. You can prioritize the scenarios and set the order in which Quick Test applies the

scenarios during the test run. You can also choose to disable specific scenarios, or all scenarios, that are associated with a test. You can also define which recovery scenarios will be used as the default scenarios for all new tests.

Adding Recovery Scenarios to Your Test

After you have created recovery scenarios, you can associate one or more scenarios with a test in order to instruct Quick Test to perform the recovery scenario(s) during the test run if a trigger event occurs. The Recovery tab of the Test Settings dialog box lists all the recovery scenarios associated with the current test.

Tip: When a trigger event occurs, Quick Test checks for applicable recovery scenarios in the order in which they are displayed in the Recovery tab. You can change this order as described in “Setting Recovery Scenario Priorities”

For more information on “adding a recovery scenario to a test” refer to Adding Recovery Scenario to a Test

Viewing Recovery Scenario Properties

You can view properties for any recovery scenario associated with your test.

To view recovery scenario properties:
1 In the Scenarios box, select the recovery scenario whose properties you want to view.
2 Click the Properties button . Alternatively, you can double-click a scenario in the Scenarios box. The Recovery Scenario Properties dialog box opens, displaying read-only information regarding the settings for the selected scenario.

Setting Recovery Scenario Priorities
You can specify the order in which Quick Test performs associated scenarios during a test run. When a trigger event occurs, Quick Test checks for applicable recovery scenarios in the order in which they are displayed in the Recovery tab of the Test Settings dialog box.

To set recovery scenario priorities:
1 In the Scenarios box, select the scenario whose priority you want to change.
2 Click the Up or Down button . The selected scenario’s priority changes according to your selection.
3 Repeat steps 1-2 for each scenario whose priority you want to change.

Removing Recovery Scenarios from Your Test

You can remove the association between a specific scenario and a test using the Recovery tab of the Test Settings dialog box. After you remove a scenario from a test, the scenario itself still exists, but Quick Test will no longer perform the scenario during a test run.

To remove a recovery scenario from your test:

1 In the Scenarios box, select the scenario you want to remove.
2 Click the Remove button . The selected scenario is no longer associated with the test.

Enabling and Disabling Recovery Scenarios

You can enable or disable specific scenarios and determine when Quick Test activates the recovery scenario mechanism in the Recovery tab of the Test Settings dialog box. When you disable a specific scenario, it remains associated with the test, but is not performed by Quick Test during the test run. You can enable the scenario at a later time.

To enable/disable specific recovery scenarios:
 Select the check box to the left of one or more individual scenarios to enable them.
 Clear the check box to the left of one or more individual scenarios to disable them.

To define when the recovery mechanism is activated:
Select one of the following options in the Activate recovery scenarios box:
 Always—The recovery mechanism is activated after every step.
 On error—The recovery mechanism is activated only after steps that return an error return value.

Note that the step that returns an error is often not the same as the step that causes the exception event to occur.

For example, a step that selects a check box may cause a pop-up dialog box to open. Although the pop-up dialog box is defined as a trigger event, Quick Test moves to the next step because it successfully performed the check box selection step. The next several steps could potentially perform checkpoints, functions or other conditional or looping statements that do not require performing operations on your application. It may only be ten statements later that a step instructs Quick Test to perform an operation on the application that it cannot perform due to the pop-up dialog box. In this case, it is this tenth step that returns an error and triggers the recovery mechanism to close the dialog box. After the recovery operation is completed, the current step is this tenth step, and not the step that caused the trigger event.
 Never—The recovery mechanism is disabled.

Setting Default Recovery Scenario Settings for All New Tests

You can click the Set as Default button in the Recovery tab of the Test Settings dialog box to set the current list of recovery scenarios to be the default scenarios for all new tests. Any future changes you make to the current recovery scenario list only affect the current test, and do not change the default list that you defined.

14.2 Sample for Recovery Scenario:
For adding a recovery Scenario:

Let us take an example of a popup window exception,

In Flight Application, when we give wrong password in the login dialog box then we get the following popup window:

In order to handle this, take a new recovery scenario, in the “Select Trigger Event” screen of Recovery Scenario Wizard, select “pop-up window” Radio button as shown below,

In the next screen, we can specify Pop-up window condition, by spying the popup window, then details of the pop-up window appears as follows:

then in the next step, In the recovery operation screen select “keyboard or mouse operation” radio button, then in the next step select “Press ENTER Key” radio button,

In the next screen select “Add another recovery operation” check box as given below:

then in the next step, In the recovery operation screen select “function call” radio button

Specify the path and name of the library file which has the appropriate function for entering the password and clicking “ok” button of “Login” dialog box.

In the “Post-Recovery Test Run Options” screen select “Repeat current step and Continue” radio button, give a name to the recovery scenario, thus the recovery will be created.

Adding a Recovery scenario into the Test:

We can add the Recovery Scenario to our test in two ways.

1. We can add the Recovery Scenario to our test while we create a new Recovery Scenario by checking the “add Scenario to current test” check box in “Completing the Recovery Scenario Wizard” screen of Recovery Scenario Wizard.

2. The other way to add Recovery Scenario to our test is by adding the required scenario file in the recovery tab of Test Settings Dialog box.

15. Optional Steps
15.1 Description:
When running a test, if a step does not succeed in opening a dialog box, QuickTest does not necessarily abort the test run. It bypasses any step designated "optional" and continues running the test. By default, QuickTest automatically marks as optional steps that open certain dialog boxes. You can manually designate additional steps as optional.
If a dialog box may or may not appear at a particular instanse then that dialog box actions performed can be set as optional, so that it proceeds to the next step, if the screen or dialog box doesn’t appear or will continue the normal flow.
Default Optional Steps:
There are some default objects, which QTP recognizes as optional, for those objects QTP by default sets as optional, those objects are as follows:
Dialog boxes with title bar as
Auto Complete
File Download
Internet Explorer
Netscape
Enter Network Password
Error
Security Alert
Security Information
Security Warning
Username and Password Required

Setting Optional Steps:
There are two ways of setting Optional steps:
1. We can directly Right-click a step in the Keyword View and choose Optional Step. The Optional Step icon will be added next to the selected step.
2. You can also add an optional step from the Expert View by adding OptionalStep to the beginning of the VBScript statement.
Example:
OptionalStep.Browser("browser_name").Page("page_n ame").Link("link_name")

16. Reporting

The process of reporting is to customize the test results, and add the appropriate comments and reports to the test results to increase the readability of it. Reporting can be done in various formats.

Test Results Window
After a test run, we view the results in the Test Results window. By default, the Test Results window opens when a test run is completed.
Note: You can open the Test Results window as a standalone application from the Start menu. To open the Test Results window, choose Start > Programs > QuickTest Professional > Test Results Viewer.

The Test Results window contains the following key elements:
 Menu bar—Displays menus of available commands.
 Test results toolbar—Contains buttons for viewing test results (choose View > Test Results Toolbar to display the toolbar).
 Test results tree—Contains a graphic representation of the test results in the test results tree.
 Test results details—Contains details of the selected step.
 Active Screen—Shows the active screen of the particular window or step in the results.

16.1 Different Options for Reporting

There are 3 options for screen capture the screens to the results:
 Always – adds screen shots to the results for every step.
 On Errors – adds screen shots only on occurrence of error
 On Errors and Warnings – adds on both errors and warnings.
 Never

Note: If “Always” option is selected then the result file will occupy lots of memory, thus selection of “Always” option should be done only if the client wants to view all the screen shots for reference during review.

16.2 Functions used for Reporting
1. ReportEvent Method

Reports an event to the Test Reports.
Syntax: Reporter.ReportEvent EventStatus, ReportStepName, Details [, in]
Argument Type Description
EventStatus Number or pre-defined constant Status of the report step:
0 or micPass: Causes the status of this step to be passed and sends the specified message to the report.
1 or micFail: Causes the status of this step to be failed and sends the specified message to the report. When this step runs, the test fails.
2 or micDone: Sends a message to the report without affecting the pass/fail status of the test.
3 or micWarning: Sends a warning message to the report, but does not cause the test to stop running, and does not affect the pass/fail status of the test.
4 or micInfo: Applies an information status (and icon) to the step. This status does not affect the pass/fail status of the test.
ReportStepName String Name of the intended step in the report (object name).
Details String Description of the report event. The string will be displayed in the step details frame in the test report .
in N/A Not in use.

Example
The following example uses the Report Event method to report that the checkpoint on this window has passed.
Reporter.ReportEvent 0,"Fax Order No. 12","The check point for this window has passed "

2. Filter Property

Retrieves or sets the current mode for displaying events in the Test Results. You can use this method to completely disable or enable reporting of steps following the statement, or you can indicate that you only want subsequent failed or failed and warning steps to be included in the report.

Syntax:

To retrieve the mode setting:
CurrentMode = Reporter.Filter
To set the mode:
Reporter.Filter = NewMode
The mode can be one of the following values:
Mode Description
0 or
rfEnableAll Default. All reported events are displayed in the Test Results.
1 or rfEnableErrorsAndWarnings Only event with a warning or fail status are displayed in the Test Results.
2 or
rfEnableErrorsOnly Only events with a fail status are displayed in the Test Results.
3 or
rfDisableAll No events are displayed in the Test Results.

Example

The following example uses the Filter method to report the following events in the Test Results: 1, 2, 5, and 6.
Reporter.ReportEvent micGeneral, "1", ""
Reporter.ReportEvent micGeneral, "2", ""
Reporter.Filter = rfDisableAll
Reporter.ReportEvent micGeneral, "3", ""
Reporter.ReportEvent micGeneral, "4", ""
Reporter.Filter = rfEnableAll
Reporter.ReportEvent micGeneral, "5", ""
Reporter.ReportEvent micGeneral, "6", "

3. ReportPath Property

Retrieves the folder path in which the current test's Test Results are stored.

Syntax
Path = Reporter.ReportPath
Argument Type Description
Path String The folder path in which the current test's Test Results are stored.

Example

The following example uses the ReportPath method to retrieve the folder in which the test's Test Results are stored and displays the folder in a message box.
dim Path
Path = Reporter.ReportPath
MsgBox (Path)

16.3 Reporting Formats
The results of the QTP runs are stored in the Results folder, which must be specified before starting the test run. The results are stored in 2 types of formats:
 QTP format – this is the format in which the results are displayed in the test window, opens with QTP
 XML format – the results are also stored in XML file, in which all the objects are stored in a hierarchy in .xml format. This is useful in transfer of the results information across platforms, since it is based on simple Unicode format.

Fig: results in XML format

Quick Test Professional FAQ’s

2008-07-02T10:12:00.000-07:00

Quick Test Professional FAQ’s
------------------------------
1. How QTP scripts are advantageous when need to re-work the same business scenarios?

A. To record the Quick Test Professional Script on one instance and be able to execute it on any other instance. The assumption is there are no major GUI changes between the recorded and the execution instances.

2. How can you make the scripts generic and what architecture needs to be followed?

A. In order to achieve the above objective, we need to plan the Quick Test Professional script. It should have two parts:
1. Script – that is generic Quick test script.
2. Data – from the parameter file that is customer instance specific.

Eg. Imagine a business flow has a scenario
- Login to the web page
- Check mail
- Logout
1. Create data/parameter file (can be flat file [.txt] or an excel file) is instance specific.
2. Create (record/program) the QTP initialization
3. The initialization script which calls the Object repository, common function library and all QTP actions/scripts

3. How to create an individual script?

A. Record the Quick Test Professional script and modify it to make it a generic script using the following steps:

a. Set the testing options in the Test Settings Dialog box.
b. Record the script
c. Modify the script to make it generic:
i. Parameterize the hard coded values.
ii. Modify the Object Repository file with regular expressions.
iii. Add unique properties to items in the Object Repository to make recognition simpler.
iv. Insert synchronization points as required.
v. Insert checkpoints for pass/fail validation.
vi. Insert additional programming logic.
vii. Use the Common Functions.

4. What is the testing process in QTP?

A. The testing process consists of 3 main phases:

1. Gather relevant test information – Input data should be gathered.

2. Create the basic test – Record/Program the scripts in actions

3. Enhance the basic test
Use Data Driven scripts to use the script to test with different sets of data
Reusable Actions- Identify the common scenarios and make the scripts generic and reuse the scripts across different business scenarios.

5. What are different types of recording modes in QTP?

A. There are two recording modes
1. Low-level
2. Analog

Low – Level Recording:

Use Low-Level Recording when you need to record the exact location of the object on your application screen.
To record in Low-Level Recording, select “Low-Level Recording” from the “Test” menu while recording

Analog:

Use Analog Recording for applications in which the actual movement of the mouse is what you want to record.
To record in Analog mode, select “Analog Recording” from the “Test” menu while recording.

6. What is Object repository?

A. The Object Repository dialog box displays a test tree of all objects in the current action or the entire test (depending on the object repository mode you choose when you create your test). You can use the Object Repository dialog box to view or modify the properties of any test object in the repository or to add new objects to your repository.

Object Repository Modes

Per – Action Object Repository:
This is the default setting, and all tests created in QuickTest 5.6 or earlier use this mode. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can record and run tests without creating, choosing, or modifying object repository files.
Shared Object Repository:
In this mode, you can use one object repository file for multiple tests if the tests include the same objects. Object information that applies to many tests is kept in one central location. When the objects in your application change, you can update them in one location for multiple tests

7. How to select the Object repository mode?

A. To select the object repository mode
Goto Test Settings > Resource Tab to change the Object Repository Mode

The default object repository file name is default.tsr
You can change object repository mode when the Test contain no actions.

8. What is Active screen? What are the advantages of Active screen?

A. Active screen captures all the properties of the application and makes available even when offline/ when you are not connected to the application.
The main advantage is checkpoints can be added without connecting to the application

9. What are different Screen capture options available for Active screen?

A. Complete—Captures all properties of all objects in the application’s active window/dialog box/Web page in the Active Screen of each step. This level saves Web pages after any dynamic changes and saves Active Screen files in a compressed format.

Partial—(Default). Captures all properties of all objects in the application’s active window/dialog box/Web page in the Active Screen of the first step performed in an application’s window, plus all properties of the recorded object in subsequent steps in the same window. This level saves Web pages after any dynamic changes and saves Active Screen files in a compressed format.

Minimum—Captures properties only for the recorded object and its parent in the Active Screen of each step. This level saves the original source HTML of all Web pages (prior to dynamic changes) and saves Active Screen files in a compressed format.

None—Disables capturing of Active Screen files for all applications and Web pages.

10. How QTP identifies the objects in the application during runtime?

A. QTP uses different properties to identify the objects in the applications. They are:
a. Mandatory Properties
b. Assistive Properties
c. Object Identifies
d. Smart Identification

11. Explain all Object identification properties.

A. Mandatory and Assistive Properties:
During the test run, QuickTest looks for objects that match all properties in the test object description - it does not distinguish between properties that were learned as mandatory properties and those that were learned as assistive properties

Smart Identification: QuickTest uses a very similar process of elimination with its Smart Identification mechanism to identify an object, even when the recorded description is no longer accurate. Even if the values of your test object properties change, QuickTest’s TestGuard technology maintains your test’s reusability by identifying the object using Smart Identification.

12. What are Ordinal identifies. Explain in detail.

A. Ordinal Identifiers are
Index:
Indicates the order in which the object appears in the application code relative to other objects with an otherwise identical description.

Location:
Indicates the order in which the object appears within the parent window, frame, or dialog box relative to other objects with an otherwise identical description. Values are assigned from top to bottom, and then left to right.

The Web Browser object has a third ordinal identifier type:

Creation Time:
Indicates the order in which the browser was opened relative to other open browsers with an otherwise identical description.

13. What is Smart Identification?

A. Smart Identification:
If QuickTest is unable to find any object that matches the recorded object description, or if it finds more than one object that fits the description, then QuickTest ignores the recorded description, and uses the Smart Identification mechanism to try to identify the object.

While the Smart Identification mechanism is more complex, it is more flexible, and thus, if configured logically, a Smart Identification definition can probably help QuickTest identify an object, if it is present, even when the recorded description fails.

14. What are the properties available in Smart identification?

A. Base filter properties:
The most fundamental properties of a particular test object class; those whose values cannot be changed without changing the essence of the original object. For example, if a Web link’s tag was changed from
Optional filter properties:
Other properties that can help identify objects of a particular class as they are unlikely to change on a regular basis, but which can be ignored if they are no longer applicable.

15. What is Object Spy? How is it used in QTP?

A. Using the Object Spy, you can view the run-time or test object properties and methods of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree. It displays the run-time or test object properties and values of the selected object in the Properties tab. It displays the run-time or test object methods associated with the selected object in the Methods tab

16. What are Run-Time Object Properties / Run-Time Object Methods?

A. Run-Time Object Properties / Run-Time Object Methods:
You can use the Object property to access the native properties of any run-time object. For example, you can retrieve the current value of the ActiveX calendar’s internal Day property as follows:

Eg. Sample code
Dim MyDay
Set MyDay = Browser('index').Page('Untitled').ActiveX('MSCAL.Calendar.7').Object.Day

17. What are Test Object Properties / Test Object Methods?

A. Test Object Properties / Test Object Methods:
You can use the GetTOProperty and SetTOProperty methods to retrieve and set the value of test object properties for test objects in your test.

You can use the GetROProperty to retrieve the current property value of objects in your application during the test run.

18.What are User-Defined Test Object Classes. How are they mapped?

A User-Defined Test Object Classes:
The Object Mapping dialog box enables you to map an object of an unidentified or custom class to a Standard Windows class. For example, if your application has a button that cannot be identified, this button is recorded as a generic WinObject. You can teach QuickTest to identify your object as if it belonged to a standard Windows button class. Then, when you click the button while recording a test, QuickTest records the operation in the same way as a click on a standard Windows button. When you map an unidentified or custom object to a standard object, your object is added to the list of Standard Windows test object classes as a user-defined test object. You can configure the object identification settings for a user defined object class just as you would any other object class

19. What are checkpoints?

A. A checkpoint is a verification point that compares a current value for a specified property with the expected value for that property. This enables you to identify whether your Web site or application is functioning correctly.

When you add a checkpoint, Quick Test adds a checkpoint with an icon in the test tree and adds a Check Point statement in the Expert View. When you run the test, Quick Test compares the expected results of the checkpoint to the current results. If the results do not match, the checkpoint fails. You can view the results of the checkpoint in the Test Results window.

20. What is a standard checkpoint?

A. You can check that a specified object in your application or on your Web page has the property values you expect, by adding a standard checkpoint to your test. To set the options for a standard checkpoint, you use the Checkpoint Properties dialog box.

21. What is Text or Text Area Checkpoint?

A. Text or Text Area Checkpoint Results
By adding text or text area checkpoints to your tests, you can check that a text string is displayed in the appropriate place in your application or on your Web page. When you run your test, Quick Test compares the expected results of the checkpoint to the actual results of the test run. If the results do not match, the checkpoint fails.

23. What is Bitmap Checkpoint?

A. Bitmap Checkpoints:
You can check an area of a Web page or application as a bitmap. While creating a test, 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. You can also choose to save only the selected area of the object with your test in order to save disk space.

24. What is Table and Database Checkpoint?

A. Table and Database Checkpoints:
By adding table checkpoints to your tests, you can check that a specified value is displayed in a cell in a table on your Web page or in your application. By adding database checkpoints to your tests, you can check the contents of databases accessed by your Web page or application. The results displayed for table and database checkpoints are similar. When you run your test, Quick Test compares the expected results of the checkpoint to the actual results of the test run. If the results do not match, the checkpoint fails.

25. What is Accessibility Checkpoint?

A. Accessibility Checkpoints:
You can add accessibility checkpoints to help you quickly identify areas of your Web site that may not conform to the W3C (World Wide Web Consortium) Web Content Accessibility Guidelines. You can add automatic accessibility checkpoints to each page in your test, or you can add individual accessibility checkpoints to individual pages or frames.

26. What is XML Checkpoint?

A. XML Checkpoint:
The XML Checkpoint Properties dialog box displays the element hierarchy and values (character data) of the selected XML file.

Select the element(s), attribute(s), and/or value(s) that you want to check. For each element you want to check, select the checks you want to perform. For each attribute or value you want to check, select the checks you want to perform, or the parameterization options you want to set.

27. What is Synchronization?

A. When you run tests, your application may not always respond with the same speed. For example, it might take a few seconds:
 for a progress bar to reach 100%
 for a status message to appear
 for a button to become enabled
 for a window or pop-up message to open
You can handle these anticipated timing problems by synchronizing your test to ensure that Quick Test waits until your application is ready before performing a certain step.

28. What are different functions available for Synchronization?

A. There are several options that you can use to synchronize your test:

You can insert a synchronization point, which instructs Quick Test to pause the test until an object property achieves the value you specify. When you insert a synchronization point into your test, Quick Test generates a WaitProperty statement in the Expert View.

29. What is the difference in Exists/wait statements?

A. Exist ()/ Wait()

You can insert Exist or Wait statements that instruct QuickTest to wait until an object exists or to wait a specified amount of time before continuing the test.

Eg. Browser('Yahoo”).Page('CheckMail”).Button(“CheckMail”).Exists(10)

QTP waits for 10 seconds till the button exists in the page. The script proceeds if the button even exits before 10 seconds unlike wait() statement – it waits for 10 seconds no matter the button exits before 10 seconds.

30. What is Default Time Out?

A. Default Time Out:
You can also increase the default timeout settings in the Test Settings and Options dialog boxes in order to instruct Quick Test to allow more time for certain events to occur

31. What is Parameterization (Data Table Wizard)?

A. You can supply the list of possible values for a parameter by creating a Data Table parameter. 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 substitutes the constant value with a different value from the Data Table.

32. What are Method Arguments?

A. Using Method arguments you parameterize method arguments in the Method Arguments dialog box. to open the Method Arguments dialog box, right-click a step containing a method in the test tree and choose Method Arguments. The Method Arguments dialog box opens and displays the method arguments in the step.

33. Well, I would like to run my test with different sets of data, How can I make it with the options available in QTP?

A. Listed are the different Data Table Iterations
Run one iteration only:
Runs the test only once, using only the first row in the global Data Table.

Run on all rows:
Runs the test with iterations using all rows in the global Data Table.
Run from row __ to row __ :
Runs the test with iterations using the values in the global Data Table for the specified row range.

34. What are different data tables available?

A. 1. Global Sheet
The Global sheet contains the data that replaces parameters in each iteration of the test.
2. Action Sheets
Each time you add a new action to the test, a new action sheet is added to the Data Table. Action sheets are automatically labeled with the exact name of the corresponding action. The data contained in an action sheet is relevant for the corresponding action only.

35. What is an Action?

A. An Quick test script contains different actions. An action contains the script ie. A piece of business scenario like, login to application, logout etc.

Well again It depends on how you create your framework ( If you would like to know more about frame work check out this link. Good one. http://www-128.ibm.com/developerworks/rational/library/591.html) for testing the applications.
I would suggest every action has a piece of business scenario which would help to re-use the script in a better way. Before deciding what are re-usable scripts. Firstly, identify all the common scenarios that occur in different business flows across different modules.
Then prepare the scripts and make generic. You can call all these functions by making this common function library available at Test options > Resourses.

36. What is Copy of action?

A. Copy of Action:
When you insert a copy of an action into a test, the action is copied in its entirety, including checkpoints, parameterization, and the corresponding action tab in the Data Table. If the test you are copying into uses per-action repository mode, the copied action’s action object repository will also be copied along with the action.

37. What are re-usable actions?

A. Reusable Actions:
Determines whether the action is a reusable action. A reusable action can be called multiple times within a test and can be called from other tests. Non-reusable actions can be copied and inserted as independent actions, but cannot be inserted as calls to the original action.

38. what about Call of Action?

A. You can insert a call (link) to a reusable action that resides in your current test (local action), or in any other test (external action).

39. When to Insert transactions?

A. Inserting Transactions:

During the test run, the Start Transaction signals the beginning of the time measurement. You define the beginning of a transaction in the Start Transaction dialog box

 The End Transaction signals the end of the time measurement

40. What are reular expressions?

A. Regular Expressions:
Regular expressions enable QuickTest to identify objects and text strings with varying values. You can use regular expressions when:
• Defining the property values of an object
• Parameterizing a step
• Creating checkpoints with varying values
A regular expression is a string that specifies a complex search phrase. By using special characters such as a period (.), asterisk (*), caret (^), and brackets ([ ]), you can define the conditions of a search. When one of these special characters is preceded by a backslash (\), QuickTest searches for the literal character.

Here is an example:
The actual pattern for the regular expression search is set using the Pattern property of the RegExp object. The RegExp.Global property has no effect on the Test method.
The Test method returns True if a pattern match is found; False if no match is found.
The following code illustrates the use of the Test method.
Function RegExpTest(patrn, strng)
Dim regEx, retVal ' Create variable.
Set regEx = New RegExp ' Create regular expression.
regEx.Pattern = patrn ' Set pattern.
regEx.IgnoreCase = False ' Set case sensitivity.
retVal = regEx.Test(strng) ' Execute the search test.
If retVal Then
RegExpTest = 'One or more matches were found.'
Else
RegExpTest = 'No match was found.'
End If
End Function
MsgBox(RegExpTest('is.', 'IS1 is2 IS3 is4'))

41. Create a script to print the message

A.
Dim MyVar
MyVar = MsgBox ('Hello World!', 65, 'MsgBox Example')
' MyVar contains either 1 or 2, depending on which button is clicked.

42. List all the run time errors in VB script.
A. VBScript run-time errors are errors that result when your VBScript script attempts to perform an action that the system cannot execute. VBScript run-time errors occur while your script is being executed; when variable expressions are being evaluated, and memory is being dynamic allocated.
Error Number Description
429 ActiveX component can't create object

507 An exception occurred

449 Argument not optional

17 Can't perform requested operation

430 Class doesn't support Automation

506 Class not defined

11 Division by zero

48 Error in loading DLL

5020 Expected ')' in regular expression

5019 Expected ']' in regular expression

432 File name or class name not found during Automation operation

92 For loop not initialized

5008 Illegal assignment

51 Internal error

505 Invalid or unqualified reference

481 Invalid picture

5 Invalid procedure call or argument

5021 Invalid range in character set

94 Invalid use of Null

448 Named argument not found

447 Object doesn't support current locale setting

445 Object doesn't support this action

438 Object doesn't support this property or method

451 Object not a collection

504 Object not safe for creating

503 Object not safe for initializing

502 Object not safe for scripting

424 Object required

91 Object variable not set

7 Out of Memory

28 Out of stack space

14 Out of string space

6 Overflow

35 Sub or function not defined

9 Subscript out of range

5017 Syntax error in regular expression

462 The remote server machine does not exist or is unavailable

10 This array is fixed or temporarily locked

13 Type mismatch

5018 Unexpected quantifier

500 Variable is undefined

458 Variable uses an Automation type not supported in VBScript

450 Wrong number of arguments or invalid property assignment

QTP VI

2008-07-02T10:11:00.001-07:00

1. To use an external spreadsheet to data-drive a test
1. Open the Excel file in Excel.
2. Verify that the first row of data contains the Column headers.
3. Rename the sheet(s) to match the names used in the test script (e.g., Global, Action1, etc.).
4. Open the test script.
5. Go to Test -> Settings.
6. Select the Resources tab.
7. In the Data table section, select the "Other location" radio button.
8. Click to close the warning dialog.
9. Enter the full path to the Excel file or browse to the file using the browse button (...).
10. Click .
11. Click .

2. To compare two .xls files
TrueOrFalse = "Same"
DataTable.Import("C:\Temp\test.xls")
FirstTableCount = DataTable.GetRowCount
DataTable.Import("C:\Temp\test1.xls")
SecondTableCount = DataTable.GetRowCount
if (FirstTableCount <> SecondTableCount) then
msgbox "Both files are not Equal"
else
For I = 1 To FirstTableCount
DataTable.Import("C:\Temp\test.xls")
Datatable.SetCurrentRow(I)
value1 = DataTable.Value("FirstSheetColumn")
DataTable.Import("C:\Temp\test1.xls")
Datatable.SetCurrentRow(I)
value2 = DataTable.Value("SecondSheetColumn")
if(value1 <> value2) then
TrueOrFalse = "Different"
Exit For
end if
Next
end if
msgbox(TrueOrFalse)

3. To parameterize a password

Option 1:
Use the Set method instead of SetSecure and parameterize that. This method will not encrypt the password.
Option 2:
1. Enter the "real" password in the data table.
2. Select the column that contains the password.
3. Right-click on the selected column and select Data -> Encrypt.
If you use Option 2, you can use the SetSecure method to directly access the encrypted password in the data table.

4. To specify number of times iteration in a test will execute

a. Go to Test -> Settings.
b. Select the Run tab.
c. In the Test Setting window, you will see a section called Data Table iterations. This is where you can specify the number of iterations. Select the "Run one iteration only" option to run only with the first row of data. Select "Run on all rows" to iterate through all rows of data. Select "Run from row x to row y" to specify which rows of data in the data table to use.
Note:
If you want to run on only one row of data, but do not want to use the first row, select the "Run from row x to row y" option specifying the same row for x and y.

5. To delete a row from the data table

Selecting a cell or row in the Data Table and pressing Ctrl+X or the Delete key on the keyboard deletes the data from the selected cell or row, but does not delete the actual cell or row. Thus, if you delete data from a row in the Data Table using one of these shortcut keys, QuickTest will still run an iteration on that row.
Workaround: To delete an entire cell or row from the Data Table, select it and choose Delete from the context menu, or press Ctrl+K on the keyboard.
6. If you import a Microsoft Excel table containing a combo box or list cells, conditional formatting, or other special cell formats, the formats are not imported and the cells are displayed in the Data Table with fixed values.
7. When you record a test and you try to play it back a popup window opens saying that “An Exception occurred in pdm.dll and Quick Test is going to close”.
How we go around this issue?
If version 6.0.0.8169 of Pdm.dll is found on the system, install a newer version from: http://support.microsoft.com/support/kb/articles/Q293/6/23.ASP. This will be recognized during installation and QuickTest Professional will instruct you to download the corrected DLL from the Microsoft site.
8. To verify if a checkbox within a Web table is selected
Use the ChildItem and GetROProperty methods to retrieve the state of a checkbox
The ChildItem method will return an object referencing the checkbox. Follow this with the GetROProperty method will return the property value specified of the object.
Example:
Set myObj = Browser("Table Example").Page("Table Example").WebTable("Bats").ChildItem(1, 1, "WebCheckBox", 0)
msgbox myObj.GetROProperty ("checked")
Where 0 is not checked and 1 is checked.
9. To rename the local data sheet name in the data table
If you rename a particular action that gets reflected in the local data sheet whereas you cannot rename any actions in the global data sheet.

10. to access the second row in local sheet without accessing the first row
The SetCurrentRow method sets the specified row as the current (active) row in the run-time data table.
Sheet.SetCurrentRow(RowNumber)
RowNumber - Indicates the number of the row to set as the active row.
If you do not specify that the sheet is a local sheet, using GetSheet, the row will be activated in the Global sheet by default.
Example:
DataTable.GetSheet("Action1") ' This will activate the specified sheet.
DataTable.SetCurrentRow(2) ' This will set the specified row in the activated sheet.
' If the GetSheet function is not used, it will set the Row in the Global Sheet.
msgbox(DataTable.Value("Data1", "Action1")) ' This will read the cell value.
DataTable.GetSheet("Action2").SetCurrentRow(3)
DataTable.Value("A", "Action2") = "new value"

Whats new in QTP8.2?

Unicode is supported.
Function to send Test result as mail.

Function SendMail(SendTo, Subject, Body, Attachment)
Set ol=CreateObject("Outlook.Application")
Set Mail=ol.CreateItem(0)
Mail.to=SendTo
Mail.Subject=Subject
Mail.Body=Body
If (Attachment <> "") Then
Mail.Attachments.Add(Attachment)
End If
Mail.Send
'ol.Quit
'ol.Skip
Set Mail = Nothing
Set ol = Nothing
End Function
'*************************************************************************************************
'Function SendMail(SendFrom, SendTo, Subject, Body)
' Set objMail=CreateObject("CDONTS.Newmail")
' ObjMail.From = SendFrom
' ObjMail.To = SendTo
'ObjMail.Subject = Subject
'ObjMail.Body = Body
'ObjMail.Send
'Set objMail = Nothing
'End Function
'***************************************************************************************************
SendTo = "Some one"
Subject = "Sending through QTP Test"
Body = "Testing"
Attachment = "Path"
Call SendMail(SendTo, Subject, Body, Attachment)

QUICK TEST PROFESSIONA V

2008-07-02T10:07:00.002-07:00

Q.T.P. 8.2 ( QUICK TEST PROFESSIONAL)

 Developed by Mercury Interactive
 Functionality Testing Tool
 Derived from Win Runner.
 Support all Win Runner 7.0 Supported technologies including .Net, XML, SAP, People Soft, Oracle Apps and multimedia technologies.
 Records our manual test cases in VB Script
 Short navigations to Edit VB Script programs.

QTP Testing Process:-

Select manual test cases to be automated.

Receive stable build from development team

Convert manual test procedures in to VB script programs.

Edit programs with control statement, Data Driven Test. Statements, Reusable actions--- etc.

Make VB Script programs as test batch. After required editing.

Run test batches

Analyze test results manually.

ADD-IN MANAGER:- These window list out all QTP supported technologies with respect to license.

NOTE:- In QTP, Every test maintains, global excel sheet likes Win Runner. In Win Runner excel sheet opening is explicit, but In QTP Excel sheet opening Implicit.

Recording Modes:- To convert our manual test case procedure into VB Script program. QTP is providing 3 Types of modes.
1. General Recording.
2. Analog Recording.
3. Low level Recording.

(1) General Recording:
In this mode QTP records mouse and Keyboard Operations with respect to Objects and Windows in our application build like as context Sensitive mode in Win Runner. It is a different mode in QTP when you click start recording icon, After click start recording icon, test Engineers can try to browse path of testing build, when he is planning more than one Software to use while creating test. This process is called Selective recording.

(2) Analog Recording: -
To record mouse pointer movement on the desktop we can use analog recording mode Ex:- Digital Signatures recording, Graphs drawing recording image movement recording. To select this mode, we can use below Navigation.
Navigation:- Text menu  Analog recording mode (or) Ctrl+Shift+f4

(3) Low Level Recording: -
In This mode QTP is recording mouse pointer movements on the desktop along with time to select this mode we can use.
Navigation:-
Text menu  Low Level recording (or) Ctrl+Shift+F3.

VISIBILITY MODES:-
QTP maintains two types of Visibilities such as
(1) Expert View (VB Script)
(2) Key word view (English)
Expert View: -
Expert view is only allowing Editing and running of the Script.

CHECK PIONTS:-
QTP is a functionality-testing tool and it provides facilities to automate below Coverage’s on application build.
(1) GUI Coverage or Behavioral Coverage
(2) Error handling coverage
(3) Input domain coverage
(4) Manipulations or out put coverage
(5) Back End coverage
(6) Service levels coverage
(7) Links coverage
(8) Static text/context coverage.
To automate above coverage’s we can use 7 checkpoints in QTP.
(1) Standard checkpoint
(2) Text check point
(3) Text area checkpoint
(4) Bitmap checkpoint
(5) Database checkpoint
(6) Accessibility checkpoint
(7) XML checkpoint

(1) Standard Checkpoint: -
We can use this Checkpoint to verify Properties of Objects like as GUI check point in Winrunner.
Example: - Manual test case.
1) Test case id: TC-id
2) Test case Name: Verify delete button
3) Feature to be test: Flight Reservation
4) Test suite Id: TS-FR
5) Priority: Po
6) Pre-condition: Existing records to be deleted.
7) Test procedure:

Step No
Action
I/P required
Expected

1

2

Focus to Flight reservation window

Open Existing record
-------

ValidOrder No
Delete button Disabled

Delete button enabled

Automation Program:-
Window (“Flight Reservation”).Activate
Window (“Flight Reservation”).Winbutton (“Delete order). Check Checkpoint (“ Delete order”).
Window (“Flight Reservation”).WinMenu (“Menu”). Select “File ; open order….”
Window (“Flight Reservation”).Dialog (“Open order”).WincheckBox (“Order No”). Set “ON”
Window (“Flight Reservation”).Dialog (“Open order”).WinEdit (“Edit”).Set “1”
Window (“Flight Reservation”).Dialog (“Open order”).WinButton (“ok”).Click.
Window (“FlightReservation”).Winbutton (“Deleteorder”).Check Checkpoint (“Delete Order-2”)

Check Point Syntax:-
Window (“WindowName”).Winobject (“ObjectName”).CheckCheckpoint (“CheckpointName”)

Check Point Insertion Navigation:-
Select Position in Script  Insert menu checkpoint
 Standard check point select testable object  click “ok” after confirmation  Select required properties with expected values  click “OK”.
NOTE :-
(a) One check point allows one object at a time unlike WinRunner.
(b) Check point insertion is possible before click stop recording except database
Checkpoint and XMI check point.
(c) Object selection is mandatory before insert any type of checkpoint.
(d) Whenever check point is pass (or) fail, but QTP continues test execution up to end.
(e) If any type of Checkpoint inserted into VB Script QTP is showing a common Syntax as above.
Example 2:- Manual test Case:-

Test Case id : Tc-2
Test case Name: verify “OK” button
Feature to be tested: verify employee recruitment
Test suite ID: Ts_ER
Priority: Po
Pre – condition I/P objects are taking values
Test Procedure

Step no
Action
I/P required
Expected

1

2

3 Focus to Employee window

Enter Employee Name

Select department No ------

Valid value

------
“OK” button disabled.

“OK” button disabled.

“OK” button enabled.

Build :-

Automation Program:-
Window (“Employee”).Activate
Window (“Employee”).Winbutton(“ok).check checkpoint (“ok”)
Window (“Employee”).Winedit (“Empname”).Set “xxx”
Window (“Employee”).Winbutton(“ok).check checkpoint (“ok.2”)
Window (“Employee”).Winbutton(“Department no”).select “xxx”
Window (“Employee”).Wincombobox(“ok).check checkpoint (“ok.3”)

Note1: -
Unlike WinRunner every QTP checkpoint is taking two types of expected values form test engineer’s, such as constant value and parameters (excel sheet column name).
Note2: -
Our checkpoint is executing one tire when our checkpoint expected is constant. Our checkpoint is executing more than one time. Depending on no of rows in excel sheet.
(2) BITMAP CHEKPOINT:-
To compare images, we can use this check point. Unlike use QTP is supporting static and dynamic images for comparison. But test Engineers have to select multimedia option in adding manager to compare dynamic images. QTP supports 10 sec. As maximum play time of images.
Example: Logo Testing
Old Version New Version

Expected Actual
= = Pass
! = Fail
Navigation:-
Open old Version of build  starting recording  open expected image in old version of build Insert menu  Check point  Bit map Checkpoint  show Expected image in old version in build - click “OK” after confirmation - Select area of image if required  Click “OK”  Close old build version  Open new build version  click run- Analyze result manually.

(3) Database Check Point:-
We can use this checkpoint to verify the impact front-end operation on backend tables content in terms data validation and data integrate. This checkpoint option is exactly equal to default checkpoint in database checkpoint of Win Runner.
Example:
 Create database check point (Current content of database tables selected as expected) Valid differences
 Perform front-end operation
 Run database check point (Current content of database tables selected Actual).

To apply data base testing, Test Engineer’s are collecting below information from development team. connectivity name in between fortend and backend in our application build  Names of tables and their column. Screens vs. Tables.
Above information is available Database design document development Team.
Navigation:-
Insert menu  Check point  DB checkpoint  Specified connect to DB using ODBC or Data Junction - Select SQL statement manually  click “Next” click create to select connectivity (Ex.Flight32) write select statement  click finish click “OK” after conformation of Database Table content  Perform Front-end Operation  run Database checkpoint  analysis results manually.

(4) Text Check Point: -
To verify content of an object in terms of match upper case, lower case ignore spaces exact match and text not displayed, we can use these check points.

Navigation: -
Select position Script Insert menu checkpoint  Text checkpoint  select Testable object- click configure if we have to apply testing on selected part object value (using text before and text after)- Select Test (match case, Ignore spaces, exact match , Text not displayed)- click “OK”.

(5) Text Area Check point: -
To Verify content of screen area value in terms of match case, ignore spaces, Exact match, Text not displayed, we can use these check point.

Navigation:-
Select position script Insert menu  checkpoint Text area check point  select value region  click “OK” after conformation  click configure if we have to apply testing on selected part  Select test to be applied  click “OK”.

Control Statements in VB Script:
(a). if Statement :-
If condition Then
-----
------
------
End if
(b) if else if Statement :
If condition Then
-----
------
------
Else if condition2 Then
-----
------
------
Else if condition3 Then
-----
------
------
Else
-----
------
------
End if
(C) While Loop:-
While condition
-----
------
-------
Wend
(D)For Loop:-
For I=1 to n Step 1
-----
-----
-----
Next

(E)Input Statement :-
Input box (“message”)

(F)Output statement

Msgbox(“message”)

(G)Test Result statement:-
Reporter.ReportEvent 0/1, “step name”, “Description”
0 = Pass
1 = Fail

(H) Capture Object value:-
Option explicit
Dim x
X= Window (“Windownames”).Winedit (“Objectname “).getvisibletext

Sample
Example 1: -

Out put = input *100
Automation Program:-

Option Explicit
Dim X, Y
Window (“Sample”).Activate
X=Window (“Sample”).Winedit (“Input”).getvisibletext
Y=Window (“Sample”).Winedit (“Output”).getvisibletext
If Y = X * 100 Then
Reporter.Reportevent 0, “S1”, “Pass”
Else
Reporter.ReportEvent 1, “S1” “fail”
End if

Example 2:- Shopping

Total = Price * quantity

Automation Program:-

Option Explicit
Dim q, p, and tot
Window (“Shopping”).Activate
q=Window (“Shopping”).Winedit (“Quantity”).getvisibletext
p=Window (“Shopping”).Winedit (“Price”).getvisibletext
p= mid (P,2 Len (p)-1)
tot = Window(“shopping”).Winedit(“total”).getvisibletext
Tot=mid (tot, 2, Len (p)-1)
If
Cdbl(tot) = Cdbl (p) * q Then
Reporter.Reportevent 0, “S1” ,“calc is pass”
Else
Reporter. ReportEvent 1, “S1”, “calc is fail”
End if
Note: - Variable declaration and type conversion are mandatory tasks in VB script.
 To convert text value to numberic we can use “Cdbl ( )”
 To convert numeric into value, we can use “Cstr ( )”

Data Driven Testing:-
The re-execution of a test with multiple text data is called data driven testing or retesting or Iterative testing there are 3 types.
(1) From Key board
(2) From front-End objects
(3) From excel sheet.
From Key board:-
Some times test engineer’s are re executing VB Script automation depending on multiple input values through dynamic submission using Key board. To read a value from key board input box ( )
Example: - multiply

Expected:-

Result = input 1 * input 2.

Text data: - 10 pairs of inputs

Automation program:-

Option explicit
Dim I, x, y, r
For I = 1 to 10 Step 1
x=input box (“Enter input1”)
y= input box (“Enter input2”)
Window (“multiply”).Activate
Window (“multiply”).Winedit (“Input1”).set X
Window (“multiply”).Winedit (“Input2”).set Y
Window (“multiply”).Win button (“OK”).click
R = Window (“multiply”).Winedit (“Result”).getvisibletext

If R = X*Y Then
reporter.Reportevent 0, “S1”, “calc is pass”
Else
reporter.Reportevent 1, “S1”, “calc is fail”
End if
Next
Example 2:- Audit

Eepected: - Total – size = No-of-files * file-size.
Test data: - 10 pairs of inputs

Automation program:-
Option explicit
Dim I, x, y, tot
For I = 1 to 10 Step 1
x=input box (“Enter no of files”)
y= input box (“Enter file size”)
Window (“Audit”).Activate
Window (“Audit”).Winedit (“no of files”).set X
Window (“Audit”).Winedit (“file size”).set Y
Window (“Audit”).Win button (“OK”).click
Tot = Window (“Audit”).Winedit (“Total -size”).getvisibletext Tot = mid (tot, 1, Len (tot) – 2)

If Cdbl (Tot) = X*Y Then
reporter.Reportevent 0, “S1”, “calc is pass”
Else
reporter.Reportevent 1, “S1”, “calc is fail”
End if
Next
(2) From Front end objects:-
Some times test Engineer’s are re-executing automation programs depending on multiple objects such as list box, menu, table, data window, activex controls.

Test data

Example :- Insurance

Expected:-
If Type is ‘A’ age is focused, If Type is ‘B’ then gender is focused and if any other Type is Qualification is focused.

Automation program:-
Option explicit
Dim I, x, n
Window (“Insurance”).Activate
N = Window(“Insurance”).Wincombo box(“Type”).getitemcount
For I = 0 to n-1 step 1
X = Window(“Insurance”). Wincombo box(“Type”).getitem(i)
Window(“Insurance”).Wincombobox(“Type”).Select X
If x = ‘A’ Then
Window(“Insurance”).Winedit(“Age”).Check checkpoint (“Age”)
Else if x = ‘B’ Then
Window(“Insurance”).wincombobox(“Gender”).check checkpoint (“Gender”)
Else
Window (“Insurance”).wincombobox(“Qualification”).check checkpoint(“Qualifiacaion”)

End if

Next

STEP GENERATION:-

It is a library of VB Script statement. To search unknown VB script we can follow below navigation

Navigation: -
Insert menu  Step  Step Generator  Select category (Functions, test objects, utility objects)  Select required operation  Fill arguments required  Click “OK”.

(3) FROM EXCEL SHEET:-
In general Test Engineer’s are using Excel sheet oriented data driven test to validate completeness and correctness our build functionality with multiple inputs value because QTP is providing a ready made process for these excel sheet oriented data driven test.

From the above model Test Engineer’s are Populating test data. In excel sheet through import data from database through typing collected data.

Navigation:-
Populate Test data in Excel sheet  convert our manually Test case into automation Program for sample inputs  Tools menu  Data driver  Select sample Input value to Parameterize  Click “Parameterize”  Click “Next”  browse excel sheet column name to replace that sample inputs  click “OK”  Click “finish”.

To fill Excel sheet with data base content, Test Engineer’s are using below navigation.

Navigation:-

Place mouse pointer on Excel sheet  Right click  Sheet  Import  From database- Specify connective  Select specify SQL statement manually  Click “Next”  Click create to select connectivity (Ex:-Flight 32)  Write Select statement to import data from base  Click “finish”.

SYNCRONIZATION POINT:-
After completion of automation program creation with required editing, Test Engineer’s are concentrating on time mapping in b/w Tool and build to conduct complete testing .They are 3 ways to synchronize Tool and build such as

(1) Wait ()
(2) Properties of object
(3) Changes in Settings.

(1) Wait (): -
We can use this function to define fixed waiting time in test Execution.

Syntax:- Wait (Time in seconds)  Wait (10)
(Or)
Wait Time in seconds  Wait 10

This function defines fixed waiting time out, but our application operations are taking variable time to complete.

(2) Properties of Object:-

We can use this concept to define time mapping between Tool and build with the help of changes in properties of objects in our application build.

Example: - Status (or) Progress bar.

100% color filled out  Process completed  able to continue Test Execution
< 100 color filling  In Process  continue Wait state.

Navigation:-
Select Position in Script  Insert menu  Step  Syncronization Point  Select Status (or) progress bar  Click “OK” after conformation  Specified property with Expected value (Enabled True)  Specify maximum time in milliseconds  Click “OK”.

Syntax:-
Window (“Window Name”).win object (“Stausbarname”).Wait property
“Enable”, TRUE, maximum time to wait

(3) Changes in settings:-
Some times our application build is not Supporting wait function and properties of objects like Synconizaiton.
In this situation test Engineer’s are changing the runtime settings of QTP through below navigation.

Navigation:-
Test menu  Settings  Run tab  Change timeout form 20.000 milliseconds to more  Click “Apply”  Click “OK”

Above 3 options are require in automation test Execution when our build background operations are taking more than 20,000 milliseconds of time, because QTS is maintaining 20,000 milliseconds as default time out.

BATCH TESTING:-
In general test Engineer’s are executing automation program as test batches to increase intension of bugs finding.
Every test batch consists of multiple test cases with dependency. One test case End state is base State to next test case, to make batches in QTP .Test Engineer’s are using below statement.

RUNACTION “Action Name [Test name]”

Above statement is applicable on Reusable actions only. A program is created as reusable action, which is callable in other programs (or) Invoke able to other program.

xxxx

SubTest/Reusable Action

From the above diagram Test Engineer’s are giving Reusable action Permission to Corresponding sub test.

Navigation:-
Create automation program individually and same then with Unique test names Open subtest in that programs list (Ex. batch 8a.m) Step menu- Action properties  General tab Select Reusable action checkpoint click “OK”follow above navigation for all sub Test. To give reusable action permissionOpen main Test in that programs listInsert menuCall to existing ActionBrowse corresponding Subtest to call in main test.

Parameter Submission:-
Like as WinRunner, QTP VB Script are also allowing parameters from one to other. Unlike win Runner main test is passing more than one parameter subtest and subtest. is returning more than one output parameters to main test.

Main Test

Subtest

To create above like i/p, o/p parameters we can follow below Navigation.

Navigation:-
Open Subtest Step menu Action properties Select parameters tab Create required no of i/p and o/p ParametersUse that Parameters in required place of Sub test program (Parameter (“Parameter Name”))

Note: - In QTP Test Engineer’s are using reusable Actions Concept for repeatable Operation in Build. Instead of user defined function in Win Runner

ADMINISTRATOR OF QTP TESTS.

(1) Paths of files :-
QTP is maintaining all automation tests in below folder by default.

[C:/program files/mercuryInteractive/QTP/tests/testName (default/name1)]

(2) object repository (or) QTP Architecture:

Like as WinRunner, QTP is also recognize objects and Windows in our application build during recording. In this recognize QTP create Entries for corresponding objects and Windows for future reference.

This all entries are maintaining in a Storage area is called an object repository. This concept exactly Equal to GUI map.

Steps:-
1 to 3 during Recording
4 and 5 during Running

To see and Edit Recognization entries of objects and Windows, We can follow bellow navigation.

Navigation: - Tools menu  object repository

This repository maintains entries of objects and windows in Per test mode only. Unlike Win Runner

Note :- No Extension to VB Script program of Entries files. It support only Per test mode. Does not support Global GUI map Entries.

(2) Changes in object Respository:-
Some times our application objects (or) Windows Labels are variating depending on given i/p values w.r. to customer requirement. To define common ness on that objects and windows labels test Engineers are following below navigation.

Navigation:-
Tools menu  Object Repository  Select corresponding Entry  Click “Browse”  Specify Regular Expression  Select Regular Expression option  Click “OK”.

Example:-

Logical Name: Fax order NO.1 Logical Name: Fax order NO.1
{ {
Class: Window Class: Window
Label: “Fax order No.1” Label: “Fax order No. [0.9]”
} }

(4) Virtual object Wizard:-
Some times the QTP is not able to recognize objects and windows in our application build .Due to the utilization of Advanced Technologies/Unknown Technologies. To recognize that type of object also forcibly. Test Engineers we can follow below navigation.

Navigation :-
Tools menu  Virtual object  New virtual object  Click “Next”  Select expected type depending on the nature of that non recognized object  Click “Next”  Mark that non recognized object area  Click “Next “after conformation  Specify logical Name to that virtual object  Say yes/no to create multiple Virtual objects  Click “Finish”.

NOTE:-
QTP maintains Virtual objects information in a storage area is called virtual object manager.

(5) Objects Identification:-
Some times our application build windows consist of more than one objects as similar. To distinguish this type of objects in test execution. Test Engineer’s are directing QTP with object identification option in tools menu.

Sample

Navigation :-
Tools menu  Object identification  Select object type  Select MSWID (windowId) as assistive property  Click “OK”.

NOTE:-
Windows operating system is maintaining ID’s for Every two objects in our application build.

Logical Name: OK Logical Name: OK-1
{ {
Class: Pushbutton Class: Push button
Label: “OK” Label: “OK”
MSWID: “xxxx” MSWID: “xxxx”
} }

REVOVERY SCENARIO MANAGER:-
This concept is equal to exceptional handling win Runner. Test Engineers are using this concept. To recover form abnormal situation while running test.

QTP allow you to create 4 types of recovery scenario such as

(1) POPUP:- To Skip unwanted window (popup means  Close window)

(2) Object state: To Recover build depending on properties of object (Ex. Status bar)

(3) Test Run Error: To Recover from VB script Runtime

(4) Application Crash: - To open build when that build crashed.

We can follow below steps to create recovery scenario w.r.t our application builds.

Select type of Recovery Scenario

Define Abnormal Situation in our application build

Select Recovery solution

Define Post Recovery to continue remaining test Execution

Save Recovery Scenario for Future Reference..

Navigation to Create recovery Scenario:-
Tools menu  Recovery Scenario manage  Click “New” Scenario icon  Click “Next”  Select Scenario Type  Click “Next”  Enter required details to define Abnormal situation  Click “Next”  Select Recovery type  Enter required details to recover from Abnormal situation  Click “Next “  Select Post Recovery type continue remaining test Execution  Click “Next”  Enter Scenario Name for future reference  Click “Finish”.

Scenario Type :-
Any problem related to build defined through 4 types of Scenario’s.

(1) Pop up Window:-
To delete unwanted window which opened during the test run?

(2) Object state :
To define problem depending on properties of values of object.

(3) Test Run Error:-
To define problem using Runtime Errors w.r.t VB Script.

(4) Application Crash:-
To define problem when an open application build fails during the test Run.

Recovery Type:-
QTP allows you to define 4 Types of recoveries to recover from above defined Scenario (or) problems.

(a) Key board or Mouse Operation :- To defined Recovery

(b) Close Application process: To defined Recovery (Ex :EndTask)

(c) Function call :- To defined Recovery using Reusable actions in QTP

(d) Restart Microsoft windows:- To define Recovery.

Post Recovery Types :-
After Recovery form specified problem during Test Run QTP allows you to Select Post Recovery Types for remaining test execution. There are 6 Types of Post recoveries such as.

(1) Repeat current step and continue.
(2) Proceed to Next Step
(3) Proceed to Next action (or) Component iteration (Ex batch test)
(4) Proceed to Next test iteration means loop (Ex. Data driven test)
(5) Restart current test Run
(6) Stop the test Run.

NOTE 1:- QTP allows you to Export and Import VB Script programs using ZIP process (To store VB Script programs with less amount of space in disk)

NOTE 2: - QTP allows you to Rename Actions in VB Script programs one Action means is a program (or) Path of Program

NOTE 3:- To remove repetation in VB Script statement we can use “With” statement.

Navigation: - Edit menu  Apply “With” statement to Script
 Remove with Statement is also possible.

NOTE4:- Book Marks for Mark in Running

NOTE 5:- Check points are comparing tester given Expected value with Project Actual. But output value statements are returning output state of object without any comparison.

NOTE 6: QTP test allows you to divide one VB Script program into multiple actions.

Navigation:- Insert menu  call to New Action

NOTE 7:- QTP 8.2 is supporting Win Runner launching to Run TSL programs. Wise versa is not possible.

Navigation: - Insert menu  call to Win Runner  Test (or) Function

NOTE 8:- QTP allows you to calculate VB Script execution time using Start and End Transaction point.

Navigation :- Insert menu  Start Transaction

NOTE 9:- QTP allows you to debug VB Script program (F11) as short key.

Navigation: - Debug menu

NOTE 10:- QTP Supports quality center S/W to save VB Script program permanently.

NOTE 11: Object spy used by test Engineer’s to identify reorganization of object (or) window.

Navigation: - Tools menu  Object Spy

WEB TEST OPTION:-
During web functionality testing, Test Engineers are concentrating on more coverage’s than generate application functionality testing such as Links Coverage and Static Test Coverage’s.

To automate these two coverage’s, Test Engineer’s are using below check points in QTP

CASE STUDY:-

Coverage WinRunner7.0 QTP 8.2

HTML Links
(Text link, image Link)

XML Links

Static text Coverage

GUI Check point

NOT Applicable

“get text “ option
Standard check point

XML Checkpoint

Text checkpoint ,Text area check point

NOTE 1:- To automate functionality test in web pages we can select web option in Add- In-Manager

NOTE 2:- During Website testing, development team and testing team are working in an offline mode (offline means Local host (or) Local network)

NOTE 3: QTP is restricting record and own test on specified web site if required.

NOTE 4:- If you create check point on link object, QTP maintains below VB Script maintains.

STATEMENT:-
Browser (“Browser Name”).page (“Page Name”).Link (“Link Name”).check check point (“checkpoint Name”)

NOTE 5:- Win Runner allows Links testing at one link levels (or) cell Links Levels (or) Page Links level.

QTP supports one Link Level or page Links Level.

NOTE 6: QTP Provides Fitter links check in Page Level testing to apply. Check point on all links (or) Selected links in page.

Statement: Browser (“Browser Name”).Page (“Page name”).Check Checkpoint (“Checkpoint Name”)

NOTE 7: To conduct testing on content of web page, Test engineer’s are using text check point (or) text area check point.
These Check point allows you to apply below test on that selected test.

(1)

qtp IV

2008-07-02T10:07:00.001-07:00

QTP Questions

VB Script Syntax (50 Examples)
1 Print Hello World
2 Find whether given number is a odd number
3 Print odd numbers between given range of numbers
4 Find the factorial of a given number
5 Find the factors of a given number
6 Print prime numbers between given range of numbers
7 Swap 2 numbers with out a temporary variable
8 Write a program to Perform specified Arithmetic Operation on two given numbers
9 Find the length of a given string
10 Reverse given string
11 Find how many alpha characters present in a string.
12 Find occurrences of a specific character in a string
13 Replace space with tab in between the words of a string.
14 Write a program to return ASCII value of a given character
15 Write a program to return character corresponding to the given ASCII value
16 Convert string to Upper Case
17 Convert string to lower case
18 Write a program to Replace a word in a string with another word
19 Check whether the string is a POLYNDROM
20 Verify whether given two strings are equal
21 Print all values from an Array
22 Sort Array elements
23 Add two 3X3 matrices
24 Multiply Two Matrices of size 2X2
25 Convert a String in to an array
26 Convert a String in to an array using ‘I’ as delimiter
27 Find number of words in string
28 Write a program to reverse the words of a given string.
29 Print the data as a Pascal triangle
30 Join elements of an array as a string
31 Trim a given string from both sides
32 Write a program to insert 100values and to delete 50 values from an array
33 Write a program to force the declaration of variables
34 Write a program to raise an error and print the error number.
35 Finding whether a variable is an Array
36 Write a program to Convert value into a currency
37 Write a program to Convert an expression to a date
38 Display current date and Time
39 Find difference between two dates.
40 Add time interval to a date
41 Print current day of the week
42 Convert Date from Indian Format to US format
43 Find whether current month is a long month
44 Find whether given year is a leap year
45 Format Number to specified decimal places
46 Write a program to Generate a Random Number
47 Write a program to show difference between Fix and Int
48 Write a program to find subtype of a variable
49 Write a program to print the decimal part of a given number
50 Write a Function to return a random number
51 Write a Function to add and multiply two numbers
52 Write a Sub Procedure to print “Hello World”
53 Write a Sub Procedure to add and multiply two numbers
54 Write a program to list the Timezone offset from GMT

VB Script Advanced Programming (100 Examples)
1 Write a program to read data from a text file
2 Write a program to write data into a text file
3 Write a program to print all lines that contains a word either “infics” or “solutions”
4 Write a program to print the current foldername
5 Write a program to print files in a given folder
6 Write a program to print subfolders in a given folder
7 Write a program to print all drives in the file system
8 Write a program to print current drive name
9 Print the last modified and creation date of a given file
10 Print the size of the file and size on the disk.
11 Write a program to display files of a specific type
12 Write a program to print the free space in a given drive
13 Write a program to display all subfolders in a given folder
14 Write a program to find whether a given folder is a special folder
15 Write a program to remove all empty files in the folder
16 Write a program to Copy contents of one folder to other folder
17 Write a program to check whether a given path represents a file or a folder
18 Write a program to compress a folder
19 Write a program to rename a folder
20 Write program to display all folders created on a specific date
21 Write a Program to enable disk quotas
22 Write a program to create, modify and delete disk quota
23 Write a program to display all files containing “demo” in their name
24 Write a program to print all lines in a file that ends with “world”
25 Write a program to check whether string starts with “Error”
26 Write a program to Replace all words that contains “demo” in a file with the word “infics”
27 Write a program to check whether a string contains only alpha numerics
28 Write a program to check whether a string is in email format
29 Write a program to check whether given string is in date format
30 Write a program to print all the lines ending with '$'
31 Check whether middle three characters in a word contains alphanumeric
32 Check whether a given line is an empty
33 Write a program to Add elements to a dictionary
34 Write a program to display items in a dictionary
35 Write a program to check whether specified Key exists in a Dictionary
36 Write a program to Store dictionary items in an array
37 Write a program to delete Key Value pair in the dictionary
38 Write a program to monitor operating system performance
39 Write a program to monitor operating system objects
40 Write a program to monitor web server performance
41 Write a program to monitor browser service performance
42 Write a program to list the PID and PPID of a process
43 Write a program to create a registry key
44 Write a program to list registry files
45 Write a program to list registry value and types
46 Write a program to delete registry key
47 Write a program to Stop and Start alerter service
48 Write a program to list services running and their statuses.
49 Write a program to list services that can be stopped
50 Write a program to start auto start services that have stopped
51 Write a program to Invoke command prompt and execute dir command from the shell
52 Write a program to schedule a task
53 Write a program to list and delete scheduled tasks
54 Write a program to add a local user account
55 Write a program to disable and delete a local user account
56 Write a program to list all user accounts in the local computer
57 Write a program to display logged in user name
58 Write a program to list cache memory information
59 Write a program to list physical memory properties
60 Write a program to list memory devices
61 Write a program to find Hard Disk size
62 Write a program to find RAM size
63 Write a program to restart a computer
64 Write a program to shutdown a computer
65 Write a program to Execute Perl script from VB Script
66 Find the systems present in the LAN
67 Write a program to Print using remote printer
68 Verify whether IE enhanced security is enabled for logged on user
69 Write a program to add a website to a favourite menu
70 Write a program to list IE LAN settings
71 Write a program to list cache, connection and security zone settings
72 Find the arguments passed to a Windows Script Host
73 Write a program to Map a network drive
74 Write a program to Print to the local printer
75 Write a program to Print to remote printer
76 Write a program to Print Computer name
77 Write a program to Print free memory in the drive
78 Write a program to Print memory and CPU utilized by a process
79 Write a program to Find the ipaddress of a local system
80 Write a program to find Network Drives
81 Write a program to find the Full path name of a shortcut
82 Write a program to Retrieve all the rows in a table
83 Write a program to find the name of columns in a table
84 Write a program to find number of rows in each column
85 Write a program to connect and print data from oracle database
86 Write a program to connect and print data from SQL Server database
87 Write a program to retrieve specific field from the database table
88 Write a program to check whether a column in the database is in ascending order
89 Write a program to insert a new row into the database table
90 Write a program to open the two record sets
91 Write a program to Update the specific field in the database table
92 Write a program to delete all records whose username starts with demo
93 Write a program to sort the record set
94 Write a program to find number of rows in a table
95 Write a program to Write simple text to windows word
96 Write a program to Write table to windows word
97 Write a program to apply style to a table in word document
98 Write a program to open and print a word document
99 Write a program to send an email using outlook
100 Write a program to print data present in all sheets of an excel files

QTP Scripting (100 Examples)
1 Write a program to enter data in login screen
2 Write a program to find the x and y coordinates of a button
3 Write a program to Read items in a list box
4 Write a program to Read items on a desktop
5 Write a program to Capture Desktop Screen shot
6 Write a program to Read tab names from a tabbed window
7 Write a program to Check whether scrollbars exists inside a editor
8 Write a program to check whether edit box is enabled or writable
9 Write a program to Check scroll bars in a web page
10 Write a program to Check whether dialog is middle of the window
11 Write a program to Check whether Window is middle of the screen
12 Write a program to Check whether country contains all the states
13 Write a program to Check whether edit box is focused
14 Write a program to Check default selection in a list box
15 Write a program to Capture webbutton image
16 Write a program to List all links in the web page
17 Write a program to Check whether given link exists
18 Write a program to Find image width and Height
19 Write a program to Print URL displayed in the address bar
20 Write a program to Check whether webpage downloaded completely
21 Write a program to Refresh a web page
22 Write a program to Verify page title is displayed correctly
23 Write a program to Verify whether page contains frames
24 Write a program to Find page load time
25 Write a program to Check given text is displayed on the web page
26 Write a program to Find whether image contains tool tip
27 Write a program to Invoke the Browser with specified URL
28 Write a program to Import an excel file to a Data table
29 Write a program to Read data from first parameter of Global sheet
30 Write a program to Read data from all sheets and all parameters of the excel file
31 Write a program to place data in a specific sheet in the excel file
32 Write a program to Import data to data table from a database
33 Write a program to Read and display data from CSV file
35 Write a program to Find number of rows and columns in a web table
36 Write a program to Display entire data in the web table
37 Write a program to Display all images in the webpage
38 Write a program to Check whether table contains headers
39 Write a program to Find the background colour of a webobject
40 Write a program to Print results in a HTML format
41 Write a program to Select different radio buttons for different script iterations
42 Write a program to Find the dialog Height whose window name is “ Appointments”
43 Write a program to Read all the items from a services window
44 Write a program to Find screen resolution
45 Write function to compare two bitmaps
46 Write a program to Add and Remove Repositories to the action
47 Write a program to Load Library files
48 Write a program to Enable and Disable Recovery scenarios programmatically
49 Write a program to Report Results status to Results file
50 Write a program to Find the active window name
51 Write a program to List out the windows that are open
52 Write a program to Call reusable actions from different script
53 Write your own standard checkpoint
54 Write your own synchronization function
55 Write a program to Check whether there is a memory leak in the process
56 Write a program to Close all the dialogs open in a window
57 Write a program to Read menu names
58 Write a program to Read menu items
59 Write a program to Check whether a check button is selected or not
60 Write a program to Check whether we can select multiple items in the listbox
61 Write a program to Check whether edit box allows exactly 15 characters
62 Write a program to Check whether items in the page are aligned properly
63 Write a program to Check whether data in the webtable is left aligned
64 Write a program to Find which add-ins are loaded.
65 Write a program to Find available add-ins in the tool
66 Write a program to Change window title
67 Write a program to Find whether specified window is there on the desktop
68 Write a program to Check whether a window is in minimized or maximized
69 Write a program to Check window is resizable
70 Write a program to Check whether logo displayed is correct?
71 Write a program to Read all items in a tree
72 Write a program to Read all elements in the XML file
73 Write a program to Read attributes of a particular element in the XML file
74 Write a program to Modify attribute value
75 Write a program to Add one more elements to XML file
76 Write a program to Display complete contents of an XML file
77 Write a program to Find font type.
78 Write a program to Find Font size
79 Write a program to Check whether text is bold and underlined
80 Write a program to Find the memory utilized by a process
81 Write a program to Verify flash image
82 Write a program to Check pointed link is having different back ground colour?
83 Write a program to Check Marquee
84 Write a program to Check whether selected tab is having different appearance?
85 Write a program to Check whether a link contains image to its left side.
86 Write a program to Check whether stock prices are updating an hourly basis
87 Write a program to Retrieve Action Parameters
88 Write a program to Disable active screen programmatically
89 Write a program to Modify Mandatory and Assistive properties programmatically
90 Write a program to Configure Run options programmatically
91 Write a program to Define test results location through program
92 Write a program to Disable Run settings
93 Write a program to Read and Update data from user defined environmental variable
94 Write a program to Configure maximum timeout value for web page to load
95 Write a program to read and delete cookies
96 Write a program to Verify whether status indicator is moving as the movie is playing
97 Write a program to Clear the cache in the webpage
98 Write a program to Check whether webpage is loaded from server or from cache
99 Write a program to Configure web options programmatically
100 Write a program to Instruct Quicktest to Capture Movie Segments of Each Error and Warning
101 Write a program to Check whether new items can be added to a listbox
102 Write a program to Check whether link s pointing to correct URL
103 Write a program to invoke the application
104 Write a program to Read parameters in the data table
105 Write a program to List out the windows that are minimized
106 Write a program to add environmental variables during run time
107 Write a program to check whether tab order is left to right and top to bottom
108 Write a program to find the maximum text length that can be entered in a edit box
109 Write a program to verify min and max length constraints of text in an edit box
110 Write a program to find the kind of data edit box accepts
111 Write a program to add objects to object repository file
112 Write a program to export object repository file to XML
113 Write a program to check whether a column in the database table is a primary key
114 Write a program to display constraints of a column in the database table

qtp III

2008-07-02T10:05:00.000-07:00

What are the types of Object Repositorys in QTP?

QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.
The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

What is QTPro? What is Quick Test Pro? What is Quick Test Professional?

Mercury QuickTest Professional™ provides the industry’s best solution for functional test and regression test automation - addressing every major software application and environment. This next-generation automated testing solution deploys the concept of Keyword-driven testing to radically simplify test creation and maintenance. Unique to QuickTest Professional’s Keyword-driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.QuickTest Professional satisfies the needs of both technical and non-technical users. It enables you to deploy higher-quality applications faster, cheaper, and with less risk. It works hand-in-hand with Mercury Business Process Testing™ to bring non-technical subject matter experts into the quality process in a meaningful way. Plus, it empowers the entire testing team to create sophisticated test suites with minimal training.The deployment of Mercury QuickTest Professional is optimized through the use of Mercury best practices. Mercury best practices cover all aspects of deployment, including product installation and operation, organizational design, process implementation, continual process improvement and measurement of return on investment (ROI). Throughout your implementation Mercury applies these best practices to your specific situation, creating world-class procedures for you that drive long-term success.source

What's New in QuickTest Professional 8.2?
 Keyword View: Lets you easily build and maintain tests without writing VBScripts.
 Auto-Documentation: Provides improved test clarity and the ability to view test steps in plain English.
 Step Generator: Allows you to quickly insert custom-built functions into your tests.
 Mercury Business Process Testing: Enhanced integration with BPT -- Business Components, Scripted Components, and Application Areas.
 Enhanced Expert View: Provides greater efficiency when generalizing test components.
 Action Parameters: Allows you to generalize testing actions for greater reusability.
 Data Parameters: You can now specify test or action parameters to pass values into and from your test, and between actions in your test.
 Open XML Report Format for Test Results: Test results are now stored in an open XML format, enabling you to easily customize the reports according to your own requirements, and to integrate the test result information with other applications.
 Unicode Support: Lets you test global deployments of your enterprise applications.
 Function Definition Generator: You can use the new Function Definition Generator to generate definitions for user-defined functions, add header information to them, and register functions to a test object.

The QuickTest testing process consists of 7 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, QuickTest 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, QuickTest 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.

You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate datasets 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.

QuickTest’s Keyword Driven approach, test automation expert shave full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

Once a tester has run a test, a TestFusion report displays allaspects of the test run: a high-level results overview, an expandableTree View of the test specifying exactly where application failuresoccurred, 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.

QuickTest 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.

QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications.

QTP Tool interface contains the following key elements:

Title bar
displaying the name of the currently open test

Menu bar
displaying menus of QuickTest 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 QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug. Note that this tutorial does not describe how to debug a test. For additional information, refer to the QuickTest Professional User's Guide.

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 QuickTest 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. For additional information, refer to the QuickTest Professional User's Guide.

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

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

Explain the check points in QTP?
A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.
 A page checkpoint checks the characteristics of a Application
 A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
 An object checkpoint (Standard) checks the values of an object on a Application.
 An image checkpoint checks the values of an image on a Application.
 A table checkpoint checks information within a table on a Application
 An Accessibility checkpoint checks the web page for Section 508 compliance.
 An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
A database checkpoint checks the contents of databases accessed by your web site

In how many ways we can add check points to an application using QTP?
We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note: To perform the second one The Active screen must be enabled while recording).

How does QTP identifies the object in the application?
QTP identifies the object in the application by LogicalName and Class.
For example:
The Edit box is identified by
 Logical Name : PSOPTIONS_BSE_TIME20
 Class: WebEdit
QTP Question 15: If an application name is changes frequently i.e while recording it has name “Window1” and then while running its “Windows2” in this case how does QTP handles?
QTP handles those situations using “Regular Expressions”.

QTP II

2008-07-02T10:04:00.000-07:00

1. What is the file extension of the code file & object repository file in QTP?
Ans) for object repositories file the extension is .tsr
for code file the extension is .vbs
2. Explain the concept of object repository & how QTP recognises objects?
Ans) 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.
3. What are the properties you would use for identifying a browser & page when using descriptive programming?
Ans) Title is the property we use.ex: Browser("Title:="xxx").page("Title:="xxxx").....
"Name" would be another property apart from "title" that we can use.
Ex: Browser ("name:="xxx"").page("name:="xxxx"").....
4. What are the different scripting languages you could use when working with QTP?
Ans) Visual Basic Script,XML,JavaScript,Java,HTML
5. Give me an example where you have used a COM interface in your QTP project?
6. Few basic questions on commonly used Excel VBA functions.
7 Explain the keyword createobject with an example.
Ans) Creates and returns a reference to an Automation object . create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by microsoft).
8. Explain in brief about the QTP Automation Object Model.
Ans) Essentially all configuration and run functionality provided via the QuickTest interface is in some way represented in the QuickTest automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in QuickTest have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods.
You can use the objects, methods, and properties exposed by the QuickTest automation object model, along with standard programming elements such as loops and conditional statements to design your program

9. What are the Features & Benefits of Quick Test Pro(QTP)..?
Ans) Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center.
Introduces next-generation “zero-configuration” Keyword Driven testing technology in QuickTest 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 thorough validation of applications through a full complement of checkpoints

10) How to handle the exceptions using recovery secnario manager in QTP?
Ans) You can instruct QTP to recover unexpected events or errors that occured 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

11) what is the use of Text output value in QTP?
Ans) 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.

12) How to use the Object spy in QTP 8.0 version?
Ans) There are two ways to Spy the objects in QTP
1) Thru file toolbar
---In the File Tool Bar click on the last toolbar button (an icon showing a person with hat).

2) Through 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

13) QTP pros and cons
Ans) Pros:
 Will be getting the initial focus on development of all new features and supported technologies.
 Ease of use.
 Simple interface.
 Presents the test case as a business workflow to the tester (simpler to understand).
 Numerous features.
 Uses a real programming language (Microsoft’s VBScript) with numerous resources available.
 QuickTest Pro is significantly easier for a non-technical person to adapt to and create working test cases, compared to WinRunner.
 Data table integration better and easier to use than WinRunner.
 Test Run Iterations/Data driving a test is easier and better implement with QuickTest.
 Parameterization easier than WinRunner.
 Can enhance existing QuickTest scripts without the “Application Under Test” being available; by using the ActiveScreen.
 Can create and implement the Microsoft Object Model (Outlook objects, ADO objects, FileSystem objects, supports DOM, WSH, etc.).
 Better object identification mechanism.
 Numerous existing functions available for implementation – both from within QuickTest Pro and VBScript.
 QTP supports .NET development environment (currently WinRunner 7.5 does not).
 XML support (currently WinRunner 7.5 does not).
 The Test Report is more robust in QuickTest compared to WinRunner.
 Integrates with TestDirector and WinRunner (can kick off WinRunner scripts from QuickTest).
Cons:
 Currently there are fewer resources (consultants and expertise) available due to QTP being a newer product on the market and because there is a greater Demand than Supply, thus fewer employee/consulting resources.
 Must know VBScript in order to program at all.
 Must be able to program in VBScript in order to implement the real advance testing tasks and to handle very dynamic situations.
 Need training to implement properly.
 The Object Repository (OR) and “testing environment” (paths, folders, function libraries, OR) can be difficult to understand and implement initially.

14) what is the difference between test plan and test strategy?
Ans) This is answer to Test strategy. The testing strategy should define the objectives of all test stages and the techniques that apply. The testing strategy also forms the basis for the creation of a standardized documentation set, and facilitates communication of the test process and its implications outside of the test discipline. Any test support tools introduced should be aligned with, and in support of, the test strategy. Whereas the test plan is the requirements definition and design specifications facilitate in the identification of major test items and these may necessitate the test strategy to be updated. A detailed test plan and schedule is prepared with key test responsibilities being indicated

15) Can test automation improve test effectiveness?
Ans) Yes, Automating a test makes the test process:
1.Fast
2.Reliable
3. Repeatable
4.Programmable
5.Reusable
6.Comprehensive

16) How will you choose a tool for test automation?
Ans) choosing of a tool depends on many things ...

1. Application to be tested
2. Test environment
3. Scope and limitation of the tool.
4. Feature of the tool.
5. Cost of the tool.
6. Whether the tool is compatible with your application which means tool should be able to interact with your application
7. Ease of use

17)