When starting up brand new testing project, very important thing is that project structure is planned, written down and communicated to all contributors.

This plan includes things like 

Common terminology Rules how to organize data Naming conventions for testing entities like test case and test set How are test cases described, which type of information belongs to description, what goes into steps What is the target group for executing test cases? Are they people who have not previously used the tool? This is needed in order to define the level in which test cases need to be written in order to tester to understand what should be done What fields are used to categorize items, are they mandatory or not and what values to use What are standard reports that are taken out after every testing period and reported forward What is my Test Set? Is it all the test cases everytime or a subset of them? And of course as these apply mainly when working with Test Management tool (like OnRoad Test Management...

General Reporting Utility for Mercury Quality Center and TestDirector has new report available: Grouping Grid Report:



What this report allows to do, is grouping based on any Requirement, Test Case, Test Set, Test Case in Test Set, Run or Defect field and see how many matching items there exists.

Grouping Grid Report gives option for multi level grouping, sorting and filtering across the data that is exported from Quality Center or TestDirector.

General Reporting Utility is part of Utility Tools and can be downloaded from here:

Utility Tools Setup for Mercury Quality Center 9.0

...

General Reporting Utility for Mercury Quality Center and TestDirector has new reporting options available:

Cumulative Test Case per DayCumulative Test Case per WeekCumulative Test Case per MonthThese three reports produce data-, summary- and graph information:

Cumulative Test Case Report SampleCumulative Test Case per Month Sample Report   

General...

One scenario that is often discussed is how can I share and reuse requirements and test cases that my subcontractor has been defining while developing and testing system in their premises? Both of us are using Mercury Quality Center (not the same version though) and it seems redicilous that I can not access those and I need to totally rewrite them during acceptance testing.

One option is that they will just print them out in the word document, send it over and I will try to import them back to my Quality Center, but this is really slow and erranous scenario where lots of things can go wrong.

And what if requirements and test cases are changed very often? I need to do this import all over again and again... Not a good idea.

Answer to this question is really an utility which can export requirements, test cases (including linked test cases), design steps and all of these while preserving folder structure and taking the attachments out as well. Then I could receive all of these in one file which...