Frame Work

Can anybody tell me,
What is frame work in WinRunner and QTP?

Is is two different frameworks or same for both WinRunner and QTP.
I am :confused: with different responses from different people and i am going :mad:.
Please explain.

Hi,

Framework in QTP or WinRunner is nothing but a folder structure where we can place our input datas, Scripts, Exporting results, Place library files. While running the scripts getting inputs and exporting the results should be done automatically inside of the framework. Now a days repository and Gui files are maintained externally at that time framework will be very helpful.

Frame work ... Now a day lot of companies are concentrating on this topic in interviews. Frame work is nothing but , the structure of the application, the structure of the functionalies

But how do you answer a question in an interview like,

"What is the framework that you use in your current job?"

What is difference between smoke and sanity testings? pls give examples

Can any one pls give the difference between performance, Load & stress testing? give live examples....

rkpanchadi,

You have posted your question in the wrong place its a right forum but wrong place.

You have to create a new thread in the appropriat forum when you want to "ask" questions in this group.

Comming to your question, there is already a thread that gives a lot information and differences between smoke and sanity testing. You will find it in 'testing issues' forum.

Automation framework is a process that helps test engineers control the tool operations for a complete and correct test execution of the automation scripts on the build.

In short it describes the directory structure of how the files are stored.

Framework varies from one automation tool to another.

For example for Mercury Interactive tools in Windows environment

the framework for WR :
C:\Program Files\Mercury Interactive\WR\tmp\<testname>
C:\Program Files\Mercury Interactive\WR\tmp\<testname>\chklist\list.ckl
C:\Program Files\Mercury Interactive\WR\tmp\<testname>\exp\gui1
C:\Program Files\Mercury Interactive\WR\tmp\<testname>\default.xls
C:\Program Files\Mercury Interactive\WR\tmp\<testname>\msqr1.sql

the framework for QTP :
C:\Program Files\Mercury Interactive\QTP\tests\<testname>

There are three aproaches in automation 1.Keyword driven 2.data driven 3.hybrid (combination of both keyword and data)
most of the time people use hybrid approach (we use hybrid at our company).
these are nothing but the frame work.

hi amarreddy

can u explain abt the three approaches u mentioned .Keyword driven 2.data driven 3.hybrid (combination of both keyword and data

mbazith's explanation for framework is right.

Framework [COLOR="Red"]also includes few more (apart from the above)[/COLOR] things like:
01. Naming convention for Scripts, Actions, Action parameters, external data files, variables, etc
02. Putting script header (Author, purpose of the script, entry point, exit point, limitations, open issues, change history, etc) and inline comments in the script to increase the readablity and maintainablity of the code.
03. Proper debugging, etc.

The proce

Hi
Framework is nothing but a standard approach which the entire Team follows in the course of a Project. This includes Folder structures, Naming conventions, File paths, Common Functions, etc

[QUOTE=sutnarcha;4572]But how do you answer a question in an interview like,

"What is the framework that you use in your current job?"[/QUOTE]

The are quiet a few Frameworks in QTP.....
DFD framework
BPT framework
Actions framework

Amongst these BPT is the most preferred if you have QC incorporated

Hi,
Can you please explain about BPT Framework. I could see a folder with the name "BPT Resources" in QC of our project and all folders that are using in Automation Testing is stored in this folder. But our project is using Keyword Driven Framework. So I am bit confused about this term "BPT Framework". I hope you can help me.

[B][I][U]Smoke[/U][/I][/B]:
1. Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
2. A smoke test is scripted--either using a written set of tests or an automated test
3. A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide.
Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification).
4. Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
[B][I][U]Sanity[/U][/I][/B]:
1. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
2. A sanity test is usually unscripted.
3. A Sanity test is used to determine a small section of the application is still working after a minor change.
4. Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
5. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.