UNIFIED FUNCTIONAL TESITNG (Preparing to Record (Understanding Functional…
UNIFIED FUNCTIONAL TESITNG
HP UFT records the action of a user on the system under test.
UFT can record at various levels of granularity
UFT records every mouse movement, click and keypress.
UFT also records each action on the graphical user interface (GUI).
UFT does not record unnecessary actions and it recognises the objects with which the user is interacting.
In normal recording, UFT recognises these objects and stores representations of them in a repository (
the Object Repository
Object Repository is a very essential entity in any UI automation tool. A repository allows a tester to store all the objects that will be used in scripts in one or more centralized locations rather than letting them be scattered all over the test scripts,
UFT refers to the repository during playbacks to reproduce the user's actions on each subject.
UFT is able to recognize wide range of objects including those which exist in an application. wich is embedded in another, such as an Active X or Java components embedded in a browser.
Checkpoints are the means by which UFT determines whether a test has passed or failed.
If the actual result of a check matches the expected result, the check passes; If it does not, the check fails. The pass or fail is recorded in the result of the test.
A checkpoint is a point in the script where the UFT stops to compare the actual state of a particular aspect of the application under test with the expected state
The types of checkpoint include checkpoint which verify object status, the presence of text strings on a web page, the presence of text strings on a web page, the presence of a bitmap in a particular place on the screen and the presence of expected data in an application's database.
There are several different types of checkpoints, each of which compares a different types of data.
Checkpoints are inserted as desired by the tester after the initial recording. A script may have any number of checkpoints.
Parameters can be used to extract data from the test.
Script in UFT can make use of
Dynamic data, In this case, a list of book identifiers is stored in UFT's built-in data table.
Data may be entered into data table manually, or imported from outside sources such as Excel spreadsheets - compatible database (wich includes Oracle, MS Access and Sql Servers.)
A script may be set up to perform an action repeatedly, each time for a different customer.
The HP UFT solution allows playback to be viewed as an animation.
A tester can use the animation to see exactly what actions were performed on the system by UFT and exactly how the system reacted
Why is it useful?
HP UFT enables functional test to be carried out automatically to increase the speed and cost-effectiveness of application development and delivery.
UFT is especially useful for
Regression tests check that existing functionality of an application still works as it should after other parts of the application have been modified.
Such as set of test is often known as a
Regression Pack will normally execute tests much faster than a team of manual testers and can also be set to run of hours
Outside the domain of testing, UFT can also be used as a 'robot' to automate a variety of repetitive tasks wich would otherwise have to be carried out by a human user.
What it does?
UFT automates functional tests by recording the actions of a user on the system under test and replaying the actions on demand to execute a test.
The HP Unified Functional Software is the HP's main automated functional testing tool wich incorporates the features of various important legacy products.
The recorded actions are stored in UFT as simple program known as
Script can be displayed in UFT either as Visual Basic Script program or as a sequence of steps labeled by Labels
The tool can test the success or failure of any step with a
Checkpoint compares the actual result produced by the system under test at the time of execution, with an expected result stored in UFT at the time of recording.
Preparing to Record
Understanding Functional Testing
Functional testing enables you to verify the following features of AUT:
Approaches for Functional Testing
Drawbacks Wich Test to Automate
consuming and tedious
Deciding Which Test to Automate
The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software.
Using a single test to verify many different test cases by dividing the test with input and expected values from an external data source instead of using the same hard-coded values.
This way, you can test how the application handles various input without having a lot of similarities that only have different data sets.
The process of putting demand on a system or device and we asuring its responce.
Benefits of Automated Test
UFT -GUI Testing Work Flow
Verify and Enhance
Enhance the automated test for playback and testing
Run multiple tests to check the flow of data
Prepare the automated test environment
Record user actions to generate the basic test
UFT- Test Environment Requirements
To Determine the input data:
Interview the Subject Matter Expert
Determine the extreme rangers of input data.
Decide what should happen when invalid data are given as input to the application.
UFT - When to Record Test
Recording helps novice UFT for GUI Testing users learn how UFT for GUI Testing interprets the operation you perform on your application...
It also helps GUI Testing users learns how UFT for GUI Testing converts operation to UFT for GUI Testing objects and buit-in operation
It can be useful when you need to quickly create a test of the basic functionality of an application or feature, but does not require long-term maintenance.
Prepare to Automate a Test
Before automating a test:
Determine the initial and end conditions of the test by determining the start and end condition for your application when you initiate your test.
Use standardize naming conventions fo tests.
Ensure You are Prepared
Before automating a functional test
Check for the stability of the AUT (Application Under Test).
Identify which tests will be created by each tester.
Execute the test case steps manually.
Check your data.
Determines the start and end conditions of the test
Standardize naming conventions.