Ans: The steps to handle pop-up exceptions are.

• Select the recovery scenario manager
• Press the new scenario
• Click next
• Select the pop-up execution
• Select the pop-window which we want to handle (capture) by clicking the spy button
• Press next
• Select the specified option like keyboard or mouse operation press next.
• Select the specified option click default or press enter
• Click next and uncheck add another recovery operation
• Click next and select proceed next step.
• Click next and give the scenario name and description
• Click next and select add scenario to current test and add scenario to default setting. Click finish afterward save the scenario.
   

Ans: The new version of HP Quick Test Professional is 10.0 and it is known as Atlantis.

Ans: It contains the following key elements: Title bar, displaying the name of the currently open test, Menu bar, displaying menus of Quick Test commands, File toolbar, containing buttons to assist you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first time. You can display the Debug toolbar by choosing View? Toolbars? Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View? Toolbars? Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View, Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameter zing 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.

Ans: Create object: Creates and returns a reference to a dynamic object. Example set Excel sheet= Create Object (“Excel. Sheet”)

Ans: To pre-configure test settings before executing the QTP test.

Ans: We can record popup window using Record and Playback method for negative testing.

In recovery scenario, we record popup window only when we want to prevent our application from crash by unexpected popup window.

For suppose our application is web base application and we are writing login script. And after entering correct credential user is able to login. But due to bug now user is unable to login and after click on submit button popup window is displaying. For this type unexpected behavior, we can create a popup handler script on all submit button and also we can user recovery scenario to handle this situation.

Ans:
Public: In any testing tool not only the QTP if we declare as a public then we can use that variable to any function within the script.

Private: we can use that variable within the function.

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

Ans: 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 difference 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, test that corresponds to a given application interface or set of objects.

You do not expect to frequently modify test object properties.

You generally crate single action tests.

You have several tests that test elements of the same application, interface or set of the objects.

You expect the object properties in your application to change from time to time 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 call to action options.

Ans: Actually my requirement is, query should be parameterized. i.e., query should be in the script and also it should change dynamically. I.e. i have to pass different values in the query condition field based on different criteria’s. (Where condition)

In this procedure (Which you have mention)?can we change the SQL query? If we can plz let me know once.

For this i? Am following the below process (Which ? Came to know? recently). Here i am giving the procedure. Plz check it once.

1.Connect to the database:????????????

strCon="Driver={Microsoft ODBC for Oracle}; " &_

"CONNECTSTRING = (DESCRIPTION = " &_

"(ADDRESS = (PROTOCOL = TCP)" &_

"(HOST=XXXX) (PORT=XXXX))" &_

"(CONNECT_DATA = (SERVICE_NAME=xxxxxxx))); uid=xxxxx;pwd=xxx;"

2. Open the database connection

Set oCon=Create Object ("ADODB.Connection")

3.? Create the record set object

Set oRs=Create Object("ADODB.Recordset")

4.?Define the Parameterized SQL query

strQuery="Parameterized query"

5. Execute the query

Set oRs=oCon. Execute (strQuery)

After that we can manipulate the record set values accordingly.