learning VB Script for QTP

Learning VBScript for QTP

We can learn the VBScript without QTP also. You need Notepad and command prompt on your system and follow below steps:

1. Create a notepad file.
2. Write a small VBScript in the notepad file.

e.g.

Option Explicit
Dim myResponse
myResponse = MsgBox(“Do you wish to quit?”, 1, “What do you wish to do?”)

1. Save the above Notepad file as Test.vbs.
2. Run above file from the command prompt using CScript.exe.
3. C:\>CScript.exe Test.vbs
4. You will be getting the result of your script.

Descriptive programming in QTP
Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository

Object Identification:
To identify an object during the play back of the scripts QTP stores some properties which helps QTP to uniquely identify the object on a page. Below screen shots shows an example Object repository:Now to recognize a radio button on a page QTP had added 2 properties the name of the radio button and the html tag for it. The name the left tree view is the logical name given by QTP for the object. This can be changed as per the convenience of the person writing the test case. QTP only allows UNIQUE logical name under same level of hierarchy. As we see in the snapshot the two objects in Browser->Page node are “WebTable” and “testPath”, they cannot have the same logical name. But an object under some other node can have the same name. Now with the current repository that we have, we can only write operation on objects which are in the repository. Some of the example operations are given below

Browser(“Browser”).Page(“Page”).WebRadioGroup (“testPath”).Select “2″
cellData = Browser(“Browser”).Page(“Page”).WebTable (“WebTable”).GetCellData (1,1)
Browser(“Example2″).Page(“Page”).WebEdit(“testPath”).Set “Test text” When and

Why to use Descriptive programming?
Below are some of the situations when Descriptive Programming can be considered useful:
The objects in the application are dynamic in nature and need special handling to identify the object. The best example would be of clicking a link which changes according to the user of the application, Ex. “Logout <>”.
When object repository is getting huge due to the no. of objects being added. If the size of Object repository increases too much then it decreases the performance of QTP while recognizing a object.
When you don’t want to use object repository at all. Well the first question would be why not Object repository? Consider the following scenario which would help understand why not Object repository

Scenario 1: Suppose we have a web application that has not been developed yet. Now QTP for recording the script and adding the objects to repository needs the application to be up, that would mean waiting for the application to be deployed before we can start of with making QTP scripts. But if we know the descriptions of the objects that will be created then we can still start off with the script writing for testing

Scenario 2: Suppose an application has 3 navigation buttons on each and every page. Let the buttons be “Cancel”, “Back” and “Next”. Now recording action on these buttons would add 3 objects per page in the repository. For a 10 page flow this would mean 30 objects which could have been represented just by using 3 objects. So instead of adding these 30 objects to the repository we can just write 3 descriptions for the object and use it on any page.Modification to a test case is needed but the Object repository for the same is Read only or in shared mode i.e. changes may affect other scripts as well.
When you want to take action on similar type of object i.e. suppose we have 20 textboxes on the page and there names are in the form txt_1, txt_2, txt_3 and so on. Now adding all 20 the Object repository would not be a good programming approach.

How to use Descriptive programming?

There are two ways in which descriptive programming can be used
By creating properties collection object for the description.
By giving the description in form of the string arguments.By creating properties collection object for the description.To use this method you need first to create an empty description

Dim obj_Desc ‘Not necessary to declare
Set obj_Desc = Description.Create

Now we have a blank description in “obj_Desc”. Each description has 3 properties “Name”, “Value” and “Regular Expression”.

obj_Desc(“html tag”).value= “INPUT”

When you use a property name for the first time the property is added to the collection and when you use it again the property is modified. By default each property that is defined is a regular expression. Suppose if we have the following description

obj_Desc(“html tag”).value= “INPUT
” obj_Desc(“name”).value= “txt.*”

This would mean an object with html tag as INPUT and name starting with txt. Now actually that “.*” was considered as regular expression. So, if you want the property “name” not to be recognized as a regular expression then you need to set the “regularexpression” property as FALSE

obj_Desc(“html tag”).value= “INPUT”
obj_Desc(“name”).value= “txt.*”
obj_Desc(“name”).regularexpression= “txt.*”

This is how of we create a description. Now below is the way we can use it

Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test”

When we say .WebEdit(obj_Desc) we define one more property for our description that was not earlier defined that is it’s a text box (because QTPs WebEdit boxes map to text boxes in a web page).If we know that we have more than 1 element with same description on the page then we must define “index” property for the that descriptionConsider the HTML code given below

Now the html code has two objects with same description. So distinguish between these 2 objects we will use the “index” property. Here is the description for both the object

For 1st textbox:
obj_Desc(“html tag”).value= “INPUT”
obj_Desc(“name”).value= “txt_Name
” obj_Desc(“index”).value= “0”

For 2nd textbox:
obj_Desc(“html tag”).value= “INPUT”
obj_Desc(“name”).value= “txt_Name”
obj_Desc(“index”).value= “1”

Consider the HTML Code given below:

We can use the same description for both the objects and still distinguish between both of themobj_Desc(“html tag”).value= “INPUT”
obj_Desc(“name”).value= “txt_Name”

When I want to refer to the textbox then I will use the inside a WebEdit object and to refer to the radio button I will use the description object with the WebRadioGroup object.Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test” ‘Refers to the text box
Browser(“Browser”).Page(“Page”).WebRadioGroup(obj_Desc).set “Test” ‘Refers to the radio button

But if we use WebElement object for the description then we must define the “index” property because for a webelement the current description would return two objects.

Hierarchy of test description:
When using programmatic descriptions from a specific point within a test object hierarchy, you must continue to use programmatic descriptions from that point onward within the same statement. If you specify a test object by its object repository name after other objects in the hierarchy have been described using programmatic descriptions, QuickTest cannot identify the object.For example, you can useBrowser(Desc1).Page(Desc1).Link(desc3), since it uses programmatic descriptions throughout the entire test object hierarchy. You can also useBrowser(“Index”).Page(Desc1).Link(desc3), since it uses programmatic descriptions from a certain point in the description (starting from the Page object description).However, you cannot use Browser(Desc1).Page(Desc1).Link(“Example1″), since it uses programmatic descriptions for the Browser and Page objects but then attempts to use an object repository name for the Link test object (QuickTest tries to locate the Link object based on its name, but cannot locate it in the repository because the parent objects were specified using programmatic descriptions).Getting Child Object:
We can use description object to get all the objects on the page that matches that specific description. Suppose we have to check all the checkboxes present on a web page. So we will first create an object description for a checkboxe and then get all the checkboxes from the pageDim obj_ChkDesc
Set obj_ChkDesc=Description.Create
obj_ChkDesc(“html tag”).value = “INPUT”
obj_ChkDesc(“type”).value = “checkbox”

Dim allCheckboxes, singleCheckBox
Set allCheckboxes = Browse(“Browser”).Page(“Page”).ChildObjects(obj_ChkDesc)
For each singleCheckBox in allCheckboxessingleCheckBox.Set “ON”

Next
The above code will check all the check boxes present on the page. To get all the child objects we need to specify an object description i.e. we can’t use the string arguments that will be discussed later in the 2nd way of using the programming description.Possible Operation on Description Object Consider the below code for all the solutions
Dim obj_ChkDesc Set obj_ChkDesc=Description.Create
obj_ChkDesc(“html tag”).value = “INPUT”
obj_ChkDesc(“type”).value = “checkbox”

Procedures Fundamentals for VB Script for QTP

Procedures Fundamentals Introduction A procedure is an assignment you ask VBScript to perform besides, or to complete, the normal flow of the program. A procedure is created to work in conjunction with the controls events of a script. There are two kinds of procedures in VBScript: A sub procedure and a function. The difference lies on their behaviors but their coding (programming) depends of your goal. A procedure can be included in the body of an HTML but to separate the script behavior from the rest of the file, it is usually a good idea to include the procedures in the head section of the file. So far, we were not using all parts of a regular HTML file because there was no need for such a structure. From now on, we will respect the normal listing of an HTML file as follows: This is the body of our HTML file. Everything you know about HTML files, their contents and sections, is completely valid here, whether you include a script or not. When adding a script, you can use the head section to "hide" the script (actually, you are not strictly hiding it). As you may know already, there can be various things (such as the This is the body of our HTML file.

Sub Procedures

A sub procedure is a section of code that carries an assignment but doesn't give back a result. To create a sub procedure, start the section of code with the Sub keyword followed by a name for the sub procedure. To differentiate the name of the sub procedure with any other regular name, it must be followed by an opening and closing parentheses. The section of the sub procedure code closes with End Sub as follows: Sub ShowMeTheDough() End Sub The name of a sub procedure should follow the same rules we reviewed for the the variables, omitting the prefix: If the sub procedure performs an action that can be represented with a verb, you can use that verb to name it. Here are examples: show, display To make the name of a sub procedure stand, you should start it in uppercase. Examples are Show, Play, Dispose, Close You should use explicit names that identify the purpose of the sub procedure. If a procedure would be used as a result of another procedure or a control's event, reflect it on the name of the sub procedure. Examples would be: afterupdate, longbefore. If the name of a procedure is a combination of words, start each word in uppercase. Examples are: AfterUpdate, SayItLoud In the following example, a sub procedure named DisplayFullName is created. It retrieves fields of two text boxes (first name and last name) on a form and displays a full name as a result of combining them: Sub DisplayFullName() FullName = FirstName & " " & LastName End Sub As mentioned already, you can declare variables for use in your program. In the same way, you can declare variables in the procedure if you need to. These variables are declared and dealt with in the same way we learned in the regular script sections. Using declared variables, the above procedure can be written as follows:

Sub DisplayFullName() Dim FirstName, LastName Dim FullName FullName = FirstName & " " & LastName End Sub

Calling a Procedure

After creating a procedure, you can call it from another procedure, function, or control's event in the body section of an HTML file. To call a simple procedure such as the earlier DisplayFullName, you can just write the name of the sub procedure. In the following example, the above DisplayFullName sub procedure is called when the user clicks the Detail section of the form: Sub Detailer() DisplayFullName End Sub If you want the procedure to be accessed immediately as soon as the page displays, you can assign its name to the onLoad() event of the body tag.

Arguments

Passing an Argument

To carry an assignment, sometimes a procedure needs one or more values to work on. If a procedure needs a variable, such a variable is called an argument. Another procedure might need more that one argument, thus many arguments. The number and types of arguments of a procedure depends on various factors. If you are writing your own procedure, then you will decide how many arguments your procedure would need. You also decide on the type of the argument(s). For a procedure that is taking one argument, in the parentheses of the procedure, write a name for the argument. Here is an example: Sub CalculateArea(Radius) Dim dblPI Dim dblArea dblPI = 3.14159 dblArea = Radius * Radius * dblPI End Sub A procedure can take more than one argument. If you are creating such a procedure, between the parentheses of the procedure, write the name of the first argument followed by a comma; add the second argument and subsequent arguments and close the parentheses. There is no relationship between the arguments; for example, they can be of the same type: Sub CalculatePerimeter(Length, Height) Dim dblPerimeter dblPerimeter = 2 * (Length + Height) End Sub The arguments of your procedure can also be as varied as you need them to be. Here is an example: Sub DisplayGreetings(strFullName, intAge) Dim Sentence Sentence = "Hi, " & strFullName & ". You are " & intAge & " years old" End Sub

Calling an Argumentative Procedure

We saw already how to call a procedure that doesn't take any argument. Actually, there are various ways you can call a sub procedure. As we saw already, if a sub procedure doesn't take an argument, to call it, you can just write its name. If a sub procedure is taking an argument, to call it, type the name of the sub procedure followed by the name of the argument. If the sub procedure is taking more than one argument, to call it, type the name of the procedure followed by the name of the argument, in the exact order they are passed to the sub procedure, separated by a comma. Here is an example: Sub Result() Dim dblHours, dblSalary CalcAndShowSalary dblHours, dblSalary End Sub Sub CalcAndShowSalary(Hours, Salary) Dim dblResult dblResult = Hours * Salary txtResult = dblResult End Sub Alternatively, you can use the keyword Call to call a sub procedure. In this case, when calling a procedure using Call, you must include the argument(s) between the parentheses. using Call, the above procedure could call the CalcAndShowSalary as follows: Sub Result() Dim dblHours As Double Dim dblSalary As Double dblHours = txtHours dblSalary = txtSalary Call CalcAndShowSalary(dblHours, dblSalary) End Sub

Functions

Creating a Function

A function is an assignment that a piece of code can take care for the functionality of a database. The main difference between a sub procedure and a function procedure is that a function can return a value. A function is created like a sub procedure with a few more rules. The creation of function starts with the Function keyword and closes with End Function. Here is an example: Function FindFullName() End Function The name of the function follows the same rules and suggestions we have reviewed for the sub procedures. To implement a function, remember that it is supposed to return a value. In the body of the function, describe what it is supposed to do. to return the right value, assign the desired value to the name of the function. Here is an example: Function CalculateArea(Radius) CalculateArea = Radius * Radius * 3.14159 End Function A function can also be as complex as performing many and various expressions in order to get a value that can be assigned to the name of the function.

Calling a Function

To call a function, you have two main alternatives. If you want to use the return value of a function in an event or another function, assign the name of the function to the appropriate local variable. Make sure you include the argument(s) of the function between parentheses.

Top software failures of 2011

Top software failures of 2011

1. Financial services giant fined USD25 million for hiding software glitch that cost investors USD217 million.

A software error in the investment model used to manage client assets resulted in this international financial services giant being fined USD25 million by the US Securities and Exchange Commission (SEC). The company also had to repay the USD217 million that backers lost when told that market volatility rather than software failure was to blame for their investment losses.

2. Computer system bugs cause Asian banking facilities' downtime.

Computer system problems at one of Japan's largest banks resulted in a nationwide ATM network of more than 5600 machines going offline for 24 hours, Internet banking services being shut down for three days, delays in salary payments worth USD1.5 billion into the accounts of 620 000 people and a backlog of more than a million unprocessed payments worth around USD9 billion.

3. Cash machine bug benefits customers by giving them extra money.

An Australian bank began giving out large sums of money from 40 cash machines across one city. Officials at the company said they were operating in standby mode, so could not identify the account balances of customers.

4. Leading smartphones suffer an international blackout.

Core and back-up switch failures resulted in network services across Europe, the Middle East, Africa and Latin America going down for three to four days. The blackout left millions without email, web browsing or instant messaging services and were reportedly due to server problems at one data centre, in Slough.

5. Bugs in social networking app for tablet just hours after delayed release.

Just hours after its release, this social networking site's long-awaited tablet app was already receiving reports about minor bugs from clicking through to pages via panel icons to problems posting comments.

6. Twenty-two people wrongly arrested in Australia due to failures in new NZD54.5 million courts computer system.

A new NZD54.5 million (USD42.7 million) computer system linking New South Wales courts and allowing documents to be lodged electronically, led to damages claims for unlawful arrest and malicious prosecution after 3600 defects in the electronic transfer of data from the courts to the police's database led to the wrongful arrest of 22 individuals.

7. 50 500 cars recalled after airbag-related software glitch.

A glitch in the automaker's software design and testing approach, which meant that airbags for passengers in the right rear seat during a crash may not be deployed, resulted in the recall of 47 401 vehicles in the US and a further 3099 in Canada and Mexico.

8. Recall of one million cars addresses fire and rollaway concerns.

A Japanese car company was forced to initiate a worldwide recall of over one million vehicles affected by a design flaw allowing residue from window cleaners to accumulate, which can degrade the switch's electrical contacts and potentially cause a fire over time. This recall followed a global 2.5 million recall by the same company due to design flaws that allowed vehicles to shift out of park and engine stalls.

9. Telecoms glitch affects 47 000 customers' meter readings and costs company NZD2.7 million.

After a software glitch that resulted in customers hitting their data limits early, some 47 000 customers, who were overcharged, were reimbursed by a New Zealand telecoms company in a NZD2.7 million (USD2.1 million) payout.

10. Army computer glitches hinder co-ordinated efforts in insurgent tracking

An army computing system designed to share real-time intelligence with troops in the front line has hindered troops by being unable to perform simple analytical tasks. The USD2.7 billion cloud-based computing network system runs slowly when multiple users are on the system at the same time and the system's search tool made finding the reports difficult as the information mapping software was not compatible with the army's existing search software.

What to expect from Test Management Consultant

• Planning and executing the test process assessments
• Reengineering test processes and recommending the test process improvement strategies
• Helping out clients in implementing the recommended test strategy
• Collaboration with sales to develop proposals/estimates for test process consultancy
• Building a team of tier-2 consultants and managing them
• Determines process efficiencies, and documentation best practices
• Drives business awareness of quality/process methodology
• Lead groups toward common goals; facilitate discussions in group settings
• Serve as a consultant in process improvement to senior management, including techniques such process mapping, procedure development and documentation, etc
• Drive projects focused on business needs, including customer satisfaction, process efficiency, and productivity
• Prepare and present status reports to appropriate stakeholders
• Maintain knowledge of current industry best practices and trends in technology and process and identify ways to apply to current IT practices.
• Different SDLC understanding
• Metrics collection and analysis
• Should have experience in auditing the projects, generating NC reports, tracking them to closure.
• Minimum experience of 4 years in Test management
• Very thorough in the test areas such as defect management, test metrics, test strategy & planning, process improvement initiatives

Step-by-Step Beginners Guide to Project Management

Get the PDF Version

By Lee Iwan

In my experience, projects must; actively involve all the group members, have excellent communication and access to project information, have a shared desired outcome, have specific dates for completion of tasks, and have all the required tools (when needed) in order to finish.

If there is no enthusiasm in the group, your project is dead or doomed to be incredibly dull and tedious.

It's all about very simple questions; what, where, who, how, when, how much, and fixing specific dates and commitments from the group members. The key to success is the leadership and maintaining the level of enthusiasm of the group members, mixed with the correct resources and tools available on time, and a shared sense of urgency in order to bring the project to completion.

Here is a simple outline that may help in organising the project and the participants.

1. Determine the objective and specific desired outcome. Write it down.
2. Identify and organise the people who might be interested or are required in order to bring the project to completion. Ask them to participate, and comment on their level of enthusiasm or belief that the project can or will be successful.
3. Identify a project leader and co-ordinator, this should be accepted by all involved in the project. No consensus, keep trying.
4. Begin "brainstorming" and create scenarios on how to achieve the desired outcome (this may have be broken down into sub-tasks). Make a date when all this creative thinking will be finished and a written draft can be printed and shared.
5. Identify factors that influence or limit the project that are beyond your control (global economic forces, natural disasters, competition, etc.) and factors that are in your control (capital invested, personnel, prices, etc.). Identify the risks or warning flags that might surface. Write this down.
6. Determine and identify the tools (capital, equipment, machinery), the people (administration, sales, suppliers, customers), and the time required to complete the objectives. Write this down.
7. Organise the people involved in the project. Review the proposed project, the factors of influence, the tools, people and time. Determine the best path, tools, time frame, and write it down.
8. Organise the tasks and sub-tasks in chronological order. Write it down.
9. Ask each participant if they are committed to participating in the project, completing their tasks on time and reaching the final outcome. If there is no commitment, find out why and resolve.
10. Develop a list of initial actions and outcomes that must be started and completed. Identify the responsible parties and dates. Write it down.
11. Request specific (realistic) dates for the completion of tasks, sub-tasks and objectives. Write it down.
12. The leader must follow-up on all dates and compromises. Make this information public to all others involved in the project. Communicate all deliveries of sub-tasks, or lack of delivery with the group.
13. Make certain that the group knows the status of the project at all times, everyone should either be waiting for information or the outcome of an ongoing activity, or actively working on obtaining information or finalising an activity.
14. If a group member is unable or unwilling to finish tasks on time, discover why and take immediate action to support or replace the member.
15. For any major problems or setbacks, get the group together to work out new scenarios and dates of completion.
16. Celebrate the big milestones and victories.

Enhance your skill sets in 2012 to become better QA

Quality Training
• Performing Quality Assurance and Control (PMP)
• Planning for Quality (PMP)
• Quality Minded Management (ISO 9000:2000)
• Six Sigma: Quality in Applications
• Six Sigma: Soup to Nuts Overview
• SmarteSoft Load Testing
• SmarteSoft Quality Management
• SmarteSoft Script Test Automation

Information Security
• DIACAP Overview / Implementation
• Ethical Hacking and Penetration Testing
• HIPAA Awareness
• HIPAA Security
• Information Assurance Awareness Course (DoD)
• PCI Compliance Overview
• Vulnerability Management Overview

Web Technologies
• Building an E-Commerce Case
• Evaluating E-Commerce Options
• E-Commerce Security
• E-Commerce Implementation Issues
• Introduction to E-Commerce

Project Management
• Moving from Technical Professional to Management
• Planning Project Scope
• Project Management Essentials
• Project Management for IT Professionals
• Project Management Made Simple
• Strategic IT Planning

Business Analysis
• Analyzing Requirements
• Communicating and Implementing Requirements
• Core Concepts of Business Analysis
• Eliciting Requirements
• Enterprise Analysis and Making a Business Case
• Introduction to Requirements Planning
• Refining and Documenting Requirements
• Requirements Planning and Management

Miscellaneous Training
• MS SQL for Querying
• Oracle 11g Fundamentals
• SharePoint Designer 2007
• SDLC Overview

Specialties

Certifications:
CIW - Ecommerce Specialist
CIW - Foundations
CIW - Site Designer

HIPAA Awareness Certificate
HIPAA Security Certificate
Information Assurance Awareness Certificate