Search code examples
continuous-integrationqtpissue-trackinghp-quality-center

Is it a good idea to use HP Quality Center for Continuous Integration?


We need to compile our code after check - ins, be notified if compile fails, run tests, be notified of test results and publish our application (publish a website or create an msi file for a desktop app) on a daily basis.

We are using SVN and were considering using TeamCity or CruiseControl.NET for continuous integration server for our .net projects which have msunit tests.

My project manager came up with HP Quality Center and Quick Test Professional (it is already purchased) and suggested using them for issue tracking (currently we are using Jira) and continuous integration.

Does it make sense?


Solution

  • We have lots of customers who integrate QC defect and test tracking into pipelined continuous integration. But QC is not driving the process, it's being integrated into the CI and CID process.