My office has recently upgraded to QualityCenter 10, as several members of our team were having issues connecting to QC9 using Internet Explorer 8 with Windows XP SP3. This was as good a reason as ever to switch.
We have been automating our smoke test suite in QuickTest Pro 9.5 over the past year and have recently upgraded to QTP10. The integration of QTP10 to QC9 was seamless and we had experienced no issues executing older scripts in the newer version of the tool. Of course, once we edited an older script, it was upgraded to the latest version. This is understandable.
Once we upgraded to QC10, however, we started experiencing some trouble. All of our prior scripts had started to fail due to external script references not being found. Also, many scripts couldn’t find the associated object repository. This caused some minor panic in our team: potential lost work, hours of required rework, etc.
We next attempted to edit our scripts in order to debug and figure out what we would have to do to fix these issues. That’s when we saw this message:
This is the first time I had heard of the QuickTest Pro Asset Upgrade Tool for QualityCenter. After doing some research, it was determined that this tool was included on the QualityCenter 10 Installation DVD.
The purpose of this tool is to upgrade all QTP scripts currently in your QualityCenter project. You will need to login to your project as a project admin and this tool must run on a machine that has QuickTest Pro 10 installed. There is another important step that took me a bit to figure out, mainly because I failed to read the documentation.
Your local QuickTest Pro installation must have the folder pathing setup to find all external references your scripts may use. This includes paths (in and out of QC) for shared object repositories, function libraries, and other scripts. If this is not set up, the Asset Upgrade Tool will not be able to process your scripts. To set up your folder pathing, in QTP go to Tools –> Options –> Folders.
Executing the upgrade tool is very straightforward, but please read the documentation carefully. The general process is to login to your project, analyze your project, then upgrade your project. It presents a full report of the analysis and upgrade process for your review. It is highly recommended that you make a backup of your project before your upgrade, as you never know what may happen. The upgrade process is done on an active project, which is different than many other QC upgrade tasks. That being said, ensure that no one is accessing the project while the upgrade is running.
Once we had everything set up correctly and processed the upgrade, we found that we were now able to open our older scripts to edit in QTP10. We were also able to execute the scripts without error.