How to Migrate From HP Quality Center to qTest
How to Migrate From HP Quality Center to qTest
With more alternatives to HP's mainstay Quality Center becoming available, we have a look at migrating from Quality Center to QASymphony's qTest.
Join the DZone community and get the full member experience.
Join For FreeWSO2 is the only open source vendor to be named a leader in The Forrester Wave™: API Management Solutions, Q4 2018 Report. Download the report now or try out our product for free.
Moving data from a legacy test case management system to a modern system can be a lot of work. But not for you!
QASymphony makes it easier than ever to bring your data on HP Quality Center over to QASymphony qTest through their migration strategy. However, before I get into the details of how this is accomplished, I'd to like walk through some reasons you should switch from Quality Center to qTest and why NOT to migrate all artifacts.
Wait, what? Believe it or not, there are reasons to not migrate all that test data you are worrying about.
Reasons Not to Migrate Everything
Your Junk Is Not Your Treasure
It's important to acknowledge that not all the data you collect remains good data to transfer. Thousands of test cases that have never found a defect and always pass could point to low-value regression suite. Five-year-old projects with complex traceability reporting no longer need to be maintained for audit coverage.
One of our large customers in the logistics industry decided altogether not to migrate any of their test case data. Their analysis showed that there was too much uncertainty with the accuracy of their existing test cases. Therefore, they decided to leverage qTest eXplorers documentation abilities to design and create test cases for reuse.
[See Creating Test Case with qTest eXplorer]
New Tools Prompt New Data Outlooks
When moving off of HP Quality Center, your organization probably already purchased or looked into other ALMs for roadmap, requirement, and defect management. Most companies I talk to use JIRA, VersionOne, or CA Agile Central (formerly Rally). This forces a new outlook on what data is important to keep, and what needs to be ignored.
If you are using JIRA to create User Stories, migrating all your HP requirements may not be necessary. If you are logging defects in VersionOne, then the links between your current HP test cases and defects wouldn’t be useful in test case management tool.
How QASymphony Migrates Your Data
QASymphony provides a unique solution that migrates your data from Quality Center directly into qTest. We're compatible with Quality Center and HP ALM versions 10, 11, and 12 and can migrate from instances on your servers or in the cloud.
Here is a simplified rundown of how the migration process works:
- Export a Quality Center project out of the system in their native file format (.qcp).
- Download and run our Quality Center migration tool.
- Load the .qcp file into the qTest importation wizard.
- qTest wizard will decode the .qcp file, create custom fields and values, and import your requirements, test cases, and defects.
- Repeat this same process with the next project, if applicable.
What Artifacts Are Migrated
- Release and Build to Test Plan
- Reqs (including custom fields + attachments)
- TCs (including custom fields + attachments)
- Req-to-TC linkages
- Test Labs + Results
- Defects (including custom fields + attachments)
- Users assigned to each project
Request a free migration consultation and to learn more about how to ditch your legacy software.
IAM is now more than a security project. It’s an enabler for an integration agile enterprise. If you’re currently evaluating an identity solution or exploring IAM, join this webinar.
Like This Article? Read More From DZone
Published at DZone with permission of Ryan Yackel , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}