Beruflich Dokumente
Kultur Dokumente
COPYRIGHT 2005 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners. Corporate Headquarters: Borland Software Corporation, 20450 Stevens Creek Blvd., Suite 800, Cupertino, California 95014 800-632-2864 or 408-863-2800 www.borland.com Offices in Australia, Brazil, Canada, India, Ireland, Italy, Japan, Korea, the Netherlands, New Zealand, Russia, Singapore, Spain, Sweden, Taiwan, the United Kingdom, and the United States.
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration Business Value . . . . . . . . . . . . . . . . . . . Setting Up the Integration . . . . . . . . . . . . . . . . . . . . Configuring the Multiple Mercury Servers Environment . . . Enabling the Integration in CaliberRM . . . . . . . . . . . . . Using the Mercury Integration . . . . . . . . . . . . . . . . . Linking Requirements to Mercury Objects. . . . . . . . . . Viewing Traces to Mercury Objects in the Traceability Matrix Using Mercury Objects in Document Factory . . . . . . . . Test Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . Publish Requirements Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 2 2 2 3 3 4 5 5 6
Introduction
The integration between CaliberRM and Mercury Quality Center and TestDirector (referred to in this document as Mercury) works the same for both TestDirector and Quality Center. For the Mercury versions that CaliberRM supports, see the release notes. This integration is designed to ensure that testers validate the system against the latest state of requirements. The integration provides you with a seamlessly integrated, bestof-breed software delivery toolset that spans various phases and roles in the application lifecycle. The integration allows you to leverage the strengths of two industry leaders, and enables bidirectional information flow between analysts and testers. This flow helps increase overall communication, efficiency, and quality in the software delivery process. CaliberRM contributes to making software a more managed business process by enabling teams to capture and manage the requirements, resources, tasks, timelines, and assets within the software development cycle. The alignment of these assets and phases can be a critical factor to the success or failure of software projects. Note: This document supersedes the information provided in Chapter 27: Project Integrations in the CaliberRM User Guide. The Mercury integration features:
I
CaliberRM Mercury Traceability allows you to trace CaliberRM requirements to Mercury objects CaliberRM Test Wizard helps create Mercury tests from CaliberRM requirements and ensures that all requirements are tested by giving the up-to-date status on requirements that have or do not have associated tests CaliberRM Publish Requirements Wizard exports requirements from CaliberRM to Mercury
Note: There are no special requirements when migrating to a new Mercury integration.
Viewing the test status within CaliberRM provides an analyst with a requirement validation status by using the links between Mercury objects and CaliberRM requirements Assessing requirement coverage provides an analyst with a way to measure how many requirements have been validated and how many requirements are left to validate by using the traceability set between Mercury objects and CaliberRM requirements
Reusing requirements description text in test creation and starting the evaluation of test assets from requirements design by using the Test Wizard Recycling current requirements in testing tools by using the Publish Requirements Wizard
In t ro d u c ti o n
Configuring the multiple Mercury servers environment. Enabling the integration in CaliberRM at the project level.
http://[host:port]/tdbin for TestDirector, where host is your Quality Center/ TestDirector server name and port is the port location for the server. The Login screen displays.
2 Click Add-ins Page. The Mercury Add-ins page displays. 3 Select Mercury Quality Center Connectivity for Quality Center or TestDirector
displays.
5 Click Open. The files are installed.
Note: If you use a database other than MS Access, you may need to install additional components on the Mercury test server to allow communication with the database (see your Mercury documentation for more information).
Warning!
Migrating your Mercury database to another server using the Mercury Export/Import changes the Mercury Object IDs and invalidates Requirement-to-Test Object Trace relationships. Please contact CaliberRM support for information about how to minimize the impact of relocating your database.
I nt e g ra t in g Ca l ib e r RM wi th M e rc u ry Q u a l it y Ce n te r a n d T e s tD i re c to r
5 Click the Browse button to navigate to the desired configuration file. The default
location is C:\Borland\CaliberRMServer\Vendorconfig\qc_config.txt.
6 Locate the qc_config.txt file and click the Open button to add the path to the file in
the Configuration File text field. Note: The default Mercury address specified in the configuration file is http://localhost:8080/qcbin.
7 Click the Edit button to open the configuration file and specify the address(es) of a
Mercury server(s) of a single version. Note: You can set up filters per Mercury servers, domains, and projects that display on the Quality Center tab of the Traceability Modification window using the instructions from the readme.txt file that is located on your CaliberRM client machine at C:\ Program Files\Borland\CaliberRM\QCAddin\readme.txt. by default. Note: You must restart your CaliberRM client after you edit and save the configuration file to load new configuration settings.
8 Select File > Save to save your edits in the configuration file. 9 Select File > Exit to close the file. 10 Click OK to close the Edit Integration window. 11 Click the Move Left button to add the Mercury integration to the Enabled
Integration(s) list.
12 To save the information, select File > Save Changes. To cancel the changes,
Note: When you access a Mercury project for the first time, the Login to Quality Center Server dialog box displays. Specify a valid user name and password to access the Mercury server.
9 Select a Mercury object you want to trace a CaliberRM requirement to. 10 Select Trace > Trace To from the menu to create a traceability link from a
CaliberRM requirement to a Mercury object . Note: You can create a traceability link from a Mercury requirement to a CaliberRM requirement selecting Trace > Trace From from the menu.
11 Repeat steps 9 and 10 to create any other traces as needed.
U s in g th e M er c u ry I n t e gr a ti o n
12 Click the Save button to save the traces, or click the Cancel Changes button to
click OK. The following information about a linked Mercury object is listed on the Traceability tab:
I I I I I
Object file type icon Traces To: the object name Tag/ID: Mercury object type Status: Suspect or not Project: the Mercury project name
If the Mercury integration becomes disabled for your project, or the Mercury server becomes disconnected, existing Mercury traces appear unavailable. You can right-click a Mercury object in the Traceability tab or the Modify Trace window to select the Properties context menu item and see the corresponding object Properties dialog box. Note: The Mercury integration automatically updates traces created using earlier Mercury integrations except traces to Test Sets. You need to recreate traces to Test Sets.
The items you select are listed in the Rows Filter and Columns Filter areas at the bottom of the Traceability Filter dialog box. These are the items that will appear in the matrix.
6 Click OK. The Mercury filtered view displays.
For more information on the Traceability Matrix, see Chapter 16: Traceability in the CaliberRM User Guide. You can also view Mercury objects in the Traceability Diagram. For more information on the Traceability Diagram, see Chapter 16: Traceability in the CaliberRM User Guide.
I nt e g ra t in g Ca l ib e r RM wi th M e rc u ry Q u a l it y Ce n te r a n d T e s tD i re c to r
Test Wizard
The Test Wizard allows you to leverage requirements to create tests by making a Mercury test for any requirement. This provides an easy way to create tests from all of your requirements by automating test creation process in Mercury. Note: Before you can create tests using the Test Wizard in CaliberRM, you must enable the integration with Mercury in Framework Administrator. To select the requirements for which you want to create tests:
1 In CaliberRM, select Tools > Test Wizard from the menu. The Select
Requirements to Test screen displays. Note: By default the Publish Requirements Wizard exports the requirements from the currently selected CaliberRM project and baseline. To change the CaliberRM server, project, or baseline to select requirements from, click Back. The Connect To CaliberRM Server screen displays. Enter the data you want to modify.
2 Select the requirements for which you want to create tests.
Note: If you select a parent requirement, all child requirements are automatically selected. Clear the child requirements you do not want to test.
3 Click Next. The Connect to Quality Center screen displays. 4 Select a Mercury server name from the Host drop-down list. 5 Click the Connect button to display the list of domains available on the selected
Mercury server.
6 Select a domain to display the list of projects available in the domain. 7 Select a project. 8 Provide a valid user name and password to access the Mercury server. 9 Click Next. The Select The Components For The Test Name screen displays. 10 Select the options for your Test Name.
Note: Requirement Name is the default. Prefix: adds your choice of prefix for the requirement to the test name. Requirement Tag: adds the requirements unique type tag to the test name. Requirement ID: adds the requirements unique ID to the test name. Requirement Name: adds the requirement name; default.
11 Click Next. The Select The Components For The Test Description screen
displays.
12 Select the components you want to add to the test description.
Requirement ID: adds the requirements unique ID to the test description; CaliberRM requirement ID is the default. Requirement Name: adds the requirements name to the test description; CaliberRM requirement name is the default. Requirement Description: adds the requirements description to the test description; CaliberRM requirement description is the default.
T e s t W i z a rd
Note: The Test Wizard places plain text in tests it creates. No images or URL included in a requirement description display in Mercury. Validation: adds the requirements validation text to the test description; CaliberRM validation text is the default.
1 Click Next. The Customize Fields screen displays. 2 Select the UDA you want to add to the list of user-defined fields of your test details.
Note: CaliberRM ID, CaliberRM Owner, CaliberRM Version, CaliberRM Status, CaliberRM Baseline are the default fields. Force updating fields: updates all user-defined fields for the test every time you run the Test Wizard, even if the requirement version is the same.
3 Click the Move right buttton. 4 Repeat steps 14 and 15 to include additional UDAs. 5 Click Next. The Assign The Test To A Folder screen is displayed. 6 Click Select All, or select individual tests to assign to separate folders. 7 Click Assign Folder for each selected test. The Select TestDirector Folders
status of each test created from requirement once the progress is complete.
10 Click Done. The Test Wizard closes.
Requirements to Publish screen displays. Note: By default the Publish Requirements Wizard exports the requirements from the currently selected CaliberRM project and baseline. If you need to change the CaliberRM server, project, or baseline to select requirements from, click Back. The Connect To CaliberRM Server screen displays. Enter the data you want to modify.
2 Select the requirements you want to import from CaliberRM.
Note: If you select a parent requirement, all child requirements are automatically selected. Clear the child requirements you do not want to test. Note: The Publish Requirements Wizard places plain text in requirements it publishes. No images or URL included in a requirement description display in Mercury.
3 Click Next. The Connect to Quality Center screen displays. 4 Select a Mercury server name from the Host drop-down list. 5 Click the Connect button to display the list of domains available on the selected
Mercury server.
6 Select a domain to display the list of projects available in the domain.
I nt e g ra t in g Ca l ib e r RM wi th M e rc u ry Q u a l it y Ce n te r a n d T e s tD i re c to r
7 Select a project. 8 Provide a valid user name and password to access the Mercury server. 9 Click Next. The Customize Fields screen displays. 10 Select the UDA you want to add to the list of user-defined fields of your test details.
Note: CaliberRM ID, CaliberRM Owner, CaliberRM Version, CaliberRM Status, CaliberRM Baseline are the default fields. Force updating fields: updates all user defined fields for the test every time you run the Publish Requirements Wizard.
11 Click the Move right buttton. 12 Repeat steps 10 and 11 to include additional UDAs. 13 Click Next. The Publish Requirements screen displays and shows the status of
Note: You cannot edit Mercury requirements unless you get the permission to modify Mercury requirements from your Mercury administrator. We recommend that you edit the requirements in CaliberRM and republish them to Mercury to keep them in sync. Note: You can publish the same set of CaliberRM requirements to Mercury several times, which updates them.
P ub l i s h R eq u i re m e n t s W i z a rd