what is qtp automation frame work,what is the use of that
frame work?




Answers were Sorted based on User's Feedback



Answer / sreenivas reddy

automation frame work is nothing but a set of guidelines
designed by expert to accomplish a task in an
effective,eficcient and an optimised way.
there are 4 different types of frame work 1)linear 2)
modular 3)keyword 4)hybrid
max we follow keyword framework
keyword frame work is nothing but creating a software
structure like
1)scripts 2)object repository 3)test data 4)recovery
scenario 5)log files 6)library files etc
1)create scripts and save it in scripts component
2)create shared o.r and save it in o.r component
3)create test data and save it in test data component
etc
after creating all these components include the files or
components to script or qtp and execte the script

Is This Answer Correct ?    262 Yes 30 No

Answer / lokesh kanithi

Automation Framework is nothing but the way we r doing
automation is represented in a systematic way with proper
planning like Initial Setup(setting up shared
repository..), Tool configuration,Test Data files,library
files,Script
generation,Enhancements,Synchronisation,Exception
handling,Batch test,maintaning the scripts....all whichever
related to our automation plan.
Thank& Regards
Lokesh Kanithi

Is This Answer Correct ?    192 Yes 24 No

Answer / jayachander lakavath(igt)

Automation framework is one....it is a test plan for
automation testing which drives entire automation testing
in a sytemamatic and scientific manner to execute the test
script like Main Script--->DriverScripts--->Environment
variables, Library files, Functions, Test Data(data table -
Parameterization.

Here MainTest Script will call the DriverScripts
DriverScripts will call the required Env, Lib files,
Func.....etc.

So the entire test will be executed/carried out in a flow
like explained above.(This comes under Keyword Driven
Framework).

Is This Answer Correct ?    92 Yes 17 No




Answer / soumitro chatterjee

Automation frame work is a set of procedures
designed by Automation Testers or their seniors to do a task
in an effective,efficient and an optimized way.

Broadly categorized Framework are :
1) Key Word Driven Testing:Most of the companies follow
keyword framework

The Keyword Driven framework consists of the basic
components given below
1. Control File
2. Test Case File
3. Startup Script
4. Driver Script
5. Utility Script

1. Control File a)Consists details of all the Test scenarios
to be automated b)User will be able to select a specific
scenario to execute based on turning on or off a flag in the
Control File c) Control File is in the form of an excel
worksheet and contains columns for Scenario ID,Execute
(Y/N),Object Repository Path, Test Case File Path

2. Test Case File a)Contains the detailed steps to be
carried out for the execution of a test case b) It is also
in the form of an excel sheet and contains columns for
Keyword, Object Name, Parameter

3. Startup Script a) The Starup script is utilised for the
initialization and reads the control files b) It then calls
the driver script to execute all the scenarios marked for
execution in the control file

4. Driver Script a) It Reads the Test Case files. Checks the
keywords and calls the appropriate utility script functions
based on specific keyword b) Error Handling is taken care of
in the driver script.

5. Utility Scripts a) Perform generic tasks that can be used
across applications. It should not be application dependent
Advantage of Framework.
The main advantage of this framework is the low cost for
maintenace. If there is change to any test case then only
the Test Case File needs to be updated and the Driver Script
and Startup script will remain the same.
No need to update the scripts in case of changes to the
application.
ALSO

Keyword-driven testing is a Software testing technique that
separates much of the programming work from the actual test
steps so that the test steps can be developed earlier and
can often be maintained with only minor updates, even when
the application or testing needs change significantly.

Keyword-driven testing (also: table-driven testing,
action-word testing) is a software testing methodology.
Although keyword testing can be used for manual testing, it
is a technique particularly well suited to automated
testing[1]. The advantages for automated tests are the
reusability and therefore ease of maintenance of tests that
have been created at a high level of abstraction.
Methodology
The keyword-driven testing methodology divides test creation
into two stages: the Planning Stage, and the Implementation
Stage.
Planning Stage
Examples of keywords
A simple keyword (one action on one object), e.g. entering a
username into a textfield.
Object
Action
Data
Textfield (username)
Enter text
<username>
A more complex keyword (a combination of other keywords in a
meaningful unit), e.g. logging in.
Object
Action
Data
Textfield (domain)
Enter text
<domain>
Textfield (username)
Enter text
<username>
Textfield (password)
Enter text
<password>
Button (login)
Click
One left click
Implementation Stage
The implementation stage differs depending on the tool or
framework used. Often, automation engineers implement a
framework that provides keywords like “check” and “enter”
[1]. Testers or test designers (who don’t have to know how
to program) write test cases based on the keywords defined
in the planning stage that have been implemented by the
engineers. The test is executed using a driver that reads
the keywords and executes the corresponding code.
Other methodologies use an all-in-one implementation stage.
Instead of separating the tasks of test design and test
engineering, the test design is the test automation.
Keywords, such as “enter” or “check” are created using tools
in which the necessary code has already been written. This
removes the necessity for extra engineers in the test
process, because the implementation for the keywords is
already a part of the tool. Tools such as GUIdancer and
Worksoft Certify use this approach.
Benefits
Although this methodology requires more planning and a
longer initial time-investment than going directly to the
test creation stage and recording a test, it does make the
test creation and test maintenance stages more efficient and
keeps the structure of individual tests more readable and
easier to modify. The more abstract keywords are, the more
reusable they are, and therefore the easier a test is to
maintain. As well as reducing the cost and time spent
maintaining and updating tests, the modular structure of
keyword-driven testing means that new tests can easily be
created from pre-existing modules.
Another advantage is the reduction in technical know-how
required for the test automation process. In the first
approach, technical know-how is only required by the
engineers that implement the keywords. In the second
approach, even this is not required, which means that the
test team is capable of entirely automating tests, even
without programming knowledge.




2) Data-driven Testing:

Data-driven testing is a framework where test input and
output values are read from data files (datapools, ODBC
sources, csv files, Excel files, DAO objects, ADO objects,
and such) and are loaded into variables in captured or
manually coded scripts. In this framework, variables are
used for both input values and output verification values.
Navigation through the program, reading of the data files,
and logging of test status and information are all coded in
the test script.

In the testing of software or programs, several
methodologies exist in dictating how this testing will be
performed. Each of these methods exist because they differ
in their effort required to establish initially and then to
subsequently maintain. This article aims to explain the
data-driven method which is part of the automated testing
disciplines.
[edit] Methodology Overview
Data-driven testing is a methodology used in Test automation
where test scripts are executed and verified based on the
data values stored in one or more central data sources or
databases. These databases can range from datapools, ODBC
sources, csv files, Excel files, DAO objects, ADO objects,
etc. Data-driven testing is the establishment of several
interacting test scripts together with their related data
results in a framework used for the methodology. In this
framework, variables are used for both input values and
output verification values: navigation through the program,
reading of the data sources, and logging of test status and
information are all coded in the test script. Thus, the
logic executed in the script is also dependent on the data
values.
This is similar to Keyword-driven testing in that the test
case is contained in the data values and not in the test
script; the script is just a "driver" or delivery mechanism
for the data. Unlike in keyword-driven testing, though, the
navigation data isn't contained in the test script. In
data-driven testing, only test data is contained in the data
source.



3) Modularity-driven testing

The test script modularity framework requires the creation
of small, independent scripts that represent modules,
sections, and functions of the application-under-test. These
small scripts are then used in a hierarchical fashion to
construct larger tests, realizing a particular test case.
Test Script Modularity Framework
The test script modularity framework requires the creation
of small, independent scripts that represent modules,
sections, and functions of the application-under-test. These
small scripts are then used in a hierarchical fashion to
construct larger tests, realizing a particular test case.
Of all the frameworks, this one should be the simplest to
grasp and master. It is a well-known programming strategy to
build an abstraction layer in front of a component to hide
the component from the rest of the application. This
insulates the application from modifications in the
component and provides modularity in the application design.
The test script modularity framework applies this principle
of abstraction or encapsulation in order to improve the
maintainability and scalability of automated test suites.


4)Hybrid

The hybrid Test_Automation_Framework is what most frameworks
evolve into over time and multiple projects. The most
successful automation frameworks generally accommodate both
Keyword-driven_testing as well as Data-driven_testing. This
allows data driven scripts to take advantage of the powerful
libraries and utilities that usually accompany a keyword
driven architecture. The framework utilities can make the
data driven scripts more compact and less prone to failure
than they otherwise would have been. The utilities can also
facilitate the gradual and manageable conversion of existing
scripts to keyword driven equivalents when and where that
appears desirable. On the other hand, the framework can use
scripts to perform some tasks that might be too difficult to
re-implement in a pure keyword driven approach, or where the
keyword driven capabilities are not yet in place.
The Framework
The framework is defined by the Core Data Driven Engine, the
Component Functions, and the Support Libraries (see adjacent
picture) . While the Support Libraries provide generic
routines useful even outside the context of a keyword driven
framework, the core engine and component functions are
highly dependent on the existence of all three elements. The
test execution starts with the LAUNCH TEST(1) script. This
script invokes the Core Data Driven Engine by providing one
or more High-Level Test Tables to CycleDriver(2).
CycleDriver processes these test tables invoking the
SuiteDriver(3) for each Intermediate-Level Test Table it
encounters. SuiteDriver processes these intermediate-level
tables invoking StepDriver(4) for each Low-Level Test Table
it encounters. As StepDriver processes these low-level
tables it attempts to keep the application in synch with the
test. When StepDriver encounters a low-level command for a
specific component, it determines what Type of component is
involved and invokes the corresponding Component Function(5)
module to handle the task.

5)Linear

I hope this will help us to know about Automation Framework
in a detailed manner.

Regards
Soumitro

Is This Answer Correct ?    23 Yes 3 No

Answer / venkat

Frame work is the Approach or we can say the Architecture
that we follow for a project. The type of frame work you
choose depends on the project.

There are so many classification's on the type of frame
work some of them are:

1. Module driven.

2. Data driven.

3. Keyword driven.

4. Hybrid driven.(Data driven + Keyword driven)

Is This Answer Correct ?    30 Yes 13 No

Answer / pramod k sirotia

Automation Framework: it is nothing but a
Standard/Procedure/Guidelines/process which is use to
Automation Planning with respect to AUT.


Linear Framework: If your application is supposed to
Regression run on Local System then this framework is
better.

Modular Framework: If AUT is supposed to Regression run in
which More than one Action has to be performing for the
same script then Modular framework is better. You might be
making your test Modular by dividing your test into many re-
usable actions and either any action can call any of the
action within that test.

Keyword Driven Framework:
It sound like business process testing where you might be
able to write business logics/code and develop your script
and those scripts can be call from outside of your test.
Moreover there might be various functions libraries to be
build and to be use, Recovery Scenarios, OR maintenance etc
will provide your test Reusable.

Is This Answer Correct ?    26 Yes 9 No

Answer / dhanasekar s

An Automation Framework is collection of
assumptions,concepts and practices you bring in while
developing the automation project, so it helps in
constituting a work platform or support for automated
testing.It would be great, if the framework is application
independent
Read below blog to know more
http://testingideas.wordpress.com/2008/08/12/what-is-a-framework-in-automation/

Is This Answer Correct ?    20 Yes 6 No

Answer / shrijith j

Automation Framework is used to automate testing an
Application by linking all the scripts, test data and
functions laying as sepearte files(XML,Excel,VBS....)

The Framework would call these file based on the
conditions specified in the framework and would continue
execution of the testcases on the Application.

We could mention Test Scenarios, Testcases and their
TestData for this execution in an external file, which
would be called by QTP Framework for Test Execution.

The Automation framework is selfdesigned and could
vary based on the Application and the developer of the
framework.

Is This Answer Correct ?    33 Yes 22 No

Answer / raja mohamed

Framework is a well organised structure of Testing
components which provides support for Automation setup.This
framework architecture would contain Driver Scripts,Test
cases, Test data storage, User defined Function and Finally
Automation Engine which may QTP or Winrunner. the
Automation Tool depends on test scripts and environment
support.

Is This Answer Correct ?    16 Yes 12 No

Answer / sangram sahoo

Fraqme work is the common repository or common storage area
, where libary functions,actions ,dll's r present & test
engineers use them as per their requirment.


we r using modular & functionnal decomposition type
framework, in which we first divide our requirment into diff
modules , then diff modules to diff functionalities.and for
each functionnality we use diffrent actions. in this way we
use framework in our project.

Is This Answer Correct ?    13 Yes 9 No

Post New Answer



More QTP Interview Questions

how to test Web application using QTP software

4 Answers   BITS,


When we r doing data driven test with chkpts, i want to insert formulae in data sheet but i didn't get. How we wil do that plz. explain in detail.

0 Answers  


what is test scheduling?

1 Answers  


I need to obtain the parent of an object programatically, so if I have: winButton("aButton") I need to obtain the parent part: window("Window1").Dialog("Dialog1") so I can programatically create a string of the full name of the object to call it with an execute statement in QTP I would like to use something like: part[1] = "window(""Window1"")" part[2] = "dialog(""Dialog1"")" so I can do: exeLine = part[1]&"."&part[2]&"."&"winButton(""aButton"")" Execute exeLine Apart from keeping a record of the window/dialog hierarchy is there a parent or path function/ command Thanks Adrian

0 Answers   Accenture,


what is the use of automation frame work ??(QTP)

2 Answers  


how do u get lib files into scripting files?

3 Answers  


i want 8.2 and 9.2 dacuments plhelp any body sand it to my id sandhyat1@yahoo.co.in

3 Answers   Siloka,


does test plan is in test strategy or test strategy is in test plan.

6 Answers   Microsoft, TCS,


HoW to open QTP in Real time.after getting the qtp window how to log in .pl answer real time people

3 Answers   GE,


what r advance features u had done in QTP?

3 Answers   HCL,


how to automate standalone infopath forms using QTP? (it is not a dotnet or a web form)

1 Answers   ABC,


During execution, how can we capture the data from the pop- up, ie. when any popup comes with some numbers written on it, then how can we capture the value/number that is coming on the pop-up and save in the dynamic file/or other file, even when the run is going on.

2 Answers   Wipro,




Categories