Ans: Object repositories needs to be merged, if there are more than one repository is built. And finally if only one repository need to be maintained for the entire application.

For example: If there are 2 QA automation engineers are working to automate the application. Engineer1 is working on module1 and engineer2 is working on module 2. If they individually prepared the shared object repositories respective to their own module. Finally, if they need to maintain the single object repository for the entire application, the two shared repositories of module1 and module2 will merged and built as a single shared object repository.

Ans: When the two object repositories are compared, the Object Repository Comparison Tool displays the Statistics dialog box, which describes how the files were compared, and the number and type of any differences found.

The number and type of any differences between the objects in the object repositories

Identical: Objects that appear in both object repository files. There is no difference in their name or in their properties.

Matching description: different name. Objects that appear in both object repository files that have different names, but the same description properties and values.

Similar description: Objects that appear in both object repository files that have similar, but not identical, description properties and values.

Unique to first file or Unique to second file: Objects that appear in only one of the object repository files.

2) The number of items that are unique to the first or the second file, or are identical in both files.

Ans: By using test>setting>resources>libraries option.

Ans: There are 5 types of output values are available. They are:

1) Standard Output Values

2) Text and Text Area Output Values

3) Table Output Values

4) Database Output Values

5) XML Output Values

Ans: By default the output values will be stored in local or global sheets of Data Table in QTP.

The output value can be seen in the data table only during the run time. After the test run, the value will not be displayed in the QTP data table. But, the output value can be seen the results data table.

Ans: The output values are seen in the data table only during the run time. While running the test, excel (default sheet pointed with the test) will be copied to the results and it will be updated. During the run time the default.xls run results data sheet will be updated. After the test run, the default.xls which is there in the test folder will be re-associated.

If you want to see the run time out put values, you need to go to the test results folder and look for the default.xls file. You can see all the run-time output values there.

Ans: Using dt sheet object we can add runtime parameters to database.

Ans: By default there are two types of check points enabled in Quick Test. Those are:

1) Database check point

2) XML check point (from resource)

Ans: R &D works means basically we can stay it is a verification process. Before you implementing some logic into your function you have to review those to find is there any errors which can be cleared by going through that piece of logic we are going.

Ans: Business Process Testing enables Subject Matter Experts to create tests using a keyword-driven methodology for testing as well as an improved automated testing environment.

Business Process Testing integrates Quick Test with Quality Center and can be enabled by purchasing a specific Business Process Testing license.