Working with Web Table in QTP

Tables are one of the primary design tools for developing Web Application. Web table object containing number of rows and columns apart from these by using web table we can design sidebars, framing images, navigation bars, titles like we can use web table objects. When we are working with Descriptive Programing using QTP, Web table object is very useful to get data for further activities. A Table containing a number of rows and columns. A Table containing any kind of information in cells in combinations of rows and columns.
        
   

In web table we having some properties to do some actions in excel. The properties are
a) RowCount
b) ColumnCount
c) GetCellData

a) RowCount: By using this method we can get the RowCount (Total number of Rows used in Excel)
Example Script:
Write a Descriptive Program to get the number of rows used in Excel:
Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”)
RC=MyTable.RowCount
Msgbox RC


                                                            (Or)

Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”).RowCount
RC=MyTable
Msgbox RC

b) ColumnCount: By using this method we can get how many columns are used in particular Row

Syntax: ColumnCount (Row)
Write a Descriptive Program to get the number of Columns used in Particular Row
Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”)
CC=MyTable. ColumnCount (3)
Msgbox CC


                                                            (Or)

Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”) .ColumnCount (3)
CC=MyTable
Msgbox CC


c) GetCellData: By using this method we can get particular cell data

Syntax: ColumnCount (Row no, Column no)

Write a Descriptive Program to get the Particular Cell data:
Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”)
GD=MyTable. GetCellData (2, 3)
Msgbox GD


                                                            (Or)

Set MyTable=Browser ("Gmail: Email from Google").Page ("Gmail - Inbox").Web Table ("html tag: =TABLE","name: =t",” X: =173”). GetCellData (2, 3)
GD=MyTable
Msgbox GD


VB Script Initializations


VB Script Variables: Variable is nothing but we are allocating some space to the particular variable to store some information. In variables we are storing the information to that value.
A=10

Here A is Variable Name
 In VB Script we have two types of Variables.

1) User defined Variables
2) Pre-defined Variables.

Variables: 
For example:  a= 1o, dim =10
                       Here a=variable name
                                 10=we are assigning one value to the particular variable.

1) User defined Variables: In user defined variable user will define the variable name.
For example:  a= 1o
                       Here a=variable name
                                 10=we are assigning one value to the particular variable.
 2) Pre-defined Variable: pre-defined variable means Vb Script having default variables those variables are called Pre-defined.

For example:  dim= 1o
                       Here a=variable name
                       10=we are assigning one value to the particular variable.

In this example dim is a pre-defined variable. We can’t use that variable as a user defined variable.

Bug Life Cycle or Defect Life Cycle?

Bug Life Cycle or Defect Life Cycle:

Following is a Diagrammatic Representation of Different phases of Bug Life Cycle
 
 
 

 Today I am going to be share what is Bug Life Cycle or what is Defect Life Cycle and what are types of status are there. Defect Life Cycle is explain entire history of the defect. When it was found, who was founded and now it is which status like these details we will get.

               In Bug Life Cycle or Defect Life Cycle we have different types of Status.

·         New
·         Assigned
·         Open
·         Duplicate
·         Fixed    
·         Verified        
·         Re-Open
·         Closed
·         Deferred

New: When testing team doing testing, testing team will find some Bugs. Whenever testing team will find the Bug they wants to raise the Bug, then only Development team will know what the issue. For that some Organization’s using some tools (Bug zilla, QC).  Some Organization’s using Excel Sheets.

               Whenever testing team will find the Bug they want to raise the Bug, when a defect is logged and posted for the first time then we can, Status is NEW.

Assigned: Once the testing team posted a BUG, and then development team lead will check and assign that bug to his team. At they set status Assigned.

OPEN: Once the defect is raised, automatically mail will generate to the Assigned Person. While raise the Bug at the time only testing team to will assign whom we are going to be Assign the Bug. For that we have one option “Assigned to”. Then The Assigned Person will open the Bug and try to fix the Bug. At the they will change the status “OPEN”. By using theses Status we can track the Bug is in which Status.

Duplicate: Sometimes testing team will open same bug more than one time. When development team open the bug to fix, if they identified the raised bug is already logged then they will set the status as Duplicate.

Fixed: Once the Development team is fixed the Bug, they will change the status as “Fixed”. Then testing team will do Re-testing based on the output testing team will “Re-open or Close” the defect.

Verified: Once the defect is fixed by the Development team then testing will verify the modified code. May be it will take some time to verify that code at the Testing team will set the Status as Verifying.  If the modified code is working  is working based on the Requirement Testing team will set the status  “Closed”, Otherwise testing team will  Re- Open the Defect.

Re-Open: After fixing the Bug, testing team will do Re- testing the Application based on the Output testing team will Re-Open or Close the defect. If the application is not working based on the Requirement then testing team will Re- Open the Defect.

Close:  If the application is working based on the Requirement then testing team will close the Defect.

Deferred: If the bug is changed to deferred state means the bug is expected to be fixed in next releases.