vote up 0 vote down
star

We're interested in feedback on the best tools to use for both test automation and test management, such as HPQC, Zephyr, and Microfocus. Heavy focus on ease of use with a variety of applications, including vendor-based as well as homegrown.

flag

3 Answers

vote up 1 vote down

Like so many things - it depends. First and foremost, I would split the question between test management and test automation and ask more specific questions - perhaps as separate questions.

For test management, there are a variety of questions that need to be considered:

  1. What development methodology is in use? Some tools are better suited for agile processes and would not be a good fit for a more heavyweight process.
  2. Are you testing a product in a regulated industry? The tracking and reporting requirements in these industries will narrow down the choices.
  3. Are their platform restrictions? A great tool for the Mac will not work in a Windows only shop.
  4. What are your cost constraints? There are great tools that are only available to those with big budgets.

For test automation, many of the above questions apply. In addition:

  1. What type of automation? End to end functional, unit testing, load testing, web vs. desktop vs. mobile device.
  2. Development language? A .net tool may be great but of no use if you are a java shop.
  3. Integration requirements - does the output of the tool need to integrate with some other system?
  4. Technical ability of the staff who will be using the tool

In terms of homegrown tools - do you have the staff, the time and the willingness to maintain the tool over the long haul?

link|flag
vote up 0 vote down

I would recommend you check PractiTest with functionality to cover the end-to-end QA process, not only easy to use but also easy to configure (you can be up and working in a matter of minutes) and logically priced.

There is both a Free Demo as well as a 30-Day evaluation

(and yes, I work for PractiTest in case you were wondering, but I also used to manage the QA for HPQC for a number of years...)

link|flag
vote up 0 vote down

QC strength is NOT on ease of use with homegrown applications. It has a lot of pluses and tight integration with HP's GUI testing tools but once you are trying to add non standard applications or interfaces you lose its ease of use.

link|flag

Your Answer

Get an OpenID
or

Not the answer you're looking for? Browse other questions tagged or ask your own question.