In The Manual Testing Concurrency Is Not Possible (Measure The Response Time Exactly) - Sanity or Smoke To Test The Major Functionalities
In The Manual Testing Concurrency Is Not Possible (Measure The Response Time Exactly) - Sanity or Smoke To Test The Major Functionalities
In the manual testing concurrency is not possible (measure the response time exactly). Sanity or smoke to test the major functionalities.
Advantages:
Parameterization: To test the same application with multiple sets of data Regression Testing: whenever the new functionality is added to the existing functionality at that time, the existing functionality we have to identify the existing sanity test cases and then automated it. Concurrency is possible
Disadvantages:
It is expensive Skill and expertise person should required If the automation plan is not properly maintained or developed, it will consume more time than the manual.
Integration types of test cases (web services, Net Banking) Usability Exploratory/ad hoc types of test cases A test case which is having manual intervention Negative test cases
QTP
QTP Stands for Quick Test Professional QTP Launched in 2002 (Nov). By Mercury Interactive. Later taken over by HP, in 2007. After acquiring by HP company has released 9.5 version which was not clicked. QTP is an Object Based Testing Tool. QTP is for functional and Regression Testing. It follows Keyword driven approach. It supports Windows Operating Environment only. It supports GUI based and Web based Applications Automation, does not support CUI (Command user interface) Applications. It has multilingual support. (It supports English, Chinese, Japanese, Korean, etc languages with respect to license.)
Technologies Supported
1.
Standard Windows applications Web objects / Applications ActiveX controls Visual Basic applications
2.
3.
4.
Astra Quick test (Mother tool of QTP) 1.0 to 5.0 Quick Test Professional 5.6 Nov 2002 6.5 2003 8.0 2004 8.2, 8.3 2005 9.0,9.1-2006 9.2- 2007 mercury interactive 9.5 2008 H.P 10.00 2009 January
Functional tools (QTP, Win runner, Silk Test etc) Management Tools (Test Director/Quality Centre) Performance tools (Load Runner, Silk performer)
2.
3.
AddAdd-in Architecture
Enables QTP to provide support for multiple technologies. Add-ins are software that need to be installed on a system that has QTP. It then becomes integrated with the QTP environment. QTP is sold with the ability to understand a few technologies, add-ins provide QTP with the ability to understand additional technologies Users are able to select the specific add-ins for the technologies they are testing thereby reducing the memory footprint of QTP
QTP supports almost all industry leading technologies, but by default it does not support, with respect to add in license it supports. Default Add- ins of QTP are: - Activex - Visual basic - Web. Other available Add Ins are: .Dot NET, Java, People soft, Siebel, TE (Terminal Emulators), SAP for GUI, Sap for Web, Oracle Apps, Web Services etc. During QTP launching it shows Add in manger dialog box, Add in Manger lists out all available Add Ins in the company. User needs to select appropriate Add Ins for his application or AUT. One can select more than one Add Ins also; if we select unnecessary Add Ins QTP performance will be reduced.
Should not start until the manual testing is stable The test script should be run each and every build The test script should be run on supported browsers If our project/product/application having localization setup with localization
2. Identify Objects Logical Name/ Class Name Physical Description/ Properties 3. Start recording Writing Scripts
4.Edit / enhance the scripts Validation 5.Run the scripts Either individually or batch 6.Log the bugs and report the results
Quick Test Pro displays your test in the form of a collapsible, icon based tree Quick Test Pro displays the source code (VB Script) of the tests in this view.
Expert View:
Data Table : Data table assists in Parameterizing the tests Debug Viewer Pane : It assists in debugging tests with the help of Watch Expressions, Variables, and Command.
Quick Test Pro Commands Quick Test Pro Commands : The Quick Test Pro commands can be chosen from the menu bar or from a Tool bar. File Tool bar : File tool bar contains buttons for managing the test.
Test Tool bar : Test tool bar contains buttons for the commands used when creating or maintaining the tests
Action Tool Bar : To view all actions in the test flow or to view the details of a selected action
3.
is the default recording mode in QTP in which it will record the standard GUI operations. (Default Recording Mode)
Navigation:
Automation Select
Or Record
Put AUT in base state Select Record Option It shows Record and Run Settings, Select type of Environment (Windows or Web) Select Record Option
(It shows two Options : I. Record and Run Test on any open window based applications II. Record and Run only on If we select first option it records on any opened application on Desktop. If we select Second option, it asks for the path of the AUT, After Providing the path it records only on that particular application.)
Analog Recording
It
will record only Keyboard and Mouse Operations. will record non standard GUI operations.
It It
Navigation
Automation
Start Recording
Or ALT + Shift + F3
Launch AUT (or we can launch AUT through QTP) Select Record option Automation>Analog Recording Analog Recording Settings Dialog box opens
(In this Dialog box two options available. 1.Record relative to the screen 2.Record relative to the following window
If we select first option QTP records User operations with respect to Desktop coordinates. If we select Second option, we have to show the window (AUT), after showing the Window it records with respect to that window co-ordinates.)
5. Select any one option in the dialog box and click Start
Analog record. 6. It records User actions 7. Stop Recording
It records some operations on Non-supported environments apart from Normal operations. This mode records at the object level and records all run time objects as window or winobject Test objects. Use Low Level Recording for recording in an environment not recognized by QTP.
Navigation
Keep
Automation
Check Points
Check Point is a verification point that compares the current value of the specified property with the expected value for that property. (It is a validation point to compare the actual and expected value.)
Standard Check Point Text/ Text Area Check Point Bitmap Check point Database Check Point XML Check Point Accessibility Check Point/ Web Checkpoint