Ans: To call non-reusable existing actions from the current test script, you need to call to copy action. Follow the steps as mentioned

1. Choose Insert > Call to Copy Action. The Select Action dialog box opens.
2. Use the from test browse button to find the test that contains the action you want to call. The Action box displays all available actions in the test you selected.
3. In the Action list, select the action you want to call
4. Decide where to insert the call to the action and select At the end of the test or After the current step
5. Click OK.

Ans: Split action that is stored with your test into two sibling actions or into parent-child nested actions. When you split an action, the second action starts with the step that is selected when you perform the split action operation. Follow the steps to split the Actions

1. Choose Edit > Action > Split Action, click the Split Action button, or right-click the step and choose Action > Split. The Split Action dialog box opens.
2. Choose one of the following options:

Independent of each other. Splits the selected action into two sibling actions.

Nested (the second action is called by the first). Splits the selected action into a parent action whose last step calls the second, child action.

Ans: Data Table parameters are used, if you want to parameterize the test case, based on the external data. You keep the data into a Data Table, which is in excel format, and do parameterize.

Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, Quick Test uses a different value from the Data Table.

When Data Table is selected as the parameter type, the Parameter Options dialog box enables you to configure your parameter to use values from the Data Table.

Ans: You can store the variable you want to pass an environment variable in one action and then if you need to access the same variable in another action first you have to call that environment variables in second action, store it in some variable and use it.

Ans: Since QTP identifies a virtual object according to its boundaries. If the screen resolution changes significantly, objects may not be recognized. So, in the automation frame work guide lines the screen resolution details needs to be mentioned.

More about Virtual Objects:

Marking an object's boundaries specifies its size and position on a Web page or application window. When you assign a test object as the parent of your virtual object, you specify that the coordinates of the virtual object boundaries are relative to that parent object.

When you record a test, Quick Test recognizes the virtual object within the parent object and adds it as a test object in the object repository so that Quick Test can identify the object during the run session. Quick Test also recognizes the virtual object as a test object when you add it manually to the object repository.

Ans: MTB

Ans: Test results file bar, Test results bar, test result tree, test result details, status.

Ans: Objects are not in editable mode when the shared object repository opened from object repository manager by default. Because the shared object repository may be used with multiple action of the respective tests. So, the shared object repository needs to be protected from unwanted editing.

If you want to edit the objects, the shared object repository need to be enabled for editing.

Choose File -> Enable Editing from the Object Repository Manager. Now you can edit the objects

Ans: The four types of exceptions are

• Pop up exception
• Object state exception
• Test run error exception
• Application crash exceptions

Ans: After merging object repositories the conflicts can be resolved as below:

1. In the target object repository, select an object that had a conflict, as indicated by the icon to the left of the object name. The conflicting objects are highlighted in the source object repositories.
2. In the Resolution Options pane, select a radio button to choose an alternative resolution method. The target object repository is updated according to your selection and redisplayed.
3. In the Resolution Options pane, click the Previous Conflict or Next Conflict buttons to jump directly to the next or previous conflict in the target object repository hierarchy.
4. Repeat steps 1 through 3 to modify additional conflict resolutions, as necessary.
5. Save the target object repository