Test faster, test faster with HP QC
May 27, 2016

Test faster, test faster with HP QC

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with Quality Center (formerly HP Quality Center)

HP Quality Center is being used for IT quality management of complex healthcare applications. It is used for managing requirements, tests, and business components for sales and enrollment applications.
  • It works well with Automated Unit testing. Test scripts can be written once and executed multiple times. This saves a lot of time otherwise spent in manual testing.
  • HP Quality center provides a concise way to write the requirements, create test cases, link them to requirements, create test sets and execute the tests, create defects and link them back to test cases and eventually to requirements, linking all the test assets (test cases, requirements and defects) on multiple levels to Releases and cycles.
  • It is possible to associate requirements with more than one release. This was particularly handy when we needed to move the requirement to another release or have to split the requirements across multiple releases.
  • Task tracking was a challenge, especially with the development community and integration with the development tool was difficult.
  • If we are creating a large number of test scripts, and storing it in QC, and using QC to kick off tests, then it's overkill and probably not worth the license fee.
  • HP QC defines relational database as supporting the relationship between test and test sets. These are primarily undocumented tables. The tests are not stored in a database, though, and so there is no rollback if Quality Center or QTP has problems. Cleanup is manual and depends on your knowledge of the disk directory structure and the database layout and table relationships.
  • We have faster delivery of products with high quality and significantly less labor costs.
  • Improved operational efficiency by measuring and reporting key performance indicators (KPIs).
  • Best practices can be shared across multiple divisions and lines of businesses. This provides a good start for new projects and prevents reinventing the wheel all the time.
HP needs to have better support for agile testing as compared to JIRA. JIRA also has some powerful integration using REST APIs. Silk Test's portability enables users to test applications more effectively with lower complexity and cost in comparison to HP QC.
It is good for a Windows operating system. You have to use a virtual machine for other operating systems.

OpenText ALM/Quality Center Feature Ratings