Comments on: HP Quality Center 10 from a Test Manager’s Perspective

By: German Garcia

German Garcia — Fri, 07 Aug 2009 23:55:57 +0000

Hi all,

I had the chance to assist a webinar of this latest version. I have to say that is awesome. Besides version control, baselines, integrated dashboards, common shared libraries, you have to mention that now HP thinks not only in very big enterprises but also in small companies (let’s say 20) that doesn’t need to stablish a very huge tool; I see this positive because of QC costs. I can recall that now there are available about 3 versions (Come on QC guys, help me out on exact names).

Regards,

German.

By: James

James — Mon, 06 Jul 2009 20:11:45 +0000

Hi Serge,
nice summary you written….answers alot of of our questions.
we are upgrading from QC9.2 to QC10 and was wondering if you have had any issues with the install…any tips or tricks or holes to avoid?

we had issues with upgrading to 9.2 so we want to be a little more proactive for the UG to 10.

if there is a separate link for this please direct me.

thanks,
James

By: Amit Kumar

Amit Kumar — Tue, 23 Jun 2009 08:56:23 +0000

Hi Avi,

I found version control a bit confusing

Lets say a project X is under version control, now I create a new folder in Test Plan tab calling it “New Req”, now when I add a new folder “test cases” and test case “test one” under this folder it is checked out with version 1, now the moment I check in its version changes to 2.

Don’t you think its version should be 1 as its first instance of that test case being created and later when any update is done the version should be changed to 2.

Thanks

Amit

By: Avi Kavas

Avi Kavas — Wed, 17 Jun 2009 18:30:56 +0000

I would like to comment to Shalini’s post,

“Hi Avi/Serge,
Test Management is already available in HP QC9.2.
Now my client wants to upgrade the HP QC9.2 to HP QC10. Any impacts due to migration of the data to QC10?”

I don’t anticipate any noticable impact of data migration to QC 10.0. Is there any specific aspect you are concerned about?

Thanks,
Avi

By: Farid

Farid — Thu, 04 Jun 2009 01:18:17 +0000

Hi Avi,

I think it was a bit hasty post!

Got it – It is Dashboard > Export

Thanks,
Farid

By: Farid

Farid — Thu, 04 Jun 2009 01:02:46 +0000

Hi Avi,

“=> In patch 2 of QC 10.0 we have added the ability to export a page to PDF format so it can be easily printed or distributed by e-mail.”

I have installed patch 2 and I cannot see any option to export as PDF. Where do I find that?

Thanks,
Farid

By: Mark Ford

Mark Ford — Wed, 03 Jun 2009 16:50:33 +0000

I think it’s worth mentioning that the Business Component (BPT) module in QC 10.0 also benefited from significant improvements:

* Canned reports & graphs are now available for the BPT module
* Create collections of BPT components in a fixed sequence that perform a specific task (flows)
* Can convert manual tests to BPT components
* Can add user defined fields and workflow code to BPT module
* Can copy components and BPT tests from one project to another
* Prompts for parameter promotion when BPT component is assigned to test
* More “Used By” dependency views (resources and application area)
* Dynamic dates can be used to represent time relative to the current date
* Cross filtering and send mail options

By: Mark Ford

Mark Ford — Tue, 02 Jun 2009 21:22:39 +0000

The QC 10.0 version control functionality is limited in that only one version can be checked out at a time. You could branch by creating a copy of a test but that’s not really all that helpful as you cannot compare the two after updates are made.

You can however create branches using the baseline import functionality. Take a baseline of the folder containing the version 1.1 tests and then import that baseline back into the SAME project into a different folder for your interim version 1.1.1. The version 1.1 version tests can now be updated for 1.2 independently from the version 1.1.1 tests.

When finished with the version 1.1.1 tests you can take another baseline and compare it back to the original to see everything that changed. You can then retrofit these changes back into the version 1.2 tests.

By: Marc Robertson

Marc Robertson — Mon, 01 Jun 2009 20:53:36 +0000

Does the version control functionality include branching to allow for parallel development? For example, suppose you have Feature A in version 1.1( no one ever buys 1.0 ) of your software, and have a test written for that. You start working on 1.2, creating a branch in your source code repository for the source code, and need to change the tests to match the new functionality. Then, you decide that the feature could be improved with a fairly simple change you can get out the door quickly, while continuing the more extensive changes planned for version 1.2. So, you create a branch for version 1.1.1, and need to modify the tests for that. I guess I’m trying to understand why you wouldn’t put the test scripts in the appropriate branch in your source code repository. Keeping the tests in a separate repository would seem to make it more complicated to connect source code version with test version.

By: shalini

shalini — Mon, 01 Jun 2009 06:25:13 +0000

Hi Avi/Serge,

Test Management is already available in HP QC9.2.
Now my client wants to upgrade the HP QC9.2 to HP QC10. Any impacts due to migration of the data to QC10?