QTP Interview Questions

1. Can I change D Active Screen page which is shown on every new test?
This page can B changed 2 B any valid HTML page. D page can B located either locally or on D network.
For example, if U want your entire organization 2 view D same Active Screen page when they open QTP, U should open D NewTest.inf file located under D dat\snapshots directory of QTP and set D next line:FileName1=FileName1=\\mercury\public\MainPage.html

2. How 2 create an action template?
You can create a template action script tat will B used on every new action tat is created. U can use this, 4 example, 2 add a header comments 2 each action.
To create D template action U should create a text file with D name ActionTemplate.mst and place it under QTP dat folder.

3. How 2 pass parameters when calling actions?
You can pass information between actions in several ways:
1. Using D new Action Parameters feature in Quick Test 8.0
2. Putting D variable in D data table and then accessing this data table 4m D called action.
3. Defining D variable as an environment variable tat can B accessed 4m D entire test.

4. How 2 configure D report 2 show only error (by default)?
You can configure D report 2 show only error by default by adding D following section 2 D QTReport.ini file (located under QTP bin directory).[FilterDialog]ReportAppDefaultFilter=1 # 4 error onlyReportAppDefaultFilter=3 # shows all messages (default)

5. How 2 use Environment variable?
QuickTest supports using environment variables. Environment variables can B either system variables or user defined variables.
You can define D user defined variables in an external file which will B read by QuickTest when it will B launched.
See D Using Environment Variables section in D QuickTest Professional help.

6. Does QuickTest have any debugging capabilities?
In order 2 debug tests U must install D Microsoft Script Debugger. If U did not download and installed it while installing QuickTest, D debugger can B still downloaded 4m D Microsoft Script Technologies site. After downloading it, double-click on D self-extracting executable and follow D instructions on your screen.
Once D Script Debugger is installed, an arrow points 2 D current step tat is being executed in D Tree View and D Expert View. U can then use D debugger 2 view local action variables, use D command window, view D objects properties, and more.
More information can B found in D QuickTest User's Guide.

7. What command-line arguments can I use when launching QuickTest?
Please refer 2 D QuickTest Command Line utility 4 more information on how 2 run QuickTest using a command line.

8. I have a Microsoft Access database tat contains data I would like 2 use in my test. How do I do this?
The powerful 'Expert View' allows U 2 access databases using ADO and ODBC. Below is a sample test tat uses D information contained in D Authors table of a database 2 search 4 books written by D author.Dim MyDB
Dim MyEng
Set MyEng = CreateObject("DAO.DBEngine.35")
Dim Td
Dim rs
' Specify D database 2 use
Set MyDB = MyEng.OpenDatabase("BIBLIO.MDB")
' Read and use D name of D first 10 authors
Set Td = MyDB.TableDefs("Authors")
Set rs = Td.OpenRecordset
rs.MoveFirst
For i = 1 2 10
Browser("Book Club").Page("Search Books").WebEdit("Author Name").Set rs("Author")
Browser("Book Club").Page("Search Books").WebButton("Search").Click
Next

9. How do I add a manual wait step 2 my test?
A manual wait (think time) can B added 2 a QuickTest test using D following command:Call Wait()


10. How do I make D test prompt D user 4 input while it is running?
The VBScript InputBox function allows U 2 display a dialog box tat prompts D user 4 input and then continue running D test. U can use D value tat was entered by D user later on in D test. See D VBScript reference manual 4 more information on D InputBox function.
The following example shows D InputBox function used 2 prompt D user 4 D password.Browser("Mercury Tours").Page("Mercury Tours").WebEdit("username").Set "administrator"
Passwd = inputbox ("Enter password", "User Input")
Browser("Mercury Tours").Page("Mercury Tours").WebEdit("password").Set Passwd

11. How 2 remove result files 4m old tests?
You can use D Test Results Deletion Tool 2 view a list of all D test results in a specific location in your file system or in a Quality Center project. U can then delete any test results tat U no longer require.
The Test Results Deletion Tool enables U 2 sort D test results by name, date, size, and more, so tat U can easily identify D results U want 2 delete.
You can find this utility in D Start Menu > QuickTest Professional > Tools > Test Results Deletion Tool.

12. How 2 change D logical name of a Test Object?
When recording an object QuickTest Professional uses one of D object's properties as D logical name 4 D object (the name displayed in D Expert View and in D KeywardView modes).
You can change D property tat is used 2 B a different one by specifying which property's value U want 2 use as D logical name 4 D object.
For example in order 2 use D alt property as D logical name of an image, run regedit.exe and set D following information:[HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\QuickTest Professional\MicTest\Test Objects\Image]
"tag query name"="alt"

13. Changing D Mic.ini file
Some of QuickTest Professional information is stored in a text file which is called mic.ini. This file is located under D QuickTest bin directory.[SectionA]NameA=ValueA
To enter D above change 2 D mic.ini file U should perform D following:
1. Open D mic.ini file located under D QuickTest Professional bin directory using any standard text editor
2. Search 4 section name (in this case 'SectionA'). If it does not exists - add it 2 D end of D file
3. If D line (beginning with D NameA text) exists in D section, then change D value 2 B ValueA
4. If D line does not exist add it 2 D end of this section (before D next Section begins)

14. How 2 change D registry?
Note: Errors in D correct editing of D registry may cause severe malfunction 2 D operating system.[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\KeyA]"ValueA"=dword:0000001"ValueB"="StringValue"
In order 2 enter D above change 2 D registry, U should do D following:
1. Open regedit (type regedit in D Start>Run dialog)
2. Navigate 2 D specified path (in this case navigate 2 HKEY_CURRENT_USER > Software >...>KeyA)
3. If D path does not exists, right click on D right pane, choose Key and enter D missing key name
4. If D value does not exists, right click on D right pane, choose DWORD value or String value and enter D missing variable name
5. Right click on D variable, choose Modify and change D value 2 D correct one

15. How 2 record on non standard menus?
In QuickTest Professional 8.0 U can decide how do U want QuickTest 2 behave while recording on menus 4m D UI.This option is available in D "Advanced Windows Application Options" dialog 2 B found underTools > Options > Windows Applications > Advanced.
More information can B found in D QuickTest User's Guide.

16 How 2 terminate an application tat is not responding?
You can terminated any standard application while running a script in QuickTest.If U want 2 terminate D application, just set this line:
SystemUtil.CloseProcessByName "app.exe"
or
SystemUtil.CloseProcessByWndTitle "Some Title"
Where can I find information on D IE Document Object Model?
You can find more information on D IE DOM in D following links:
Document object: http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_document.asp
Other HTML Objects: http://msdn.microsoft.com/workshop/author/dhtml/reference/objects.asp
General DHTML reference: http://msdn.microsoft.com/workshop/author/dhtml/reference/dhtml_reference_entry.asp

17. How 2 configure QuickTest 2 record on Embedded HTML Controls?
In order 2 B able 2 record context sensitive operations on Embedded HTML Controls (an application which contains an embedded IE HTML viewer), U will need 2 set D following
Add 2 D ie_hook section in mic.ini (located under QuickTest bin directory) D following lines:[ie_hook]myapp.exe=yes (where myapp.exe is D executable name of D application U want 2 test)you should change D following setting in D registry:[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Hooks\myapp.exe]"bbHook"=dword:00000001
"GetMessageHook"=dword:00000001
"WndProcHook"=dword:00000001

18. How do I launch a new browser 4m a test?
A new browser window (and any other application) can B launched 4m within a test by adding D following step 2 your test:SystemUtil.Run "iexplore.exe", http://www.mercuryinteractive.com/

19. How 2 access D HTML tags directly?
QuickTest provides direct access 2 D browser's Document Object Model (DOM) through which U may access D HTML tags directly. Access 2 D DOM is done using D .Object notation. U can find more information about D DOM on D Microsoft Web Workshop web site.
The test below demonstrates how 2 iterate over all D tags in D page. D test then outputs D inner-text of D tags (the text contained between D tags) 2 D report using D Reporter object.We need D on error because not all D elements have inner-text
On Error Resume Next
Set Doc = Browser("CNN Interactive").Page("CNN Interactive").Object
' Loop through all D objects in D page
For Each Element In Doc.all
TagName = Element.TagName ' Get D tag name
InnerText = Element.innerText ' Get D inner text
' Write D information 2 D report
Reporter.ReportEvent 0, TagName, InnerText
Next

20. Where can I find a web page's cookie?
The cookie used by D browser may by accessed through D browser's Document Object Model (DOM). D following example returns D cookie collection 4m D browser. U can find more information about D DOM on D Microsoft Web Workshop web site.Browser("Flight reservations").Page("Flight reservations").Object.Cookie

21. Changing D Mic.ini file
Some of QuickTest Professional information is stored in a text file which is called mic.ini. This file is located under D QuickTest bin directory.[SectionA]NameA=ValueA
To enter D above change 2 D mic.ini file U should perform D following:
1. Open D mic.ini file located under D QuickTest Professional bin directory using any standard text editor
2. Search 4 section name (in this case 'SectionA'). If it does not exists - add it 2 D end of D file
3. If D line (beginning with D NameA text) exists in D section, then change D value 2 B ValueA
4. If D line does not exist add it 2 D end of this section (before D next Section begins)

22. How 2 change D registry?
Note: Errors in correct editing of D registry may cause severe malfunction of D operating system.[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\KeyA]"ValueA"=dword:0000001"ValueB"="StringValue"
In order 2 enter D above change 2 D registry, U should do D following:
1. Open regedit (type regedit in D Start>Run dialog)
2. Navigate 2 D specified path (in this case navigate 2 HKEY_CURRENT_USER > Software >...>KeyA)
3. If D path does not exists, right click on D right pane, choose Key and enter D missing key name
4. If D value does not exists, right click on D right pane, choose DWORD value or String value and enter D missing variable name
5. Right click on D variable, choose Modify and change D value 2 D correct one

23. How 2 change D template test which is used by Quality Center 2 create new tests?
When creating a new test 4m Quality Center, D test is based on a template test which is located under "bin/TD2000" directory under D "TestDirector Plugins" installation.
You can replace this test 2 contain D test template tat U wish 2 B used.
Note tat if U change D test 2 use a QuickTest Professional 6.0 (or later) template test then this test can not B opened in Astra LoadTest 5.x

24. How 2 change D manual template test which is used by Quality Center when converting manual tests 2 QuickTest test?
When U have a manual test defined in Quality Center and U want 2 create 4m it an automatic test, U can control D way this automatic test will B created.
You can edit D ManualTemplate.txt file located under "bin/TD2000" directory under "TestDirector Plugins" installation 2 contain D steps which U want 2 B generated in D QTP test 4 each manual step.

25. How 2 close QuickTest after runs when running 4m Quality Center?
When running multiple QuickTest Professional tests 4m Quality Center U can specify tat U want 2 close QTP after specific amount of tests which r executed.
To do so, U should add 2 D end of D mic.ini file (located under D bin directory of QTP installation) D following lines:[RemoteAgent]CloseToolAfterRuns=

26. How 2 configure which add-ins will B loaded when working with Quality Center?
Note: 4m QTP 6.5 version D test is opened with D correct add-ins, D settings below can B used with older versions.
When Quality Center launches QuickTest Professional 2 run tests, then by default QTP is loaded with all add-ins which r installed on D machine. If U want QTP 2 B loaded with D last add-ins configuration which was opened on this specific machine U should change D following value in D registry of D machine which QTP is running on:[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\AddIn Manager]"SilentModeWithPredefinedAddIns"=dword:0000001
Click here 4 information on how 2 change D registry

27. How 2 open Quality Center connection dialog faster?
You can launch D Quality Center connection dialog by double clicking on D right pane of D status bar of either QuickTest or D Report.
How do I use QuickTest together with Quality Center?
Quality Center is a powerful test management tool tat enables U 2 manage and control all phases of software testing. It provides a comprehensive view of D testing process so U can make strategic decisions about D human and material resources needed 2 test an application and repair defects.
Quality Center and QuickTest work together 2 integrate all aspects of D testing process. In QuickTest, U can create tests and save them in your Quality Center project database. After a test has been run, D results r viewed and analyzed in Quality Center.
For more information on using QuickTest and Quality Center together, please refer 2 D QuickTest User's Guide.

28. Changing D Mic.ini file
Some of QuickTest Professional information is stored in a text file which is called mic.ini. This file is located under D QuickTest bin directory.[SectionA]NameA=ValueA
To enter D above change 2 D mic.ini file U should perform D following:
1. Open D mic.ini file located under D QuickTest Professional bin directory using any standard text editor
2. Search 4 section name (in this case 'SectionA'). If it does not exists - add it 2 D end of D file
3. If D line (beginning with D NameA text) exists in D section, then change D value 2 B ValueA
4. If D line does not exist add it 2 D end of this section (before D next Section begins)

29. How 2 change D registry?
Note: Errors in correct editing of D registry may cause severe malfunction of D operating system.[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\KeyA]"ValueA"=dword:0000001"ValueB"="StringValue"
In order 2 enter D above change 2 D registry, U should do D following:
1. Open regedit (type regedit in D Start>Run dialog)
2. Navigate 2 D specified path (in this case navigate 2 HKEY_CURRENT_USER > Software >...>KeyA)
3. If D path does not exists, right click on D right pane, choose Key and enter D missing key name
4. If D value does not exists, right click on D right pane, choose DWORD value or String value and enter D missing variable nameRight click on D variable, choose Modify an

4.3 When testing should occur?

Testing can and should occur throughout the phases of a project.

Requirements Phase
· Determine the test strategy.
· Determine adequacy of requirements.
· Generate functional test conditions.

Design Phase
· Determine consistency of design with requirements.
· Determine adequacy of design.
· Generate structural and functional test conditions.

Program (Build) Phase
· Determine consistency with design.
· Determine adequacy of implementation.
· Generate structural and functional test conditions for programs/units.

Test Phase
· Determine adequacy of the test plan.
· Test application system.

Installation Phase
· Place tested system into production.

Maintenance Phase
· Modify and retest.



10.0 Defect Tracking Process

The Defect Tracking process should answer the following questions:
When is the defect found?
2. Who raised the defect?
3. Is the defect reported properly?
4. Is the defect assigned to the appropriate developer?
5. When was the defect fixed?
6. Is the defect re-tested?
7. Is the defect closed?

The defect tracking process has to be handled carefully and managed efficiently.

The following figure illustrates the defect tracking process:
The Tester/Developer finds the Bug.
Reports the Defect in the Defect Tracking Tool. Status “Open”

The concerned Developer is informed
The Developer fixes the Defect
The Developer changes the Status to “Resolved”
The Tester Re-Tests and changes Status to “Closed”
If the Defect re-occurs, the status changes to “Re-Open”
Defect Classification

This section defines a defect Severity Scale framework for determining defect criticality and the associated defect Priority Levels to be assigned to errors found software.

The defects can be classified as follows:

Classification
Description
Critical
There is s functionality block. The application is not able to proceed any further.
Major
The application is not working as desired. There are variations in the functionality.
Minor
There is no failure reported due to the defect, but certainly needs to be rectified.
Cosmetic
Defects in the User Interface or Navigation.
Suggestion
Feature which can be added for betterment.


Priority Level of the Defect

The priority level describes the time for resolution of the defect. The priority level would be classified as follows:

Classification
Description
Immediate
Resolve the defect with immediate effect.
At the Earliest
Resolve the defect at the earliest, on priority at the second level.
Normal
Resolve the defect.
Later
Could be resolved at the later stages.