Wednesday, March 11, 2009 7:27 AM
Updated 4/27/09 - As of Test Design Studio 1.6.4227, QuickTest 10 is fully supported and Quality Center 10 is supported with the exception of the Repository module. Repository module support is planned for TDS 2.0.
HP has recently released updated versions of QuickTest Pro (v10.0) and Quality Center (v10.0). Since Test Design Studio (TDS)integrates with these tools, we wanted to clearly define our policy on supporting new upgrades and the current status of the integration.
Our goal is to always support the latest versions of these tools as quickly as possible.
QuickTest 10
Status: Basic Support, Not Fully Tested
QuickTest 10 testing is still underway. You should see no impact to your ability to edit scripts, but may encounter some issues with actions that utilize the API to control QuickTest. Assuming no breaking changes in the API, integration should contintue to work as normal. This, however, is a bold assumption.
HP has also changed the file format for QuickTest 10 so that it is not compatible with previous versions of QuickTest. You can still you the file templates that are provided with TDS, but will receive a prompt about upgrading the files if you open them in QuickTest 10. Since templates can be completely customized by the end user, you can upgrade these templates on your own to avoid the prompt.
Quality Center 10
Status: Unsupported
It appears an issue with the Quality Center API has broken integration with TDS. Some portion of the 'Logout' method is hanging, which causes TDS to be unresponsive when attempting to configure a new Quality Center 10 server. We will investigate and resolve this issue as soon as possible.
Our first goal is to get TDS working with Quality Center 10 at the same level it works with Quality Center 9.x. This means the new Repository module will probably not be initially supported, but we do plan to add the ability for TDS to properly integrate with this new storage mechanism. The new integrated Version Control may not be initially supported either depending on the API changes that are used to interact with versions. If the new integration VC is implemented like the old 3rd-party VC, TDS integration should not be difficult and may require no updates. Further investigation is required.