If you are working with a Premier edition Quality Center server, then you can also import and share your resources across different projects. You can synchronize these assets in both projects when changes are made. This functionality also enables you to reuse your existing assets instead of creating new assets whenever you create a new project. For example, you can create a set of template assets to use as a basis for new projects.
Using the Resources and Dependencies Model
In previous versions of QTP and Quality Center, a test's associated resource files (such as shared object repositories, function libraries, recovery scenarios, and external data tables), were stored in Quality Center as attachments, while files associated with an application area were stored in a standalone Resources folder in the Business Components module.
Quality Center 10.00 introduces a new Test Resources module. This module enables you to store all of these resources as separate entities that are linked to their owners and marked as dependencies. Tests or actions that call other tests are also linked as dependencies.
When you select a QTP test, business process test, or individual component in the Quality Center test or component tree, you can view these dependent resources and tests in a new Dependencies tab. The Dependencies tab shows all Quality Center entities that are used by your testing document as well as all entities that are using it. For example, if your QTP test is associated with two function libraries, and the actions in your test are associated with three object repositories, these entities will be displayed in the Using table of the test's Dependencies tab. If one of the actions in your test is called by another test, then that calling test will be displayed in the Used by table.
In QTP, you can also view the action-specific dependencies in the Used By tab of the Action Properties dialog box.
Quality Center recognizes assets that are linked as owned by or owner dependencies and ensures that these important relationships are maintained when you import or create baselines, rename or move resources, select to delete resources, or perform other operations that can impact these relationships.
Note: If required, you can continue using the previous attachments model for all or some of your QTP assets. However, if you use the old model, you will not be able to take advantage of many of the features associated with the resources and dependencies model.
Go Back to -> QTP 10 integration with QC.