Components are associated with resources such as function libraries, recovery scenarios, and object repositories (via an application area). QuickTest displays all the resources associated with a component in the Resources pane. The Resources pane enables you to view and open all of the resources in your component. To view the Resources pane, click the Resources Pane button or choose View > Resources.
Showing posts with label QTP Panes. Show all posts
Showing posts with label QTP Panes. Show all posts
Friday, November 25, 2011
Test Flow Pane
The Test Flow pane is comprised of a hierarchy of actions and action calls in the current test, and shows the order in which they are run. Each action is displayed as a node in a tree, and includes calls to all of a test's actions. The steps of the action that you double-click in the Test Flow pane are displayed in the Keyword View and Expert View.
The Test Flow pane is displayed by default when you start QuickTest Professional. To view the Test Flow pane, click the Test Flow Pane button or choose View > Test Flow.
The Test Flow pane is displayed by default when you start QuickTest Professional. To view the Test Flow pane, click the Test Flow Pane button or choose View > Test Flow.
Available Keywords Pane
The Available Keywords pane displays the keywords available to your test or component. It enables you to view and drag and drop objects or calls to functions into your test or component. When you drag and drop an object into your action or component, QuickTest inserts a step with the default operation for that object. When you drag and drop a function into your test or component, QuickTest inserts a call to that function. To view the Available Keywords pane, click the Available Keywords Pane button or choose View > Available Keywords.
Process Guidance Panes
In QuickTest, process guidance is displayed in two panes: the Process Guidance Activities pane and the Process Guidance Description pane
Process Guidance Activities Pane:
The Process Guidance Activities pane (shown on the left) lists the activities that are part of the selected process. Activities are often grouped, enabling you to navigate directly to the sub-process that interests you. The example above illustrates some of the groups and activities in the Keyword-Driven Testing process. For example, the Determine Testing Needs group contains three activities: Define Testing Environment, Analyze Your Application, and Plan Your Actions.
The Process Guidance Description pane (shown on the right) displays the topic (description), for the selected activity.
Each description introduces you to a specific activity and provides links to locations in which you can find more information about how to perform that activity. Additionally, many of the descriptions include interactive links that open dialog boxes or other relevant features, enabling you to directly access the features that are being described.
Process Guidance Activities Pane:
The Process Guidance Activities pane (shown on the left) lists the activities that are part of the selected process. Activities are often grouped, enabling you to navigate directly to the sub-process that interests you. The example above illustrates some of the groups and activities in the Keyword-Driven Testing process. For example, the Determine Testing Needs group contains three activities: Define Testing Environment, Analyze Your Application, and Plan Your Actions.
The Process Guidance Description pane (shown on the right) displays the topic (description), for the selected activity.
Each description introduces you to a specific activity and provides links to locations in which you can find more information about how to perform that activity. Additionally, many of the descriptions include interactive links that open dialog boxes or other relevant features, enabling you to directly access the features that are being described.
Missing Resources Pane
The Missing Resources pane provides a list of the resources that are specified in your test but cannot be found. Missing resources can include calls to missing actions missing function libraries, missing recovery scenarios, a missing XML file used to store environment variables, unmapped shared object repositories, and parameters that are connected to shared object repositories. To show or hide the Missing Resources pane, choose View > Missing Resources or click the Missing Resource button.
Each time you open your test or function library, QuickTest automatically checks that all specified resources are accessible. If it finds any resources that are not accessible, QuickTest lists them in the Missing Resources pane. If the Missing Resources pane is not currently displayed, QuickTest automatically opens it when a missing resource is detected.
Information Pane
The Information pane provides a list of syntax errors in your test or function library scripts. To show or hide the Information pane, choose View > Information or click the Information button.
When you switch from the Expert View to the Keyword View, QuickTest automatically checks for syntax errors in your script, and shows them in the Information pane. If the Information pane is not currently displayed, QuickTest automatically opens it when a syntax error is detected.
You can double-click a syntax error to locate the error in the script or function library, and then correct it.
When you switch from the Expert View to the Keyword View, QuickTest automatically checks for syntax errors in your script, and shows them in the Information pane. If the Information pane is not currently displayed, QuickTest automatically opens it when a syntax error is detected.
You can double-click a syntax error to locate the error in the script or function library, and then correct it.
HP QTP Debug Viewer Pane
The Debug Viewer pane contains three tabs to assist you in debugging the script or function library as Watch, Variables, and Command. To view the Debug Viewer pane, choose View > Debug Viewer.
Watch: The Watch tab enables you to view the current value of any variable or VBScript expression that you added to the Watch tab.
Variables: During a run session, the Variables tab displays the current value of all variables that have been recognized up to the last step performed in the run session.
Command: The Command tab enables you to run a line of script to set or modify the current value of a variable or VBScript object in your function library. When you continue the run session, QuickTest uses the new value that was set in the command
Designing QTP Framework
What is framework?
Automation Framework is a set of guidelines and process you use to manage and optimize your automation testing. In simple words, Framework is a way to do the things in fashioned and organized manner! Framework is nothing but a concept.
It’s always possible to work without framework but you’ll be doing a lot of rework, everything will be here & there and in most of the time you will end-up with a mess, specially in the large projects.
Framework lets you predefine your automation plans, strategies and how you are going to proceed.
Types of Framework:
Framework can be of several types, but here are three main types of frameworks-
1. Keyword driven framework
2. Data driven framework
3. Hybrid framework
But this is only theoretical. Practically, there is no ‘Chinese Wall’ between the framework types.
In every organization you work, you’ll find that it’s quite different from the other and not only on organization level, you can feel the difference within different projects!
Yess, but most of the them could be mapped with Hybrid type and I like it!! :)
Hybrid framework has no boundaries and open to take benefit of all possible type of frameworks.
How to design a framework?
I have done a lot of automation projects and designed a lot a frameworks, but seriously guys, I never used any particular type of framework!
Practically, every application/project has its own expectation. You just need to start your work in organized way and believe me friends, at the end of the day; your framework will be ready automatically!! Sounds crazy??
You can’t design a complete framework and then start automation! You start automation and framework will start building simultaneously.
The first step of any test automation framework is to do a quick POC with few high priority test cases. By doing POC, you will identify the object identification issues, challenges, complexities, required test-data and limitation you have. Once you are ready with this information, you can proceed with next steps. On the basis of above information, you can decide what type of framework is most suitable to you.
But before starting, you must take some time to decide your strategies about..
1. Object Identification
2. Test-Data
3. Function Library
4. Error Handling
5. Controller script
6. Documents and Manuals
1. Object Identification:
How to identify objects i.e. using Object Repository or Descriptive programming or both. As per my understanding, dont’t try to stick on one particular. Depending on the application/object types, mixed approach is most fruitful most of the time.
2. Test-Data:
How to manage you data? DataTable or Excel or may be flat/csv files.
3. Function Library:
Be clear about what type of function libraries you are going to use and why.
4. Error Handling:
Whets your plan to handle errors? Be clear about it.
5. Controller script:
Design a controller script, which will control all your automation. It should be neat. This helps to understand what actually you are going to call.
6. Documents and Manuals:
Automation Framework is a set of guidelines and process you use to manage and optimize your automation testing. In simple words, Framework is a way to do the things in fashioned and organized manner! Framework is nothing but a concept.
It’s always possible to work without framework but you’ll be doing a lot of rework, everything will be here & there and in most of the time you will end-up with a mess, specially in the large projects.
Framework lets you predefine your automation plans, strategies and how you are going to proceed.
Types of Framework:
Framework can be of several types, but here are three main types of frameworks-
1. Keyword driven framework
2. Data driven framework
3. Hybrid framework
But this is only theoretical. Practically, there is no ‘Chinese Wall’ between the framework types.
In every organization you work, you’ll find that it’s quite different from the other and not only on organization level, you can feel the difference within different projects!
Yess, but most of the them could be mapped with Hybrid type and I like it!! :)
Hybrid framework has no boundaries and open to take benefit of all possible type of frameworks.
How to design a framework?
I have done a lot of automation projects and designed a lot a frameworks, but seriously guys, I never used any particular type of framework!
Practically, every application/project has its own expectation. You just need to start your work in organized way and believe me friends, at the end of the day; your framework will be ready automatically!! Sounds crazy??
You can’t design a complete framework and then start automation! You start automation and framework will start building simultaneously.
The first step of any test automation framework is to do a quick POC with few high priority test cases. By doing POC, you will identify the object identification issues, challenges, complexities, required test-data and limitation you have. Once you are ready with this information, you can proceed with next steps. On the basis of above information, you can decide what type of framework is most suitable to you.
But before starting, you must take some time to decide your strategies about..
1. Object Identification
2. Test-Data
3. Function Library
4. Error Handling
5. Controller script
6. Documents and Manuals
1. Object Identification:
How to identify objects i.e. using Object Repository or Descriptive programming or both. As per my understanding, dont’t try to stick on one particular. Depending on the application/object types, mixed approach is most fruitful most of the time.
2. Test-Data:
How to manage you data? DataTable or Excel or may be flat/csv files.
3. Function Library:
Be clear about what type of function libraries you are going to use and why.
4. Error Handling:
Whets your plan to handle errors? Be clear about it.
5. Controller script:
Design a controller script, which will control all your automation. It should be neat. This helps to understand what actually you are going to call.
6. Documents and Manuals:
HP QTP Data Table Pane
The Data Table contains one Global tab plus an additional tab for each action in your test. The Data Table assists you in parameterizing your test. To view the Data Table, click the Data Table toolbar button or choose View > Data Table. The Data Table is a Microsoft Excel-like sheet with columns and rows representing the data applicable to your test.
HP QTP Panes Active Screen Pane
The Active Screen provides a snapshot of your application as it appeared when you performed the corresponding step during a recording session. An Active Screen can be captured for every step you record.To view the Active Screen pane, click the Active Screen button or choose View > Active Screen.
The Active Screen enables you to parameterize object values and insert
checkpoints, methods, and output values for almost any object in the
page after you finish your recording session, even if your application
is not available or you do not have a step in your test corresponding to
the selected object.
You can specify the level at which QuickTest captures and stores
information on objects while recording tests. For example, you can
instruct QuickTest to capture all properties for all test objects on the
captured screen, or only the properties of the recorded objects and
their parents.
Subscribe to:
Posts (Atom)