Post defect to QC

Set TDConnection = CreateObject("TDApiOle.TDConnection")
TDConnection.InitConnection "http://testdb/tdbin" 'DB URL
TDConnection.ConnectProject "projectname","username","password"
If TDConnection.Connected Then
 reporter.reportevent micPass,"Connection","Connection successful"
Else
 reporter.reportevent micFail,"Connection","Connection Failed"
End If
Set BugFactory = TDConnection.BugFactory
Set Bug = BugFactory.AddItem (Nothing)
Bug.Status = "New"
Bug.Summary = "Connecting to TD"
Bug.Priority = "4-Very High"
Bug.AssignedTo = "admin"
Bug.DetectedBy = "admin" 
Bug.Post

Batch Execution

Executing a group of Tests or series of tests at a time is known as Batch Execution. 

To perform Batch execution, QTP provides a separate Tool called Test Batch Runner. 

Steps for Batch Testing: 
1) Create Individual Tests and Run once. 
2) Open 'Test batch Runner' Tool and Form Batches

• Launch Test Batch Runner. 
• Navigation: Start>program>quicktest professional>Tools>Test Batch Runner>File>new>batch>add>browse path of the test (like this add number of tests)>save with MTB extension (Module test batche)>close test batch runner. 

3) Provide permission to 'Test batch Runner' to run tests 
4) Run or Execute Test Batches from Test Batch Runner
Navigation: File>open>browse path of the test batch>batch>run 
5) View Test wise Result in 'Test Result Viewer'

Note:

1. QTP doesn’t provide Batch wise result. 
2. Test Batch Runner launches QTP Tool, QTP runs Tests one by one. 
3. Allowing other products to Run Tests. Navigation: Tools>Options>Run>check allow other mercury products>apply & Ok 

Executing partial Test Batch: Open Test Batch Runner >open Test Batch>Select or deselect tests>run test batch.

Utility Objects

QTP Provides the several utility objects to enhance the power of scripting.Utility Objects are the reserved objects in qtp.These objects can be used in reporting preferences during run time. There are various Types of Utility Objects: 1)Crypt Object 2)DataTable Object 3)Description Object 4)DotNetFactory Object 5)DTParameter Object 6)DTSheet Object 7)Environment Object 8)Extern Object 9)LocalParameter Object 10)MercuryTimers Object (Collection) 11)MercuryTimer Object 12)Parameter Object 13)PathFinder Object 14)Properties Object (Collection) 15)QCUtil Object 16)RandomNumber Object 17)Recovery Object 18)Reporter Object 19)RepositoriesCollection Object 20)Repository Object 21)Services Object 22)Setting Object 23)SystemMonitor Object 24)TextUtil Object 25)TSLTest Object 26)XMLUtil Object

Mouse right click for context menu

The below code right clicks on a link in a page named “Document” and selects “CreateDocument” in the context menu. Each option in the menu belongs to WebElement class. 'set the path to an object Set pathObj = Browser(“objBrowserName”).Page(“objPageName”) 'Create an object of DeviceReplay class which helps us simulate mouse click operation Set deviceReplay = CreateObject(“Mercury.DeviceReplay”) 'Get the X-axis value of the link getX = pathObj.Link(“Document”).GetROProperty(“abs_x”) 'Get the Y-axis value of the link getY = pathObj.Link(“Document”).GetROProperty(“abs_y”) 'Simulates the right click operation over the link deviceReplay.MouseClick getX,getY,RIGHT_MOUSE_BUTTON 'Click on the “CreateDocument” option. pathObj.WebElement(“name:=CreateDocument”).Click Set deviceReplay = Nothing

Test Estimation template

This template can be used to estimate the tasks given the resources and other parameters


Download Test estimation template

Risk Register

This template can be used to track and maintain the list of risks in an organization.


Download Risk Register

Testing checklist

Check list for the testing team

Product:

Version:

Date:

Checklist Item	Yes/No/NA
1.    Is the release notes prepared and shared?
2.    Are the requirements that are implemented documented?
3.    Has knowledge transfer happened on the critical aspects?
4.    Is the unit testing done by the developers?
5.    Is the testing strategy defined and accepted?
6.    Are the dependencies documented and shared to the testing team?
7.    Are the assumptions documented and shared to the testing team, if any?
8.    Is the environment setup clear to the testing team?
a.    different software required
b.    hardware required
c.    network connections required
d.    installation procedure
e.    credentials required etc.
9.    Are all the known issues documented and shared to the testing team?
10.  Are the milestones identified and accepted?
11.  Is a POC (Point of contact) identified to address the clarifications from the development team and testing team?
12.  Is the testing life cycle defined and accepted?
13.  Are all the defect ids that were fixed are documented and shared?
14.  Are any SLAs identified and accepted?

Reviewed By:

Date: