Checkpoints refer to a validation point that compares the current value with the expected value for specified properties of an object.
HPE UFT/QTP
UFT Classes #13: Parameterization using Data Table | After all the scripts need ‘Test Data’
Parameterization tells UFT how & from where to fetch the Test Data for running the Test cases. One of the simplest method – using the Data Table!
UFT Classes #12: Don’t know programming? Use the Keyword View!
In UFT context, View is the GUI representation to facilitate automation scripting. Apart from the code editor UFT offers a Keyword view for non-programmers.
Automation Object Model in HPE UFT!
HP UFT provides a COM interface that allows automation of UFT itself. This Automation object model enables user to write code to perform the core UFT tasks.
UFT Classes #11: Introduction to Functions
If you have segments of code that needs to be used several times, you may want to create a function and then call that function from within the main action.
UFT Classes #10: Start scripting | Working with Actions
UFT action is a component in which you can write your code, i.e. code for a specific functionality. Scenario: Say you want to send a mail from Gmail & then logout. What would the steps be for this Test script?
UFT Classes #9: Ease of Automation with different Recording Modes
To begin automation, the first step every tester learns is ‘Record-and-Play’. Why? It’s the easiest 🙂 Also, during automation there will be cases when we need to record object using its properties, or continuous mouse movements, or object’s co-ordinates, or to record images of the object. The purpose defines the type of UFT Recording mode you select.
UFT Classes #8: Object Repository – collection of objects and its properties!
‘Repository’ is a generic term meaning a central location in which data is stored and managed. And why would someone need a central location? To access data from a single source of truth, which can be accessed across-locations by multiple users. Now apply the same concept to Automation.
UFT Classes #7: Most used UFT Utility – Object Spy
In our last post “UFTBasics #6: Object Identification via Mandatory & Assistive properties”, we briefed about how to identify objects in an application using their ‘properties’. The next obvious step is ‘How do you extract the ‘attribute-value’ pair for an object’s properties? This is where “Object Spy” comes to rescue!
UFT Classes #6: Object Identification via Mandatory & Assistive properties
As stated in previous post – Textbox, Button, Image, Checkbox, Dropdown, Hyperlink, etc. – everything which is visible in an application is known as “Object”. Automation is all about identifying these “Objects” in the application and the subsequent “Actions” to-be-performed on it. But the question is – How do you identify different ‘Objects’ in the application via HP UFT?
UFT Classes #5: UFT is not free! First identify your required Licensing Model.
As you all might know – HP UFT is a commercial (licensed) tool. There are two main types of UFT licenses – Seat and Concurrent.
UFT Classes #4: “Objects” – The fundamental building blocks for UFT Test Automation!
“Objects” are the fundamental Building Blocks for any Test Automation & its necessary that you fully understand the concept.
UFT Classes #3: The power to automate almost ANY application type | Understanding UFT Add-ins
UFT supports automation for wide range of development environment like Windows (.Net, Java), Web, SAP, Oracle, etc. And this is made possible by the corresponding UFT Add-ins you install. Its like knowing the requirements prior to the start of testing 🙂 Yeah! UFT add-ins are that important, so pay attention.
UFT Classes #2: Be a better version of yourself | What’s new with HP UFT (over QTP)?
Formerly known as HP QuickTest Professional (QTP), Unified Functional Testing (UFT) provides functional and regression test automation. It uses the Visual Basic Scripting Edition (VBScript) as its scripting language. UFT automates testing through an intuitive, visual user experience that ties manual, automated, and framework-based testing together in one IDE.