QTP / UFT Introduction

1. What is Automation Testing 2. Advantages of Automation Testing? 3. Types of Automation Tools in the market
4. Difference Between Manual Testing and Automation Testing? 5. What to Automate? 6. What not automated? 7. When to automate? 8. Difference between different QTP Versions?
9. Comparison of GUI Automation testing tools, QTP, WinRunner, TestPartner, SilkTest
10. What can do the best tester and smart tester.
-----------------------------------------------------------------------------------------
Introduction:
- Software industry to search for new ways through process methodology  and tools for improving the quality of the software they develops and delivers. - Testing is the Key instrument for making this process happens.
What is Automation Testing?
- Test (validating) the application with any Automation Tool with respect to requirements is called Automation testing.
-  Automation enables you to control the functionality of an application pro-grammatically.   Ex: QTP 11.0
Benefits / Advantages of Automation Testing:
1. Fast - Tools are faster in execution then human users, i.e. Execute within less time. Eliminate human errors for same task.
2. Reliable - Tools are reliable in complex calculations and tasks.
3. Repeatable - We can repeat the same operations with multiple versions of software. (Ex: Sanity Tests, Regression Tests)
4. Programmable - We can use flow control statements for applying logic for run the test.(test scope is high than manual)
5. Comprehensive - Detailed Coverage each & every feature of the Application.  We can execute series of tests without human interaction.
6. Reusable - We can reuse automated tests on multiple versions of software.
Types of Automation Tools:
I) Vendor Tools:  Companies develop tools, license is required to use and get technical support.        1. Functional and Regression Test: QTP/UFT, Win Runner, Silk, Rational Robot, RFT
2. Performance Tools: LR, RPT, J-Meter, Silk Performer etc.
3. Test Management Tools: Quality Centre / Test Director, QA Director etc.
4. Defect Management Tools: Bugzilla, Zera, Issue Tracker, PR-Tracker etc.
5. Version Control Tools: VSS, PVCS (Politron Version Control System)
6. Unit Test Tools: JUnit (Java Unit Testing Tool), NUnit
7. Security Test Tools:
II) Open Source Tools:  Source Code available on NET anybody can download and use.
1. Functional and Regression Test:    Selenium
III) In-House Tools:  Some companies are developing tools for their internal use.

Difference between Manual Testing and Automation Testing?
Manual Testing Test the Application with Human interaction is called Manual testing.
Manual Testing Drawbacks:
1. Tedious / Tiredness process. (lengthy process) 2. Time consuming 3. Low reliability (consistently good) 4. Human errors may occur. 5. Repetition of the task is not much easy. 6. Simultaneous actions are not possible (more resources required)
7. Ex: use 1,000 users What about performance? Provide 1000 systems.     Large investment for human and H/W Resources.
8. Inconsistent (unchanging) -- Automation Testing: Test the Application with the Automation Tool is called Automation testing.
Automation Testing Drawbacks:
.It is Expensive. .Lack of expectation (Domain KW and QTP/UFT KW). .We can’t automate all Area’s.
.It has some limitations ( It can’t test all the areas).
Why to depend on automation?
-          To conduct tests those are humanly impossible. -          To eliminate human errors in manual testing. -          Ability to test more, faster. -          Especially useful for Regression Testing, when test procedures are automated.
-          Free Test engineers for creative thinking. -          Report amount of coverage (statement, path, etc.). -          Predict the number of Tests to run.

What to Automate?
-          Tests that need to run repeatedly (Regression) -          Tests need to be run for every build of the application (smoke level) -          Tests that use multiple data values for the same actions (DDT) -          Tests that require detailed information from application internals (e.g., GUI attributes) -          Stress/Load testing (Performance)

What not automated?
-          Configuration testing -          Usability testing -          One time testing (automated will be too time consuming). -          ‘ASAP’(As soon as possible) Testing or Quick look testing -          Tests without predictable results (Adhoc or random testing) -          Documentation – Help -          When Customer Frequently Changing Requirements
When to automate?
Functional:  
-          Stable Application – to become AUT -          Done with at least one round of ‘MT’ -          Good understanding of the feature -          Clear idea on Expected Results
Performance:    Load testing

Difference between QTP Versions 6.5, 8.0, 8.2, 9.0, 10.0, 11.0, 11.53: QTP 6.5
-          Tree View
QTP 8.0
-          Keyword View -          Object Repository -          Enhance Keyword View -          Insert step
QTP 8.2
-          Keyword Driven Testing -          AOM Concept -          Per test Mode and Shared mode Options
QTP 9.0
-          Resources menu -          Automation menu -          Information pane -          Missing Resources pane -          Shared Mode only QTP 10.0** (Tool UI Changed)
-          Drag the Particular Object Script to the Test Pane without Record Button using object repository.
-          Advanced Keyword Driven Testing.

QTP 11.0** 
-   - Integrate with ALM.
-   - Add an object directly from Object Spy to Repository. Highlight an object in our application.
- Copy / paste object properties into any document.
-   - New Smart Regular Expression list: It provides Syntax hints that make it easier to insert RE for this enable the RE Evaluator.
-   - New Run Results Viewer: See the summary page both Current and previous runs. Customize the set of panes in our run session ex: show, hide, move, dock. Share the results to others who do not work with QTP (Business analysts, developers)
-   - To hide the Keyword View
-   - Facility to add Images to Our Run Results: Now add a Reporter.ReportEvent statement includes an image file path
-   - Automatic Parameterization of steps: by selecting the automatically parameterize steps option in the General tab of the Options dialog box. We can set the option to use Global Data Table Parameters or Test Parameters. By select this option to map the generated parameters to the column names of a data resource and the use different configurations in our test sets.
-   - New Visual relation identifiers: By using this Dialog box to identify application objects based on other objects that are always near them.
-   - Visual indication of Version Control Status of Tests: using QTP provides an icon / text in the title bar in HP ALM
-   - Web 2.0 add-ins support
-   - Now record the steps on Mozilla Firefox DOM.
-   - New Web based 3 methods introduced: AnyWebBasedObject.RightClick / MiddleClick, Brower.ClearCache , Browser.DeleteCookies
-   - New LoadFunctionLibrary statement:  load only the required function libraries  during a run session
-   - Improved checkpoints and output value objects management: when comparing, merging, and exporting object repositories just like any other test object, including filtering, searching, and conflict resolution.
-   - Dual Monitor support: QTP on one monitor while the steps run on our application on another monitor.
-   - Improved Business Process testing: All component parameters in HP ALM are now inserted as string value types. From HP ALM, we can use options to encrypt these parameter values or to apply dynamic date values.
-   - The new QTP-Service Test integration enables us to test across the GUI and non-GUI layers of our application
-   - Improved Web Add-in Extensibility.
-   - Test execution in minimized remote desktop protocol session:  

QTP 11.50 (Tool UI Changed)  Patches given for QTP 11.53
     - Insight recording method new features is given (UI based Recording)
     - It is used for Device Testing (Mobile Testing)
     - Web Services Testing
     - Some Additional Software supported to test the applications like Qtopia, Mobile Applications. 


QTP 12.0 (Expected to Release mar 2014)


Comparison of GUI Automation testing tools: QTP, WinRunner, TestPartner, SilkTest
Some feauters of GUI testing tools: Here I provide the knowledge for people who are interested in Automation field. I have given some information on GUI testing tools like QTP, TestPartner, WinRunner and SilkTest. In addition to these others GUI testing tools are also available in market like loadRunner, e-Tester, Robot, Functional Tester.
Best Tester
“   The best tester is not the one who finds the most bugs or who embarrasses the most developers. The best tester is the one who gets the most bugs fixed.”
"A smart tester is one who keeps a balance between listening and implementing. If a developer can’t convince you a bug should n’t be fixed, it’s your duty to convince him to fix it."
***

Application Under Test:

Action of A Tool:

Application must be displayed to the tool. The tool focuses on the application.

AUT: (i) The application window that is currently tested by the Automation Tool or T.E.

(ii) Tool learns the properties of the object of the AUT.

(iii) (a) Tool has recording facility.

(b) It records users actions and

(c) Generate the corresponding programmatic statements. (Test Scripts)

(iv) Execute the script in order to repeat the actions of the user which were recorded during recording.

1. Played side by side to the Tool.

2. Capturing the information of objects.

3. Identify.

4. Put it under recording mode.

5. Execute

***