Default Support 1. Standard Windows applications 2. Web objects / Applications 3. ActiveX controls 4. Visual Basic applications
Supported Add-ins QuickTest Professional Java Add-in 9.1 QuickTest Professional .NET Add-in 9.2 QuickTest Professional Oracle Add-in 8.2 QuickTest Professional PeopleSoft Add-in 8.2* QuickTest Professional Add-in 8.2 for SAP Solutions QuickTest Professional Siebel Add-in 8.0* QuickTest Professional Stingray Add-in 8.2 QuickTest Professional Terminal Emulator Add-in 8.0* QuickTest Professional VisualAge Smalltalk Add-in 8.2 QuickTest Professional Web Services Add-in 9.2
QTP’s Add-in Manager facilitates the users to select the technology / environment from variety of environments suitable for the AUT (Application Under Test)
Once an add-in is loaded, users can record that application in its supported environment and thus QTP recognizes the objects specific to the application under test (AUT) as loaded through Add-in Manager.
It is critical for the users to know the development technologies / environment of AUT, and load right Add-Ins while invoking Quick Test Pro.
QuickTest Professional, the Mercury advanced keyword-driven testing solution enables you to test standard Windows applications, Web objects, ActiveX controls, and Visual Basic applications. You can also acquire additional QuickTest add-ins for a number of special environments (such as Java, Oracle, SAP Solutions, .NET Windows and Web Forms, Siebel, PeopleSoft, Web services, and terminal emulator applications).
Once the record button is pressed and test steps are performed , QuickTest listens and records the activities. This results in the recording and storing of each step of the business process. Each step consists of:
The method (operation)
The method property (a value for the action performed on the object)
QuickTest should be running before the application under test is invoked. For some environments, this is mandatory.
In the example above, there are several objects called Buttons, two of which are:
The only way to distinguish one object from the other of the same class is by the difference in object characteristics. Specific characteristics of an object within QuickTest are called object properties.
QuickTest uses a method when it learns objects during the recording process.
QuickTest first looks at the object you are recording and stores it as a test object, determining its object class. For example, QuickTest might classify the test object as a standard Windows dialog box or a web button.
For each object class, QTP has a default set of properties that it always learns.
Usually, only a few properties are needed to uniquely identify an object.
Quick Test defaults to allocating the same amount of time for every object.
Wait times often occur before an object becomes available for the next step. For example, in the Flights application, once the Insert Order button has been clicked, a process bar must complete to yield the Order No. associated with the reservation. The process bar may require additional time before the test can proceed. If insufficient time is allocated for these special circumstances, the test may fail.
The error message “Object not enabled” appears if QuickTest is running a test and proceeds to the next step before the previous step has fully processed.
Rather than recording the login process three times in three separate tests, and enhancing this part of the script (with checkpoints and parameterization) separately for each test, you can create an action that logs into the application in one test.
Inserting calls to existing actions makes it easier to maintain our tests; when an object or procedure in your application changes. It only needs to be updated one time, in the original action.
Interact with Test Objects not stored in the Object Repository
You can also instruct QT to perform methods on objects without referring to the object repository without referring to the object’s logical name. To do this you provide QT with a list of properties and values that QT can use to identify the object or objects on which you want to perform a method
10. Enhance TestCases With Descriptive Programming
Types of Checkpoints Check that a Web page (or any portion of it) is displayed as expected. Checks an area of a Web page or application after capturing it as a bitmap Bitmap Checkpoint Check whether the expected text string is displayed in the expected location on a Web page or dialog box Checks that a text string is displayed in the appropriate place in a Web page or application window Text / Text Area Checkpoint Check how long a Web page takes to load or if a Web page contains broken links. Checks the characteristics of a Web page Page checkpoint Check that the value in a table cell is correct. Checks information in a table Table Checkpoint Check that the image source file is correct. Checks the property values of an image Image Checkpoint Check that a radio button is selected. Checks values of an object’s properties Standard Checkpoint
Cont…. Note: XML file checkpoints are used to check a specified XML file; XML application checkpoints are used to check an XML document within a Web page. Checks the data content of XML documents XML Checkpoint Check if the images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines. Identifies areas of a Web site to check for Section 508 compliancy Accessibility Checkpoint Check that the value in a database query is correct. Checks the contents of databases accessed by an application or Web site Database Checkpoint