Jaanu Jeeva: March 2009

10 steps to become QTP guru

Would you like to know how to become QTP guru?
The recipe is simple. You should learn the following:

VBScript
QTP uses VBScript language. That's why strong knowledge of VBScript is 'must have'.
Sources:
- w3schools' VBScript tutorial
- MS' VBScript Guide.
Software Testing Automation Frameworks
To write good automated tests, you should know how to write them.
There are different approaches and solution. There is not a silver bullet.
Sources:
HP QuickTest Professional Tutorial
This QTP tutorial cames with QTP.
It's quite clean and informative. Its main goal is to show and explain basic concepts of QuickTest Professional. It provides knowledge on:
- creating a test
- working with Object Repository (OR)
- running and analyzing tests
- verifying tests
- parameterizing, etc
Sources: '\help\QTTutorial.pdf' or '\help\Tutorial.chm' in QTP Install folder.
HP QuickTest Professional User's Guide
As previous tutorial, the present User's Guide come with QTP install too.
This guide is intended for QuickTest Professional users at all levels. It gives a deeper
knowledge on:
- working with QTP Object Repositoies
- designing tests
- enhancing tests (checkpoints, parameterizing, etc)
- maintaining anf debugging tests
- advanced testing features, etc
Sources: '\help\QTUsersGuide.pdf' or '\help\MainUsersGuide.chm' in QTP Install folder.
COM/DCOM Technologies
When working with QTP, you will be closely linked with such Microsoft's applications, as: Excel, Word, Outlook. So, I recommend to get familiar with COM, COM Technologies, and COM objects of:
SQL
SQL is so important in programming, that I strongly recommend to spend time to learn SQL:
- concepts of RDBM
- selecting/updating/deleting data
- SQL queries optimizations
- databases administration
Sources:
- w3schools' SQL tutorial
- MS SQL Server - this and this
- Oracle DB
XML
XML is an extremely popular and useful format. I'm sure that нou will have to deal with data, stored in XML-files.
Sources:
- w3schools' XML tutorial
HTML, DOM
Since QuickTest Professional works perfectly with web applications, you should be expert in related fields - HTML, HTTP, DHTML, DOM, etc. They will simplify your future QTP script and make them more reliable and maintenable.
Sources:
HP QTP Knowledge Base
It contains a lot of practical articles about QuickTest Professional.
You can find there QTP webinars, QTP FAQs, documentations, solutions of your problems or different ways how to improve your QTP automated tests.
Sources:
- HP Self-solve Knowledge Search (requires an access to HP site)
Useful sites
Sure, it's impossible to know all information on QTP.
That's why I recommend to use these two sites to search answers to your QTP questions:
- Google
- Easy way to automate testing

LoadRunner tutorials

LoadRunner parameters:

LoadRunner correlation:

Recording:

LoadRunner Controller:

How to run LoadRunner Controller from command line?

LoadRunner Analysis:

How to automatically create custom HTML report in LoadRunner Analysis from command line?

LoadRunner & QTP integration:

How to execute QTP script from LoadRunner?

Content verification:

Monitoring:

How to detect memory leaks with LoadRunner - visual tutorial

LoadRunner coding/scripting:

LoadRunner unique file names:

Mercury Quality Centre is a web-based test management tool. It gives you a centralized control over the entire testing life cycle. It gives an easy interface to manage and organize activities like Requirements coverage, Test Case Management, Test Execution Reporting, Defect Management, and Test Automation. All these activities are provided from a single tool, which is web-based and can be accessed from any where. Hence, making the task of the testers and managers easy.

Mercury Quality Centre can be divided into two parts:

Site Administrator Bin
Quality Centre Bin

Site Administration Bin: It is the starting point for the usage of Mercury Quality Centre. This part is used for all the administrative activities. Password for site admin is defined during the installation so make sure that you remember the password during installation. From this part of Mercury Quality Centre, we generally do the following activities:

Creating the projects
Assigning users to the projects
Creating specific roles
Configuring QTP or Winrunner scripts to use from Mercury Quality Centre
Configuring the mail servers
Verifying licensing information
Information about database

Note: If you are using Winrunner, you need to make sure that backward compatibility property of the application to true.

Quality Center Bin: This part of Mercury Quality Centre gives functionality of almost everything that as a tester or test manager you need to do in your day to day activity apart from execution. This is the most common interface used by the customers or users. In this part, we generally do the following activities:

Creating test plans
Defining requirements
Creating test cases
Creating test labs
Associating requirements with defects in essence

Mercury Quality Centre is installed as a service in Microsoft windows environment. Before start working on it, make sure that Mercury Quality Centre service is running.

As soon as you access the application, the first screen is a login screen where you need to provide administrator credentials which were used during the installation of Mercury Quality Centre. Once you are logged on to the SABin, you can perform all the administrative tasks mentioned above.

Note: If Mercury Quality Centre is listening to default port, then you can access the application using the following URL:

http://%7Byourmachinename%7D:8080/sabin/SiteAdmin.htm

Define your projects in SABin. Quality Center provides the role based accessed to the Projects. For example, A Test Manager can create projects and Test Lead can prepare test plans and tester can write the test cases. This role based access makes it very easy to control access to various artifacts of the project and also distribution of responsibility among team members. Following four things can be managed in Mercury Quality Centre:

Requirements
Test Plan
Test Lab
Defects

Once you have created a project in SABin, Now log on to QCBin by providing your credentials and access the project that you have created. Here, you will notice different tabs for Requirements, TestPlan, TestLab and Defects.

Under Requirements Tab, you can organize the project requirements. You can also create folder hierarchy to represent various features in your project. This can be accomplished by just right-clicking and choosing appropriate options. After creating requirements, move on to next tab Test Plan.

Test Plan Tab will have information about the test cases. These test cases can also be mapped to requirements created in the earlier steps, thus makes foundation for the traceability metrics. Each requirement can be mapped to one or more than one test cases.

After creating new test case you will see in the left hand pane. The right hand pane will have tabs for writing the steps, mapping to requirements, description, expected result etc. Every test case will have steps and for every step you can specify the expected behavior.

The test cases written here, can also be linked to the QTP or Winrunner Scripts. This way, it is providing you better management for the automation and capability of executing automation scripts from Quality Centre itself. Once you are done with Test Plan preparation, move on to the next tab Test Lab.

To manage test execution for a specific release, you have to create a Test Lab. Test Labs can be created, specific to the release and execution of test cases specific to release can be managed very easily using this concept. In the Test Lab you can identify the set of test cases already written under test plan to include for execution.

If the test cases are already linked to the requirements, then after each test cycle the management will be able to trace what requirements have been tested.

When you choose the option of manual test execution, a window will open up containing the steps to execute. These steps are executed and after every step you can specify whether it is passed or not. Quality Center also allows parameterized manual test execution, where some of the default parameters like username, password etc. can automatically be read during the manual execution. If you encounter any defects during the failure of any of the steps, it will be automatically logged in to the defect tracking system of Quality Centre. Once you are done with Test Execution move on to next tab, Defects.

Report generation is one of the most important part of the test management process. Once you are done with planning and execution, its REPORTING time. Mercury Quality Centre provides a very good reporting feature by providing certain pre-defined reports and also capability to create your own reports.