The migration process requires that you add new migration plug-ins to the existing ClearQuest Eclipse client. These new plugins add an RQM Export function to the client. The RQM Export function starts an Export wizard in which you select the test assets to be migrated and the destination of that migration.
With this migration, data flows in XML fragments via HTTP from the ClearQuest client to the Rational Quality Manager server, as shown in the following figure:
If your Rational ClearQuest Test Manager projects are integrated with test scripts from Rational Manual Tester, you must migrate your manual test scripts before migrating your Rational ClearQuest Test Manager projects. If you have done the reverse, simply repeat the Rational ClearQuest Test Manager migration.
For migration, the test script location in Rational Manual Tester must match the location of those scripts in Rational ClearQuest. In particular, if a UNC path name is used in Rational ClearQuest Test Manager to refer to the manual test scripts, the same path must be used to migrate the manual test scripts to Rational Quality Manager. This path is used to ensure that the scripts align properly in the Jazz™ Team Server.
If your Rational ClearQuest Test Manager projects contain test cases with associated automated test scripts, you must import or refer to the automated test scripts in Rational Quality Manager before migrating your Rational ClearQuest Test Manager projects.
When importing the scripts, you must import them from a shared resource location, using a UNC path, rather than from a local computer. The UNC path that you provide during the import must match the File Location UNC path that was used in the Rational ClearQuest Test Manager project for the automated scripts.
Rational Quality Manager checks to see that these paths match when associating the test cases to the automated test scripts during the migration. If the paths do not match, test execution fails.
If your Rational ClearQuest Test Manager projects are integrated with requirements from Rational RequisitePro®, you must take the following steps to prepare for a successful migration:
The RAProject records contain the Rational RequisitePro database information for Rational ClearQuest. One of the fields in these record is the ReqWeb server URL. This is the same URL used in Rational Quality Manager to connect to RequisiteWeb. You must use this exact URL in Rational Quality Manager so that the requirement information in Rational ClearQuest Test Manager migrates correctly.
If you use Rational ClearQuest for tracking defects, you must set up the Rational ClearQuest Connector or the Rational ClearQuest Bridge before migrating test assets from Rational ClearQuest Test Manager. Otherwise, links to defects will no longer be available.
If you use the Rational ClearQuest Connector, you can then use the synctool command to migrate the defects into Rational Quality Manager. You must migrate the defects before performing the Rational ClearQuest Test Manager migration.
With the Connector, defects that are created in Rational ClearQuest are visible in Rational Quality Manager and vice-versa.
See The IBM Rational ClearQuest Connector for details.
The following Rational ClearQuest Test Manager asset types can be migrated to Rational Quality Manager:
Rational ClearQuest Test Manager asset | Rational Quality Manager asset |
---|---|
Test plans | Test plans |
Test cases | Test cases |
Configured cases | Test execution records |
Test suites | Test suites |
Manual test scripts | Manual test scripts |
Committed test logs and suite logs | Test execution results |
Links to requirements | Links to requirements within test plans and test cases |
Links to defects | Links to defects within test execution results |
Iterations (must be associated with a test plan, test case, or configured test case) | Test schedules |
Configurations | Test environments |
Computers | Lab resources |
Computer groups | Resource groups |
Association to automated scripts | Test scripts (references to external test scripts) |