Quality Center api 仅使用 HTTP？
所以..我将 IE 设置为使用 WebScarab 作为代理，然后登录到 Quality Center。你瞧，该程序使用 HTTP 与服务器进行所有通信，并且所有命令和响应都是人类可读的文本。它不是 XML，也不是 JSON，但它是人类可读的，而且我非常确定如果需要的话我可以编写它。
那么..该协议是否有记录在任何地方？你“应该”能够使用这个吗？无论如何，有人有使用它的经验吗？
是的，我知道他们有一个 COM api，但我有一种感觉，我通常在 QC 中遇到的崩溃行为可能是在 COM 对象中，所以我可能编写的任何使用它们的软件都会表现出相同的行为。
So.. I set up IE to use WebScarab as a proxy, and then logged into Quality Center. Lo and behold, the program uses HTTP to do all its communication with the server, and the all commands and responses are human-readable text. It ain't XML, it ain't JSON, but its human-readable and I'm pretty sure I could write it if I had to.
So.. is this protocol documented anywhere? Are you "supposed" to be able to use this? Anybody have any experience using it anyway?
And yes I am aware that they have a COM api, but I have a feeling that the crashy behavior I normally experience from QC is probably in the COM objects, so any software I might write that uses them would exhibit the same behavior.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
官方支持的与 QC 通信的方法是通过已发布的开放测试架构 (OTA) API，该 API 有很好的文档记录。我认为尝试在较低的 HTTP 级别重写 API 会导致您的工作中断。许多人成功地使用 OTA API 来自定义 QC 并编写第三方扩展。此外，许多 COM 特性现在都记录在 .NET 上。也许您可以详细说明一下您在使用 COM API 时遇到的各种问题？
The officially supported method for communicating with QC is via the published Open Test Architecture (OTA) API which is very well documented. I think you would have your work cut-out trying to re-write the API at a lower HTTP level. Lots of people are using the OTA API successfully to customise QC and write third-party extensions. Also many of the COM idiosyncrasies are now documented on the .NET. Maybe you can elaborate on the sorts of problems you are having with the COM API?
以下页面可以提供帮助：
访问
http://technologicaguru.blogspot.com/2009 /06/connect-to-quality-center-ota-client.html
The below page can help :
Visit
http://technologicaguru.blogspot.com/2009/06/connect-to-quality-center-ota-client.html