Friday, February 22, 2013

Introduction To HP-QTP

                           Introduction to QTP

History of QTP:

‘QTP’ stands for ‘Quick Test Professional’. This tool is combination of Mercury- Interactive Winrunner and Atra’s Quick test tools. The current owner of QTP is HP(Hawlet and Packerd)and current version is QTP 11.0.
  • Developed by HP
  • Functional testing tool
  • Run in windows computer like XP,Vista,and Seven like client side OS and 2003 server, 2008 sever like sever side OS.
Differences between HP-QC 10.0 and HP QTP 11.0

HP-QC 10.0
  • HP-QC is developed by HP.
  • HP-QC is a test management tool including defect reporting and tracking.
  • HP-QC will run on only server side OS like 2003, 2008.
  • P-QC is reporting defect to specific person.
HP QTP 11.0
  • HP-QTP is developed by HP.
  • HP-QTP is a functional testing tool.
  • HP-QTP will run on client and server side OS.
  • HP-QTP defect detecting from software.
Manual testing Vs Automation testing

In general, testing people can test a software by executing test cases but, test cases are in folders or in QC database in server computer. But, to  decrease the time in test cases execution on SUT testers are going to ‘test automation’.

‘Test excecution’ means comparing the test cases expected value to the SUT actual value which is compared by the manual tester (Manual Testing).
From the above diagram manual testing means comparison of the test cases expected value to the SUT actual value which is compared by the manual tester.

From above diagram test automation means that the conversion of test cases into programatical testscripts. Here, test cases are in English language and stored them in a folder or in QC database.

“Automated testing” means that execution of test scripts on SUT to compare expected values and actual values.

Double V – Model:  (VV and A model)

From the above model, Software testers are reading SRS(Verification ) to understand project requirements, writing test scenarios and cases (Validation) for responsible modules and testing topics and automate those cases (Automation) by using QTP like testing tools i.e., VV and A model.

Need for test automation in software testing

From the above table, automation was needed for regression levels of functional testing and all levels of performance testing. There is no wellknown tools in market for all other Non-Functional testing.

Need for Automation Testing in Functional Testing

From previous heading, Automation is applicable for regression levels of functional testing to save time. Because, manually sanity testing and regression testing are taking more time. Due to these reasons testers are following below factors to goto functional test automation by using QTP like Tool.

The following types of functional test cases are preffered (But not limited to) for automation:
  • Tests that need to run for every build.
  • Tests that use multiple data values for same action.
  • Identical functional tests that need to be executed using different browsers .
Ex: Websites.

The following types are not considered to be good cases for automation:
  • Test cases that executed only once.
  • Test cases used for adhoc / random testing.
  • Test cases that are infrequently selected for execution.
  • Test cases that will require manual interaction i.e, a task not possible to automate.
  • The most important one that is based on intuition and knowledge of application.
EX: If you find that you cannot escape from manual interaction (ex: Intellegent games).

 Functional Test Automation Tools:

There are four generations of functional testing tools:
In 1st generation, we can see all commercial tools and they are using vendor languages to write test scripts.
Example: Winrunner, SQA Robot, Silk test ….. etc (Commercial tools + Using own languages)

In 2nd  generation, we can see all commercial tools and but they are generating test scripts in generic languages. 

Example: QTP(HP),  RFT (IBM) (Rational Functional Test), Test complete(Compuware). 

In 3rd generation we can see open source tools they are using generic languages to generate testscripts . But, support is the problem.

 Example: Selenium, Sahi, Watir…. Etc.

In 4th generation opensource generic languages directly to write testscripts. But, those languages are typical or complex to testers. Because testers are not strong in the programming.

Example:   Perl, Python ……. Etc

Launching QTP Tool :

Double Click on QTP tool logo --> Click continue in license window--->Click OK in add-in manager window--->OK---> File menu--->New--->Test.

TestScripts in QTP Tool:

From introduction of QTP, Functional test cases are automatable using QTP tool. An automated program in  QTP is called as Script or TestScript.

Testers are writing test scripts in QTP tool by using 4 languages as shown in below figure.

Proof Of Concept (POC):

After launching  QTP tool and before writing test scripts, test automators can follow navigation for proof of concept means that QTP tool is supporting automation on SUT.

In this POC process, test automators can follow below steps:
  1. Knowing Technology used by developers to develop SUT screens and database.
  2. Launch QTP tool with suitable add- ins w.r.t SUT technology used by developers.
  3. Click continue in license window while launching QTP.
  4. Tools menu-à object spyàapply hand icon on SUT objectsàObserve identification properties of corresponding objects.

Recommend on Google



Popular Posts