Mercury TestDirector for Quality Center

Mercury TestDirector for Quality Center

Average User Rating:
1.8
out of 16 votes
See all user reviews

Quick Specs

Version:
9
File Size:
Not available
Date Added:
June 01, 2006
Price:
Free to try (30-day trial with 5 user licenses)
Operating Systems:
Windows 98/NT/2000/XP
Total Downloads:
172,886
Downloads Last Week:
125
Product ranking:
Additional Requirements:
Windows 98/NT/2000/XP/2003 Server

Editors' Note: Please contact the developer for pricing information.

Publisher's Description

More Products to Consider

All User Reviews
  • All Versions:

    1.8

    out of 16 votes

    • 5 star: 1
    • 4 star: 1
    • 3 star: 1
    • 2 star: 3
    • 1 star: 10
  • Current Version:

    2.7

    out of 6 votes

    • 5 star: 1
    • 4 star: 1
    • 3 star: 1
    • 2 star: 1
    • 1 star: 2
  • My rating:

    0 stars

    Write review

    Results 1-2 of 2

  • 1 stars

    "terrible software!"

    January 22, 2014   |   By timoteoalpha1

    Version: HP Quality Center 11.5

    Pros

    in theory, a good way to organize, manage, and run your Quick Test Pro (QTP) scripts.

    Cons

    buggy, quirky, unreliable, files stored in "repository" are nothing more than a disk directory, database used to manage files in disk directories is not transparent or documented, database gets screwed up from time to time requiring HP to fix.

    Summary

    We have used Quality Center (QC) with Quick Test Pro (both are version 10) for four or five years now.

    HP presents Quality Center as a source control system for your Quick Test Pro scripts. It is allegedly designed to manage and execute Quick Test Pro scripts.

    The Quality Center "repository" consists of a SQL database containing undocumented tables. These tables define the relationship between tests and test sets. The tests are not stored in a database, though, and so there is no rollback if Quality Center or QTP has problems, clean-up is manual and depends on your knowledge of the disk directory structure and the database layout and table relationships. We have learned the disk folder layout and some of the database table relationships from HP when we've had serious problems with Quality Center.

    We have seen again and again corruptions of the database used by QC to manage the disk files and have had to hack the database (with HP's help) to fix the problems. Sometimes QC just gets "confused" and screws up a check-in or check-out, leaving your with tests that can neither be checked out nor checked in. Tests that you know exist on disk cannot be opened in QTP because QC and QTP have screwed up the disk directory that contains the test folders and files.

    QC crashes frequently for seemingly no reason. I was testing last week and QC crashed on me five times in one day. My teammates had similar problems. We never did find out why it was crashing.

    Since the "repository" files are not managed by a database, there is no secure transaction to check files in or out of the repository. If they were in a SQL database, if an error occurred during check-in or check-out SQL would rollback the transaction and the failed transaction would cause no problems. That is not the case with QC's folder- and file- based "repository" system. There is a check-in/check-out history. This consists of a history directory on disk which contains every copy of every file ever checked into QC. It doesn't save deltas like many other source management programs - it saves the entire file each time, so the history takes up vast amounts of disk space. The history directory, like the test directory is unprotected so anyone with access to the server has the potential to do damage, even if unintentional. Sometimes to fix a problem with QC, we have had to go into the disk file directories and manipulate files and directories to get things working again (under the direction of HP at first).

    QC does not have an adequate backup built into it. It can do a backup of your project, assuming it doesn't exceed something like 5GB in size. QC tells you that if your project exceeds that size, the backup may not succeed. So we backup the QC database and all of the disk files regularly via MS SQL backup and file copy to backup disks. QC is also very inefficient and slow (as it QTP). In order to manage our thousand or so tests it is using around 25GB of disk space. Of that space, the "history" and "test" directories together contain around a million files with an average size of ~15k each. with a 4k block size on our NTFS disk, the average file is only 4 disk blocks. So it has many, many very small files it has to manage, meaning it is a monster for time spent on disk I/O.

    QC also provides you no way to run tests or sets of tests at a specified time. The only answer I found on the internet was a VBScript program that uses the QC API to run test sets. This script is built into an exe file that we run via the Windows scheduler. So now you need a programmer familiar with coding against an API and you need the QC API documentation, and a lot of time to figure out how this test works. So, if you want to run your tests on a nightly schedule, better find this code, modify it for your project and installation, then run it via the Windows scheduler on a regular basis.

    Would you use a tool that sometimes screws up your repository, screws up its own database, and crashes frequently for no apparent reason?

    we have over 1,000 QTP tests stored in QC. They are stored in 315,000+ directories and subdirectories, and this includes about a quarter of a milion disk files as well. Our history directory adds another 16GB of disk space plus another 600,000+ disk files in

    Finally, if you use QC you had better sign up for tech support from HP or another provider. Support cost in the neighborhood of $1500 a year. If you suspend the support contract for a year or two because of financial issues, or maybe your organization is not going to be using QC for a few years, or you decide to see how well you can get along without QC support, there is a penalty PLUS you have to pay for every year of support you missed. If you miss two years of support then decide you need it after all, you have to pay the $1500 fee for each of the two years you missed, plus $1500 for the current year, plus a penalty from HP. That amounts to around $5000 to renew after missing two years. Try selling that up the corporate ladder!

    This tool is not only unreliable, it is dangerous to your automated tests because over time it screws up its own database and the disk file structure it uses. I am still fighting with this today and I know most of the "tricks" needed(from experience and from working with HP on problems) to keep QC and its "repository" working. Just when we think we're moved past all the problems (we have had MANY), we run into something new. I am very concerned that sooner or later we are going to end up with a database and disk structure so screwed up that our tests will no longer run. So we are moving to Selnium which is open-source, and costs nothing. There are several commonly used, open-source source code management systems (we use one in our development here) that provide better, safer, more reliable use than Quality Center.

    Highly NOT RECOMMENDED!!

    Reply to this review

    Was this review helpful? (1) (0)

  • 1 stars

    "The worst software I've ever used"

    October 29, 2013   |   By mattdarwin

    Version: HP Quality Center 11.5

    Pros

    There are none. This software is simply awful and I would urge anyone considering it to use a web-based open-source alternative.

    Cons

    1. requires windows - I have to have a VM just for my ticketing tool
    2. Slow
    3. Buggy

    And here's the worst - it's incredibly tightly coupled between the client and the server. They upgraded the server version from 10 to 11, and I can't log in any more. I'm actually having to edit the registry in order to try and make it work.

    Summary

    We use this tool for managing defects and testing in our environments. It's absolutely awful and we all hate it.

    And another thing - you will see two good reviews here, but look closer. One of the users is called 'qualitymercury', and both of them have only ever written one review.

    Reply to this review

    Was this review helpful? (0) (0)

  • Results 1-2 of 2

Add Your Review

Quickly sign in with: or Login or create an account to post a review.
You are logged in as . Please submit your review for Mercury TestDirector for Quality Center
Add Your Review

The posting of advertisements, profanity, or personal attacks is prohibited.
Click here to review our site terms of use.

Update your review

Since you've already submitted a review for this product, this submission will be added as an update to your original review.
Submit

The posting of advertisements, profanity, or personal attacks is prohibited.
Click here to review our site terms of use.

Previous Versions:

Close[x]

Submit a problem report for Mercury TestDirector for Quality Center

Please describe the problem you have with this software. This information will be sent to our editors for review.

Problem:

The Download.com Installer isn't working as expected

The download link does not work

The software has a newer version

The product contains malicious software

Other

Description:

Please select a feedback type.

Please enter a description.

Submit Problem Report

Close[x]

Problem Report submitted

Thank you for submitting a problem report! The Download team is committed to providing you with accurate software information.

OK