HP QTP Utility Statements : ManualStep Statement
September 10, 2018
HP QTP Utility Statements : ManualStep Statement
Welcome to this post! – ” HP QTP Utility Statements : ManualStep Statement”.
If you are looking for HP UFT, QTP utility statements and their usages, then you are at right place. This post “HP QTP Utility Statements : ManualStep Statement” consists of concept discussion and usage discussion. Go ahead and enjoy reading…
This discussion will help you prepare well if you are going for the interview and can help you if you need the function to be used in your project test suite.
ManualStep Statement
Abstract
The ManualStep statement represents a manual step in a business component. The statement in itself falls under the category of utility statements and not utility objects. Remember there is a difference between utility statements and utility objects.
Before we dig down deep into the usage let’s quickly visit some general questions.
In the interview usually, you might be questioned in different ways like:
- How to define manual step in QTP?
- Can you define manual step in UFT script?
- What are the objects and parameters of ManualStep statement?
- Is ManualStep is an object or statement?
- If you have business component, can you include business component?
Discussion
First of all, this statement is available as part of Business Components only and cannot be used with regular QTP test script.
Now lets try and understand how it works.
Suppose you have a business component and components with manual steps. If you try open a manual component in QTP or UFT, it converts it to a business component; that is automatically converts each of the steps in the manual component to ManualStep statements, and includes the step name, description, and expected result as argument values of the ManualStep statement.
You can also insert a ManualStep operation to add manual steps to your business component, or edit existing ManualStep statements. All modifications you make in test to the component’s ManualStep operations are reflected in the Component Steps tab and Automation tab of the component in Quality Center and vice versa, post you save the changes.
Points to note here:
- The manualstep statement is intended for use only with business components.
Syntax
ManualStep(Name, [Description, ExpectedResult])
Let’s see the parameters and their usage description for this statement:
Argument | Type | Description |
Name | String | The name of the manual step. |
Description | String | This is Optional. The content of the manual step (its description). |
ExpectedResult | String | This is Optional. The expected result in the application you are testing after the manual step is performed. |
This brings us to the end of our discussion on “HP QTP Utility Statements : ManualStep Statement”.
I really hope you have enjoyed reading this short post. If you have any doubt on this please feel free to add your comment below.
And if you like to read more on UFT or QTP Technical Interview Questions please follow below links:
UFT Technical Interview Questions – Set 1
UFT Technical Interview Questions – Set 2
How to Download Resource From QC\ALM?
How to Upload Resource To QC\ALM?
Or if you prefer General Interview Questions please follow below links:
UFT General Interview Questions – Part 1
UFT General Interview Questions – Part 2
If you would like to keep track of further articles on UFT (QTP). I recommend you to SUBSCRIBE by Email and have new UFT articles sent directly to your inbox.