Annoyance in Quality Center Reporting

September 9, 2007 · 1 min read

Not only am I an Automation Engineer, I'm also one of the Quality Center admins at my current job.

And for the record, the out of the box reporting capabilities of Quality Center SUCK.  I had a situation last week where the Manual Testing Manager wanted a list of test cases that appear in one test set but not in another.  Simple "intersection" of two test sets right?

WRONG! I tried every concievable report schema to get this to work and kept failing.

Ultimately, I was forced to go to the DB and do a direct select statement with about 5 table joins to get the Test Plan location of the test cases.

In a word...ANNOYING!!!

Its the weakest part of that application and ye gods is it frustrating.

This article is part of the GWB Archives. Original Author: Maryanne Sweat

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.