We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(6)
我相信您刚刚描述了SmartBear Software 的 TestComplete。
I believe you just described TestComplete by SmartBear Software.
Autoit 会执行您列出的所有操作。我一直用它来治疗同一只海豚。另外,Delphi 的优点在于使用标准 Windows 控件,这使得它很容易连接。
Autoit does everything you listed. I use it for the same porpoises all the time. Also, Delphi is good in the sense that uses standard windows controls which makes it very easy to hook into.
我在 sikuli 方面取得了一些成功,它的优点是 python (jython) 代码。它建立在 OpenCV 之上,并使用完整的图像处理引擎来对屏幕的各个部分进行图案匹配。它还包含用于屏幕截图、等待更改以及击键和鼠标注入的编辑器和功能。
I've had some success with sikuli, which has the advantage of being python (jython) code. It is built on top of OpenCV, and uses a full image processing engine to pattern match parts of the screen. It also contains editors and functions for screenshots, waiting on changes, as well as keystroke and mouse injection.
与我的其他答案不同: PyWinAuto
它具有完整的脚本(因为它是Python),它使用控件名称而不是 X、Y 坐标,它等待窗口并且您可以发送按键。而且它是免费的。
缺点应该是显而易见的:)
Something different from my other answer: PyWinAuto
It has full scripting (because it's Python), it uses control names instead of X, Y coordinates, it waits for windows and you can send keypresses. And it's free.
The downsides should be obvious :)
要自动化delphi应用程序,我发现的主要问题是任何测试工具(带delphi插件的QTP、Test Complete、Testanywhere、autoit、sikuli)都不会检测到任何Tlabels和Tlist以及其他组件,这些组件对于在delphi中构建的应用程序构成了 UI 的一个突出部分。即使要进行基于 func 的测试,我们最终也需要检查前端的组件以查看 func 是否正确输出。即使要使脚本自动化,我们也需要首先能够检测对象并将其添加到存储库中。
我们有一个应用程序,其中我们严重依赖许多第三方组件。我尝试使用市场上几乎所有可用的工具来检查可行性。
市场上排名前两位的工具没有任何用处。
带有 Delphi 插件的 QTP 没有用,即使在他们公开提到的网站上,它不会支持在 delphi 中构建的许多类。
TestComplete 它比 QTP 更好,其中它检测到许多组件菜单组件,如果我没记错网格等。
然后经过几次谷歌搜索后,我发现
当我谈到检测组件时,它可能是部分或完全的,即某些工具能够检测到 XY 坐标处有一个组件,但无法获取组件类或详细信息(如组件属性名称等),否则很难获取组件类或详细信息(如组件属性名称等)自动化和编写脚本。
其余的或多或少都是上述这些的组合或子集。
还在寻找中!!!!!!!!!
To automate a delphi application main problem i found was that the any testing tools (QTP with delphi addon , Test Complete , Testanywhere, autoit, sikuli) they all dont detect any Tlabels and Tlist and and other components, which for an application build in delphi forms a prominent part of the UI. Even to do func based testing we need to ultimately examine a component in the front end to see whether a func is giving right out. Even to right a script to automate we need to first be able to detect and add the object to the repository.
We have an application in which we have heavy dependency on a lot of third party components. I have tried to check feasibility with almost all the tools available in market.
The top two tools in market were of no use.
QTP with Delphi addon is of no use even in there website they have openly mentioned it wont support many classes build in delphi.
TestComplete its better than QTP where in it detects many components menu components and if i remember correctly grid etc.
Then after few googling i found
When i speak of detecting components it may be partial or fully ie some tools were able to detect that there is a component at XY co-ordinates but failed to get the component classes or details (like components property name etc) without which it was difficult in automating and writing a script.
Rest all was more or less combination or subset of these above there.
Still Searching !!!!!!!!!!!
使用 TestComplete,如果您将应用程序编译为开放应用程序 - 即包含它们的库,它会使您的应用程序超级易于检查。非常适合测试,但可能不太适合安全性。测试完成是最好的,对于我的预算来说太贵了。
里面的脚本很棒,对Delphi的理解也很棒。价格标签并不高,特别是如果您想在组织内获得 GUI 测试的吸引力,就像听起来的那样。
With TestComplete, if you compile your app as an open app - i.e. include their libs, it makes your app super inspectable. Great for testing, probably not best for security. Test complete was the best, it is just TOOOO expensive for my budget.
The scripting in it is great, the understanding of Delphi is great. The pricetag is just not great, especially if you are trying to get traction for GUI testing within an org, like it sounds like you are.