How to Test CLM Migration from 5.0 to 6.0 Version
Team,
I need to test the migration from 5.0 to 6.0 version of the CLM, Could any one help me with the following queries:
1. Any standard test cases or test plan available to test the migration
2. What are all need to be tested
3. Any DB queries to run and verify before and after migration
4. Any tools available from CLM to verify the migration
One answer
You should follow the interactive guide instructions in the Knowledge center:
https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.6/com.ibm.jazz.install.doc/topics/interactive_guides.html
I also recommend reviewing the deployment wiki page on migration:
Having done more migrations than I can count over the past 10 years, I can tell you that these instructions are pretty rock solid. When you migrate, you are changing the binaries on the RTC/JTS server(s), and will be upgrading database tables. If you need to validate the data has not been adversely altered, here are the items you should check:
Work items
Source data
Build definitions
User data
For Work items, you can do an easy pre/post comparison by creating a query, and then exporting that to a CSV file. After you upgrade, you will run the same export to another CSV file. You can then compare the two files using a text comparison tool (such as what is in the RTC/Eclipse client). You likely only need to do this on a subset of work items, not all work items (which could be too many to compare).
For build definitions, you can do a similar test, by exporting the build definitions using the ANT tools. Here is the documentation:
Similarly to the work item text comparison I mentioned above, you would do the same here. Run an ANT export before and after the migration, and then compare the two XML files for differences.
For source code, you would load a repository workspace for every stream, and loaded with every component before the migration. After the migration, and after upgrading your client, you would go into the pending changes view. You should have no pending changes coming or going (it will naturally do a compare on all the source members).
Lastly, you can do a similar thing with exporting members using the repotools-jts.sh commands (https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.4/com.ibm.jazz.install.doc/topics/r_repotools_exportusers.html). Do an export before and after the migration, and then compare the results.
If there are any issues on the migration, you will almost certainly see them during the migration process, not in test cases I mentioned above.