This is the third tutorial in our series on QuickTest Professional Training.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
In our preceding tutorial, we discussed the use of the Keyword View.
The content of today’s article is centered on integrating steps into a QuickTest Professional test from the keyword view. However, before we delve into integrating the steps, we should first understand the various types of steps that can be incorporated.
Incorporating Standard Steps from Keyword View
#1) Standard Step: A standard step pertains to any action that is enacted on an object. For example,, this could encompass setting a value in an edit box or choosing an option from a drop-down list.
#2) Checkpoint Step: A checkpoint is a step in a QuickTest Professional test that compares an object’s expected property/state to its actual value. This serves as a verification procedure to ensure that the application being tested is operating as expected.
During the execution of this step, QuickTest Professional cross-checks if the anticipated and actual values align. If they align, the checkpoint succeeds; if not, it fails. Evidence of checkpoints can range from verifying if a checkbox is chosen or if a specific text is evident on the screen.
QuickTest Professional offers ten built-in checkpoints, and users can also generate custom checkpoints by crafting programmatic conditions. We will detail all varieties of checkpoints in later articles.
#3) Output Value: The output value, as it’s aptly named, is a variable that preserves the result of a specific step in a test. This value can then be exploited as an input parameter for forthcoming steps. However, it should be mentioned that the output value is only accessible during the test duration and is reset thereafter. We will delve into this topic in greater detail in due course.
#4) Comments: Comments are non-executable steps injected into the script to enhance its readability and comprehensibility.
#5) Conditional and Loop statement.
#6) Other: These are declarations employed to structure the programming logic. Examples include synchronization statements and writing to test results.
Now we shall initiate the integration of a standard step. To ease the process, we will concentrate on the “item,” “operation,” “value,” and “documentation” columns in the keyword view. The remaining columns are seldom utilized.
To incorporate a step, click in an empty area in the keyword view and choose Insert -> New Step from the primary menu.
An alternative is to right-click on an existing step and select Insert new steps from the menu.
Both of these options will generate a new line after the chosen step. If a container object is selected, the fresh step will be formulated as a sub-step. If the last-level object is chosen, the new line will be inserted as a sibling.
Behold how the newly incorporated line appears. It functions as a blank template that can be modified to comply with the test prerequisites.
The new line initiates with a “Select an item” dropdown menu.
Given that every operation necessitates an object, selecting an item is crucial. Diagrams of items include test objects, statements, utility objects, or comments. Test objects nested under container objects are displayed in the dropdown list.
If the user requires an item that is not listed in the dropdown list, it can be chosen from the Object Repository. This introduces us to the concept of the Object Repository, which acts as a centralized storage facility for all objects utilized in a test.
In case the user requires an item not included in the dropdown list, they can pick it from the Object Repository. This is the first time we introduce the Object Repository. Essentially, the Object Repository is a database that consolidates all the objects used in a test.
In case the user requires an item that does not appear in the dropdown menu, it can be chosen in the Object Repository. This Object Repository operates as a warehouse or database storing all the objects involved in a test.
In our example, when aggregating a new step under the sub-level steps of the Login Dialog, the items available for selection are “Agent Name,” “OK,” and “Password.”
If the user requires an item that is not present in the dropdown list, it can be chosen from the Object Repository. This is the first time we mention the Object Repository in this series. So, what does it encompass? Simplistically speaking, the Object Repository is a place where all objects employed in a test are stored.
Upon selecting “Object Repository” from the dropdown menu, the following view is exposed:
As such, an item can be chosen either from the list displayed or from the Object Repository. The subsequent stage is to outline the operation to be enacted on the chosen object. Clicking on the Operation column discloses a list of operations applicable specifically to the selected object type.
This list fluctuates depending on the type of object selected. For instance, a dialogue object will possess different operations compared to an edit box.
Pick the desirable operation
The consecutive column is labeled as Value. This column operates as the argument for the chosen operation. Clicking on the Value column exposes the possible arguments:
If an operation necessities multiple arguments, each argument will be delineated as separate cells in the Value column.
The “Type” operation on the “FlyFrom” item necessitates keyboard input. Clicking on the icon in the Value column reveals a dialogue to organize the value.
As corroborated in the above dialogue, the value can be a “Constant” that is manually typed into the textbox or parameterized by choosing it from a datasheet locale, generating a random number, or utilizing an environment variable. The topic of parameterizing values will be detailed later on.
In our instance, we will key in “Test” in the constant field and click OK. Here is what the generated line looks like:
It’s crucial to acknowledge that the “Documentation” field is automatically populated with a description corresponding to the operation executed on the chosen item.
In conclusion, we have delved into the topic of “Integrating a standard step to a test from the Keyword View”. We have inspected the varying kinds of steps that can be incorporated from the Keyword view and furnished an in-depth analysis of the steps involved in integrating a Standard Step.
Look forward to more articles on the QuickTest Professional keyword view in forthcoming tutorials. We will explore other kinds of steps, conditional and loop statements, and demonstrate how the Keyword view can be employed to alter or remove test steps.
Please provide your feedback to help us improve this QuickTest Professional training article series. Don’t hesitate to share your queries in the comments section below. Remember to sign up for our email newsletter since there are many more articles to come in this series.
Have faith, this will be the most extensive QuickTest Professional training article series you’ve ever come across online!