HP QTP Utility Statements : ExitComponent Statement

Welcome to this post! – ” HP QTP Utility Statements :ExitComponent 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 : ExitComponent 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.

ExitComponent Statement

Abstract

The ExitComponent statement is used to get the current component exited and return to the parent calling action. This statement is called as a priority step or statement whenever defined. 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:

1. How to get current iteration of the component stopped?
2. Can you use the ExitComponent and exitTest one after the other?
3. What are the objects and parameters of ExitComponent statement?
4. is ExitComponent is an object or statement?
5. What happens to next component in order of execution when prior one is exited?
6. Can you use the return value of the exit component into another business process test component?

Discussion

Suppose you have created the test with several components. Each component of the Business Process test needs to be executed in order of execution. And in case of some unexpected errors, business cases you might want to exit the current component. Now, exiting the component and returning a status of the current component can be done via this ExitComponent Statement.

Hence, officially the main purpose of the ExitComponent statement is to exit the current component run. The pass or fail status of the component remains as it was in the step prior to the ExitComponent statement.

Points to note here:

1. The ExitComponent statement and its return value are displayed in the Run Results.
2. If the component is not part of a component group, then any remaining component iterations are skipped and the run proceeds to the next component in the test.
3. If the component is part of a component group, then the entire component group is skipped and the run proceeds to the next component after the component group.
4. The return value can be stored in output parameter to be used in other Business Process Components or Tests as an input parameter.

Syntax

ExitComponent [(RetVal)]

Let’s see the parameters and their usage description for this statement:

Example

The following example uses the ExitComponent statement to end the component run if a checkpoint on the userPassword edit box fails.

'ExitComponent example

res = Browser("Home").Page("Login Page").WebEdit("userPassword").Check ( CheckPoint("userPassword") )

If res = False Then

    ExitComponent

End If

This brings us to the end of our discussion on “HP QTP Utility Statements : ExitComponent 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.