不。 我现在在客户处使用，并且讨厌它。 它不支持非 MS 浏览器（ActiveX 等），因此在 OS X 上，我们只能使用 VM 等。此外，它的界面相当笨重且复杂。 慢的。 这是古老、可怕的遗留技术。 还有很多更好的选择。
NO. I'm using now at a client, and hate it. It does not support non-MS browsers (ActiveX, etc), so on OS X, we are stuck with VMs, etc. Moreover the interface it quite clunky & slow. It's ancient, horrible, legacy tech. There are much better options.
我们有很多客户将 QC 缺陷和测试跟踪集成到流水线持续集成中。 但 QC 并不驱动该流程，而是集成到 CI 和 CID 流程中。
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.
We use QC to run what are called Test Sets. We have been very successful running in this manner. You can use QC to notify you on a failed execution. This would of course notify you if something did not compile on QTP's end. You also set up other QTP and LoadRunner scripts to run if a script fails.
这不是一个好主意，我已经为QC和Borland工具（针对HP）做了POC，尽管可能，但有太多同步必须完美的区域，并且有时由于网络等原因QC的响应时间很慢触发正确的文件，获取编译结果并发布有点不稳定。 从技术上讲，通过 API 也是完全可行的。
Not a good idea, I've done a POC for QC and Borland tools (for HP), and although possible, there are too many area where the synchronization has to be perfect, and the slow response time of QC sometime due to network etc to trigger right file, get result of compilation and publish is a bit shaky. Again technically via API it is completely feasible.
发布评论
评论（4）
不。 我现在在客户处使用，并且讨厌它。 它不支持非 MS 浏览器（ActiveX 等），因此在 OS X 上，我们只能使用 VM 等。此外，它的界面相当笨重且复杂。 慢的。 这是古老、可怕的遗留技术。 还有很多更好的选择。
NO. I'm using now at a client, and hate it. It does not support non-MS browsers (ActiveX, etc), so on OS X, we are stuck with VMs, etc. Moreover the interface it quite clunky & slow. It's ancient, horrible, legacy tech. There are much better options.
我们有很多客户将 QC 缺陷和测试跟踪集成到流水线持续集成中。 但 QC 并不驱动该流程，而是集成到 CI 和 CID 流程中。
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.
我们使用 QC 来运行所谓的测试集。 我们以这种方式运行非常成功。 您可以使用 QC 来通知您执行失败。 如果 QTP 端未编译某些内容，这当然会通知您。 您还可以设置其他 QTP 和 LoadRunner 脚本，以便在脚本失败时运行。
We use QC to run what are called Test Sets. We have been very successful running in this manner. You can use QC to notify you on a failed execution. This would of course notify you if something did not compile on QTP's end. You also set up other QTP and LoadRunner scripts to run if a script fails.
这不是一个好主意，我已经为QC和Borland工具（针对HP）做了POC，尽管可能，但有太多同步必须完美的区域，并且有时由于网络等原因QC的响应时间很慢触发正确的文件，获取编译结果并发布有点不稳定。 从技术上讲，通过 API 也是完全可行的。
Not a good idea, I've done a POC for QC and Borland tools (for HP), and although possible, there are too many area where the synchronization has to be perfect, and the slow response time of QC sometime due to network etc to trigger right file, get result of compilation and publish is a bit shaky. Again technically via API it is completely feasible.