LIBRARIES
1) Quality Center Premier Edition includes all Libraries module functionality and Quality Center Enterprise Edition includes some functionality. This module is not available with Quality Center Starter Edition.
2) Libraries tree. Displays libraries and baselines in a hierarchical tree structure.
3) Details tab. Describes the library folder, library, or baseline currently selected in the libraries tree.
4) The Entities pane lists the root folders associated with the library.
5) Quality Center Premier Edition: The following additional tabs are available
for importing libraries:
a) Imported By tab. Lists the projects that imported the selected library
b) Imported From tab. Displays details about the library from which the
currently selected library was imported.
6) The Libraries menu contains commands that enable you to add library folders, libraries and baselines. It also contains a command enabling you to compare libraries and baselines.
7) Quality Center Premier Edition: Import Library. Imports a new library and adds it to the libraries tree.
8) Create Baseline. Creates a baseline and adds it to the libraries tree.
9) Compare To. Compares the currently selected library or baseline with other libraries or baselines.
10) Delete. Deletes the selected item. Deleting a library folder also deletes its libraries and baselines. Deleting a library also deletes its baselines.
(Lets read more)
11) You can add user-defined fields and change the label of any of the fields in the Details tab. You can also customize project lists.
12) You can use the Script Editor to restrict and dynamically change the fields and values in the Libraries module.
13) You create libraries in the Libraries module. After you create a library, you can create and compare baselines for the library to track changes in your project over time.
14) In the Libraries module, you define a hierarchical libraries tree to create and manage your libraries.
15) A library represents a set of entities in a project and the relationships between them. The entities in a library can include requirements, tests, test resources, and business components.
16) After you create a library, you can create a baseline. When you create a baseline for a library, you have a snapshot of the library at a specific point in time.
17) Baselines enable you to keep track of changes made to your project over time.
You can compare baselines at all stages of the application development life cycle. You can use a baseline to mark any significant milestone in the application development life cycle. You can compare two baselines in a library to review changes made to requirements in the library over time.
18) A baseline includes all the entities defined in the library, including requirements, tests,
19) and test resources. Baselines also include the relationships between the entities in the library, such as traceability and coverage. Baselines enable you to keep track of changes made to your project over time.
20) When you create a baseline, Quality Center first verifies the library. The link verification process checks whether there are entities in the library that are associated with entities not contained in the library.
21) You can use baselines in the following ways:
a) Compare two baselines to view the changes in a library at different stages of development.
b) Pin a test set to a baseline. This associates the test set with the tests stored in a baseline that you specify. This ensures that when you run the test set, Quality Center runs the versions of the tests stored in a baseline you specify. A test set that is pinned to a baseline can include only tests that are included in the baseline. When you pin a test set to a baseline, tests that are not a part of the baseline are removed from the test set. In addition, all test runs are deleted from the test set.
22) Quality Center Premier Edition: Use a baseline to share the entities in a library. This enables you to reuse the library’s entities within your project, or in a different project. To import a library, the library must contain a baseline.
23) You can also compare a baseline to the current entities in the library.
24) Quality Center Premier Edition: You can also import a library. Importing a library enables you to reuse an existing set of entities.
25) Creating and managing libraries and baselines requires appropriate user permissions.
26) You define a hierarchical framework for your libraries by creating a libraries tree that can contain folders and subfolders.
27) A library name cannot include the following characters: \ / : * ? " < > |
28) Under Select Entities, select folders to include in the library. You can select one or more root folders for each of the Requirements, Business Components, Test Plan, and Test Resources modules.
29) For each entity in the library that is associated with another entity in the project, Quality Center verifies that the associated entity is also contained in the library.
30) If there are entities in the library that are associated with entities not contained in the library, Quality Center creates a list of these entities, and the Broken Links Verification dialog box opens.
31) When the process is complete, view the log before refreshing the display. If you refresh the display after the baseline is created, the View Log button is no longer displayed, and you cannot view the log.
32) You can compare two baselines in a library. You can also compare a baseline to the current entities in the library.
33) Quality Center does not consider changes made to Target Release and Target Cycle fields when determining whether an entity has been modified.
34) If coverage or traceability between two entities was deleted and then added again, those entities are considered modified.
35) A deleted or moved entity is displayed in its original location in the tree, indicated by a placeholder. This maintains the hierarchical structure, enabling you to compare changes between baselines.
36) You can view all versions of an entity that are stored in a baseline. This includes entities in the Requirements, Business Components, Test Plan, and Test Resources modules. You can also compare two baseline versions when the baselines belong to the same library.
37) If you are viewing information for a QuickTest test, clicking the Test Script button opens the test in a QuickTest viewer, enabling you to view the test or open the test in QuickTest.
38) You can rename a library folder, library, or baseline.
39) You can move a library folder or a library to a different location in the libraries tree. Moving a library folder also moves its libraries and baselines. Moving a library also moves its baselines. You cannot move a baseline or the root Libraries folder.
40) You can also move a library folder or a library to a new location in the libraries tree by dragging it.
41) You can delete a library folder, library, or baseline. You cannot delete a library folder that contains libraries, or delete a library that contains baselines. Deleting a library or baseline does not delete the library’s entities from your project.
42) If you delete a baseline, you can no longer compare between the baseline’s library and another library that was imported from or synchronized with the baseline.
43) Deleting a baseline clears the baseline from pinned test sets.
44) Compare an entity between two baselines from the History page of the Requirements, Test Plan, and Test Resources modules.
45) Compare two versions of an entity from the History page of the Requirements, Test Plan, and Test Resources modules.
46) Compare an entity between two baselines from the Compare Baselines Tool dialog box.
47) Compare an entity between two libraries from the Compare Libraries Tool dialog box.
48) When you compare two versions of an entity, not all sidebar buttons are displayed. The buttons available depend on the information stored under version control.
If you are comparing a QuickTest entity, the QTP Comparison button is displayed, enabling you to open the QuickTest Asset Comparison Tool.
49) For traceability and coverage, if a linked entity is marked as both Deleted and Added, or is displayed as Missing on both sides, this can indicate that the link between the entities was deleted and then added again.
50) You can import a library to share and reuse the library’s entities within a project or in different projects across your enterprise. You import a library by selecting a baseline in another library from which to import. You can import a library from the same project, or from a different project.
51) You can compare associated libraries at all stages of the application development life cycle. For example, you can compare an imported library with the source library from which it was imported.
52) When changes are made to entities in a library, you can synchronize libraries to update the entities in an associated library. Importing and synchronizing libraries requires appropriate user permissions.
53) You can also share defects across multiple Quality Center projects. You share and synchronize defects using the HP Quality Center Synchronizer.
54) Library examples - Reuse requirements and tests for a new release, Create a set of requirements, tests, and resources for use by multiple applications, Update imported libraries with changes made in the source library, Update a source library with developments in an imported library.
55) You can import a library to your libraries tree from the same project or from a different project. When you import a library, the library is added to your libraries tree, and the library’s entities are copied to the corresponding modules in your project. If the library includes associated entities, such as requirements that have test coverage, this relationship is also copied. An imported library is displayed with an Imported Library icon 
in the libraries tree.
in the libraries tree.56) You import a library by selecting a baseline in another library from which to import. After you import a library, Quality Center automatically creates a baseline for the new library in your project. This baseline is the basis for comparing the libraries at any point in time and should not be deleted.
When you import a library, Quality Center first verifies that the library can be successfully imported. The verification process includes the following checks:
a) Requirement type check - Checks that your project contains the necessary requirement types. If the source library contains customized requirement types, your project must contain the same requirement types.
b) Entities compatibility check. Checks that your project has the necessary extensions enabled. If the source project has a Quality Center extension enabled, and the source library includes entities for that extension, your project must also have that extension enabled.
57) You cannot import a library under the same previously imported library in the requirements, test plan, or test resources tree.
58) You can import a library by selecting a baseline from the same project or from a different project.
59) You cannot import an imported library.
60) You can view information about associated libraries. You can view details of projects that imported a selected library in the Imported By tab. You can also view details of the source project from which a library was imported in the Imported From tab.
61) You can compare two associated libraries. The Compare Libraries Tool enables you to compare an imported library with the source library from which it was imported.
62) If coverage or traceability between two entities was deleted and then added again, those entities are considered modified.
63) To synchronize the libraries, click the Synchronize button. Data from the other library is copied to your library.
64) You can synchronize two associated libraries to update one library with changes made in another library. You can update an imported library with changes made in the source library. You can also update a source library with changes made in the imported library.
65) Entities in a library must not be edited during synchronization. If entities in your library are being edited by another user during the synchronization process, synchronization cannot complete successfully.
66) All entities in your library must be checked in before synchronization. If an entity in your library is checked out, synchronization cannot complete successfully.
67) You can send email about a library to other users. This enables you to inform them about the status of your libraries. A link is included in the email that enables the recipient to go directly to the library.
No comments:
Post a Comment