I am looking for ideas on how others utilize Quality Center in relation to Test Plans. To date, all of our projects have individual test plans related to the project. I am trying to broaden the usage of QC here to stop re-work. The idea is to have a central test bed that can be accessed for multiple projects.
I know I can copy test plans from 1 project to another. But if the project requires updates to the test plan, the testers must remember to update the original and so forth.
I am currently on QC version 9.2 and don't know if 10.0 offers more flexibility in this area.
If you are in a similar situation, please let me know how you handle this.
QC 10 offers you templating of projects so that should help you with workflow, but not individual test management (that I know of)
What I have come across in the past is a set-up where there is ONE regression project where ALL tests are stored. This is the source of truth for the creation of all other projects.
Each sub project was based on a release and meant that subsequent changes to the application required modification of the tests. This meant that once the full suite of tests was imported, run, updated to cover changes, run, then totally passed according to the release, the test lead for each area updated the regression project with the updated scripts.
In this case it was not the job of the testers to manage the base regression suite, but the Test Leads.
While I have been working for Businesses that are Vendor partners with HP, IBM and Microsoft, my opinions and advice is my own.
The solutions provided are either sourced from my own scripting libraries or from a quick Google Search.